-
Notifications
You must be signed in to change notification settings - Fork 217
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
Test #7: osal-core-test Failure #424
Milestone
Comments
osal/src/tests/osal-core-test/osal-core-test.c Lines 121 to 140 in 7d9c4c8
|
skliper
added
bug
unit-test
Tickets related to the OSAL unit testing (functional and/or coverage)
labels
Apr 17, 2020
It is great to see this reported by someone else on Linux. My macOS port has this too this is why I have commented out the test in the branch. See here. |
Perhaps loop on the delay checking if the child task has exited. |
skliper
added a commit
to skliper/osal
that referenced
this issue
Apr 20, 2020
14 tasks
astrogeco
added a commit
that referenced
this issue
Apr 28, 2020
Fix #424, Add looping wait for self exiting task
astrogeco
pushed a commit
that referenced
this issue
May 1, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Test #7: osal-core-test fails.
To Reproduce
Steps to reproduce the behavior:
Note: this test was not readily repeatable, but it failed 2/10 times on this branch:
fix413-Add-Reference-To-Osal-Users-Guide-From-ReadMe
Expected behavior
The test failed 2/10 times. Specifically, failure is due to the code snippet noted below in osal-core-test.c, line 138 where a small time delay is supposed to occur and the child task is perhaps not exiting before the OS_TaskDelete call happens, so it's returning success.
Code snips
[ FAIL] 01.261 osal-core-test.c:138 - OS_TaskDelete, self exiting task
System observed on:
GNOME VM
OS: Ubuntu 18.04
Versions: OSAL 5.0.11.0
Additional context
This may be due to the VM delay.
Reporter Info
Yasir Khan
NASA GSFC
The text was updated successfully, but these errors were encountered: