Skip to content
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

Coverage test failure in VxWorks #321

Closed
jphickey opened this issue Dec 18, 2019 · 0 comments · Fixed by #334
Closed

Coverage test failure in VxWorks #321

jphickey opened this issue Dec 18, 2019 · 0 comments · Fixed by #334
Assignees
Milestone

Comments

@jphickey
Copy link
Contributor

Describe the bug
The coverage test cases for OS_VxWorks_Sigwait are failing:

[BEGIN] 03 OS_VxWorks_SigWait
[ FAIL] 03.001 coveragetest-ostimer.c:160 - Osapi_Internal_CallSigWaitFunc(0) (0) == 8888 (8888)
[ FAIL] 03.002 coveragetest-ostimer.c:162 - Osapi_Internal_CallSigWaitFunc(0) (0) == 5555 (5555)
[ FAIL] 03.003 coveragetest-ostimer.c:164 - Osapi_Internal_CallSigWaitFunc(0) (0) == 5555 (5555)
[  END] 03 OS_VxWorks_SigWait   TOTAL::3     PASS::0     FAIL::3      MIR::0      TSF::0      N/A::0   

To Reproduce
Build OSAL coverage tests and execute

Expected behavior
All tests should pass

System observed on:
Ubuntu 18.04 LTS 64-bit

Additional context
This was probably some fallout related to the VxWorks timer fixups that were done recently (#271, #274) but never noticed because the OSAL coverage test is still separate (that aspect is also being addressed).

Reporter Info
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey self-assigned this Dec 18, 2019
jphickey added a commit to jphickey/osal that referenced this issue Dec 18, 2019
This is related to the change for nasa#271, where the return value
of this function depends on the configured timer interval.  The
coverage test case for this was not updated in the original change.
skliper pushed a commit that referenced this issue Dec 30, 2019
This is related to the change for #271, where the return value
of this function depends on the configured timer interval.  The
coverage test case for this was not updated in the original change.
skliper added a commit that referenced this issue Dec 30, 2019
Fix #295, #298, #305, #307, #308,
    #313, #314, #316, #321, #323
Reviewed and approved at 2019-12-18 CCB
@skliper skliper added this to the 5.1.0 milestone Jan 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants