Integration Tests Failing When Merged with Radio #48
Description
It looks like our integration tests are failing after a merge commit from main into #40. I have tried running the jobs on both the spacelab and deathstar runners and it fails the same way in both. I have also verified that running a test from main does not cause and failures.
RP2350 not in bootloader mode - triggering bootloader
============================= test session starts ==============================
platform linux -- Python 3.13.7, pytest-8.3.3, pluggy-1.5.0
rootdir: /home/broncospace/Documents/proves-cd/actions-runner/_work/proves-core-reference/proves-core-reference
plugins: fprime-gds-4.0.2a7
collected 1 item
FprimeZephyrReference/test/bootloader_trigger.py E [100%]
==================================== ERRORS ====================================
______________________ ERROR at setup of test_bootloader _______________________
fprime_test_api_session = <fprime_gds.common.testing_fw.api.IntegrationTestAPI object at 0x7fc57f706e40>
@pytest.fixture(scope="session", autouse=True)
def start_gds(fprime_test_api_session: IntegrationTestAPI):
process = subprocess.Popen(["make", "gds-integration"], cwd=os.getcwd())
gds_working = False
timeout_time = time.time() + 30
while time.time() < timeout_time:
try:
fprime_test_api_session.send_and_assert_command(
command="CdhCore.cmdDisp.CMD_NO_OP"
)
gds_working = True
break
except Exception:
time.sleep(1)
> assert gds_working
E assert False
FprimeZephyrReference/test/bootloader_trigger.py:24: AssertionError
---------------------------- Captured stdout setup -----------------------------
15:24:28.506010 [Test API] Sending Command: CdhCore.cmdDisp.CMD_NO_OP []
15:24:28.506564 [Test API] Beginning a sequence search of 2 items.
15:24:28.506901 [Test API] Sequence search now awaiting for at most 5 s.
make[1]: Entering directory '/home/broncospace/Documents/proves-cd/actions-runner/_work/proves-core-reference/proves-core-reference'
Warning: Checksum validation failed.The integration test runner does successfully run the main tests again after the failed test run, indicating that something is going wrong specifically with the boot loader_trigger component in the #40 branch.