fix: AdaptiveTimeout MinTimeout test needs to be more resource-aware for github runners - BED-7153#281
Conversation
…for github runners
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughA test in the AdaptiveTimeout suite was modified to remove a 50ms delay and simplify its assertions. The test now uses Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description
Github runners are too efficient with concurrency resources for
Task.Delay()code in parallelized tests to be particularly timely.Motivation and Context
https://specterops.atlassian.net/browse/BED-7153
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist:
Summary by CodeRabbit