Incomplete cleanup in scheduler leading to bugs
See original GitHub issueThe test that caused the error was added in ktbarrett/cocotb@d589303f9ae8cca17789b21b597e4bec66cf80bf. The failure can be observed by running the failing test and at least one other test after it.
cd tests/test_cases/test_cocotb
make MODULE=test_concurrency_primitives COCOTB_SCHEDULER_DEBUG=1 TESTCASE="test_exceptions_forked_late,test_exceptions_first"
You can see from the log that the coroutine test_exceptions_forked_late.<locals>.await_later
that was scheduled in the first test was not cleaned up and fires in the second test and causes it to fail.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Bugs fixed in each 19.0.0.0.0 Release Update and ... - ANBOB
This document lists the non-security important bugs( NOT ALL bug fixes) ... 31071080, INCREASE WAIT IN RMON TO ENSURE ORPHAN CLEANUP WHEN ...
Read more >[New scheduler] Fix new scheduler bug by kisuke95 · Pull Request ...
I've run scripts/format.sh to lint the changes in this PR. · Testing Strategy. Unit tests; Release tests; This PR is not tested (please...
Read more >MySQL bugs fixed by Aurora MySQL database engine updates
The following sections identify MySQL bugs that have been fixed by Aurora MySQL ... Fixed an issue which can lead to a failure...
Read more >process - Is it feasible to track or measure the cause of bugs or is this ...
If too many bugs is a big problem, then management and lead programmers ... High bug rates can be a symptom of a...
Read more >730169 – postgresql generated core file is incomplete
This is unrelated to GDB, this is a kernel core file producer bug. ... In the unmodified schedule, you'll only see concurrent core...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@eric-wieser Did you check the log from the OP? You can see a couroutine from the first test is still being scheduled during the second test (line 59). After the
Timer
returns it reschedules that coroutine where it awaits on the outcome fromraise_soon
, which is stored.The correct solution is to not use
fork
, but preferstart_soon
instead.