You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On seL4/seL4#449 which does not change the binary (checked that by comparing said binaries), we saw the PC99_debug_clang_64 simulation test failing. It succeeded after re-running.
The specific test task that failed was Running test SCHED0021 (Test for pre-emption during running of many threads with equal prio), which depends on timer input.
It looks like that can be too unreliable on GitHub.
Just putting this information here in case we're seeing this more often. If we do we might either have to remove this test from simulation, or tweak parameters to make occurrence rare enough that it is not a nuisance.
The text was updated successfully, but these errors were encountered:
Seems SCHED0021 is als suffering from a race condition. The threads are release and a yield() is called. It might happen that the round robin scheduler preempts the main thread after it released the other threads (by clearing the global variable), but before is can call yield(). In this case all threads can run 2 time slices and not just one.
On seL4/seL4#449 which does not change the binary (checked that by comparing said binaries), we saw the PC99_debug_clang_64 simulation test failing. It succeeded after re-running.
The specific test task that failed was
Running test SCHED0021 (Test for pre-emption during running of many threads with equal prio)
, which depends on timer input.It looks like that can be too unreliable on GitHub.
Just putting this information here in case we're seeing this more often. If we do we might either have to remove this test from simulation, or tweak parameters to make occurrence rare enough that it is not a nuisance.
The text was updated successfully, but these errors were encountered: