-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Functional tests get stuck at SB Performance test #2592
Comments
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 15, 2024
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 15, 2024
2 tasks
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 16, 2024
This avoids the timeout on SB receives for the receiver tasks
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 16, 2024
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 16, 2024
This avoids the timeout on SB receives for the receiver tasks
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 16, 2024
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 29, 2024
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 29, 2024
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 29, 2024
pepepr08
added a commit
to pepepr08/cFE
that referenced
this issue
Aug 29, 2024
dzbaker
added a commit
that referenced
this issue
Aug 29, 2024
Fix #2592, Yield cpu to other tasks in SB Perf Test
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When running the cFE functional tests on the MUSTANG processor card and using RTEMS, the SB performance test gets stuck forever. The test is TestBulkTransferMulti4. In this test, the command transmitter task preempts the telemetry transmitter task and doesn't let it run until it is finished. The telemetry receiver task only waits 5 seconds for receiving a packet, before it exits. When the telemetry transmitter task finally gets to run, the receiver has already exited so there is no one to give the semaphore that lets the transmitter task to continue running.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Code snips
The timeout in the following line can be increased to work around the issue.
System observed on:
Additional context
Add any other context about the problem here.
Reporter Info
Full name and company/organization if applicable
The text was updated successfully, but these errors were encountered: