ROX-36975: Fix race - #22827
ROX-36975: Fix race#22827
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 10 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe queue test directly signals ChangesQueue signaling validation
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The test isolates stale wakeups and verifies subsequent item delivery, so the change is mergeable. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #22827 +/- ##
==========================================
- Coverage 51.82% 51.79% -0.04%
==========================================
Files 2901 2901
Lines 182819 182819
==========================================
- Hits 94755 94691 -64
- Misses 79777 79822 +45
- Partials 8287 8306 +19
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
🚀 Build Images ReadyImages are ready for commit 51600ba. To use with deploy scripts: export MAIN_IMAGE_TAG=5.0.x-302-g51600ba89f |
a6e66cd to
e5b52e8
Compare
e5b52e8 to
b103d8b
Compare
|
@mtodor: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
Failed e2e tests are not related to: |
Description
The problem we are facing is that we expect that
PullafterPushin main test routine will be executed, but we have another routine (started consumer) waiting on signal and there can be a race where consumer picks item before main routine.Simple way to reproduce:
The purpose of this test is to ensure that empty queue with triggered nonEmpty signal will not cause spin-loop.
Suggested fix
Instead of triggering nonEmpty signal with push->pull - we will trigger it directly.
Related to: #22456
User-facing documentation
Testing and quality
Automated testing
How I validated my change