Bump to fprime-tools v4.0.0a6 (Fix CI)

[LeStarch]

Related Issue(s)
Has Unit Tests (y/n)
Documentation Included (y/n)

---

Change Description

Just bumping to fprime-tools v4.0.0a4 to ensure backwards compatibility.

[Copilot]

Pull Request Overview

This PR updates the CI integration to allow selecting a specific platform directory when running tests and applies it for the Raspberry Pi target.

• Added an optional PLATFORM parameter to integration_test_run (default *)
• Updated the fprime-gds dictionary path to use the new PLATFORM variable
• Modified RPI-Ints.bash to invoke integration_test_run with "raspberrypi"

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File	Description
ci/tests/fputil.bash	Export PLATFORM and inject it into the fprime-gds dictionary path
ci/tests/RPI-Ints.bash	Pass "raspberrypi" as the second argument when calling integration_test_run

Comments suppressed due to low confidence (1)

ci/tests/fputil.bash:62

• [nitpick] Add a brief header comment explaining the optional second PLATFORM parameter, its default (*), and how it affects the dictionary lookup to improve clarity for future maintainers.

function integration_test_run {

[kevin-f-ortega]

Nice catch @LeStarch !

[LeStarch]

Diagnosis: the RPI tests failed because the new system includes both the deployment build and the unit-tests when building a deployment. This is likely the preferred behavior, however; it does mean that the UTs built including the deployment resulting in both Linux and raspberrypi being installed.

This meant that we required a unique identifier and not *

[LeStarch]

@kevin-f-ortega please review and if you approve, merge this one. Should fix CI.