-
Notifications
You must be signed in to change notification settings - Fork 215
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
OSAL Timer UT failing intermittently #943
Comments
Likely that whatever this is will be the same as #942 (just hypothesizing) ... but please advise as much as you can about your specific VM config and I can attempt to reproduce on my side. |
FWIW, today I did open up my VirtualBox install (currently reporting itself as version 6.1.18) and made a new VM with a fresh Ubuntu 20.04 install. I selected "minimal" install, then did the usual apt-get updates and installed build prerequisites, then pulled down the latest bundle from github and built it. In the end - I ran So - I'm suspecting this has something to do with configuration. In particular I'd like to compare the settings for "System" in the VM settings GUI - i.e. amount of RAM and vCPUs assigned to the guest, acceleration options, etc. Also - One issue I did run into - for some reason, by default, VirtualBox did not immediately enable caching on my virtual disk. Which meant that the disk was exceptionally slow. Even just getting the install done was taking way too long - so I forced-off, found the cache setting, enabled it, and restarted the install - which was MUCH faster second time around. |
Note the "1Hz" processing on the system in question is extremely jittery, added a syslog right before the 1Hz elapsed check:
and a sample result shows huge errors (> 500ms in one case)! Note on my docker errors are less than 2ms, the default limit is 20ms. I'm somewhat surprised there isn't at minimum a debug event generated for such poor performance, just a counter in tlm.
|
Implement consistent conversion/lookup functions to translate between names and IDs for all resource types. Also reorganize all internal resource ID functions into a separate source file for better organization. Clean up documentation and references.
Add a NULL check to CFE_ES_ResourceID_ToIndex_Internal(). Although this function is internal, it does check arguments on behalf of the public APIs which call this.
For backward compatibility - remove logic that actually made thes different numerical values. This should be put back in at some point.
Describe the bug
On my virtual machine running Ubuntu 20.04, OSAL_timer_UT fails roughly 50% of the times I run it. Specifically the OS_TimerSet test.
To Reproduce
Run Make test
Expected behavior
It should pass 100% of the time.
Code snips
Here is the printout
BEGIN] 05 OS_TimerSet
[ PASS] 05.001 ut_ostimer_timerio_test.c:525 - #1 Invalid-id-arg
[ INFO] 05.002 ut_ostimer_timerio_test.c:532 - #2 Internal-error
[ INFO] ut_ostimer_timerio_test.c:553:
OS_TimerSet() - #3 Interval-too-short (clk_accuracy=10000)
[ PASS] 05.003 ut_ostimer_timerio_test.c:560 - #3 Interval-too-short
[ INFO] ut_ostimer_timerio_test.c:591:
OS_TimerSet() - #1 Nominal condition (clk_accuracy=10000)
[ FAIL] 05.004 ut_ostimer_timerio_test.c:600 - #4 Nominal
[ END] 05 OS_TimerSet TOTAL::4 PASS::2 FAIL::1
System observed on:
Ubuntu 20.04
Reporter Info
ALex Campbell GSFC
The text was updated successfully, but these errors were encountered: