Repository navigation
fix: start only the missing threads after a failed pool start - #467
Conversation
|
An automated preview of the documentation is available at https://467.capy.prtest3.cppalliance.org/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-10-23 20:05:39 UTC |
|
GCOVR code coverage report https://467.capy.prtest3.cppalliance.org/gcovr/index.html Build time: 2026-10-23 20:17:39 UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #467 +/- ##
===========================================
+ Coverage 98.36% 98.47% +0.10%
===========================================
Files 137 137
Lines 7293 7293
===========================================
+ Hits 7174 7182 +8
+ Misses 119 111 -8
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 10 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
If a worker thread failed to start, the next post() started a full set of threads again, so the pool could run more threads than it was given. ensure_started() now starts only the missing ones. The test uses a new test/unit/fault harness, a cut-down copy of Corosio's, that replaces pthread_create to make one thread fail. It runs on Linux only. Closes cppalliance#457
445edbc to
d6dd7c1
Compare
fix: start only the missing threads after a failed pool start
If a worker thread failed to start, the next post() started a full set of threads again, so the pool could run more threads than it was given. ensure_started() now starts only the missing ones.
The test uses a new test/unit/fault harness, a cut-down copy of Corosio's, that replaces pthread_create to make one thread fail. It runs on Linux only.
Closes #457