-
Notifications
You must be signed in to change notification settings - Fork 595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(test): use rate limit instead in background ddl test #13179
Conversation
526bec0
to
fd18cd1
Compare
ci/scripts/deterministic-it-test.sh
Outdated
@@ -16,7 +16,6 @@ mv target/ci-sim target/sim | |||
echo "--- Run integration tests in deterministic simulation mode" | |||
seq $TEST_NUM | parallel MADSIM_TEST_SEED={} NEXTEST_PROFILE=ci-sim \ | |||
cargo nextest run \ | |||
--no-capture \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5fccb81
to
ba06539
Compare
ba06539
to
a3c50d1
Compare
Seems like deterministic test failure is triggered by something else... It failed even when all |
Temporarily add 2 commits from #13178, so we can see if it resolves the failure. |
Codecov Report
@@ Coverage Diff @@
## main #13179 +/- ##
=======================================
Coverage 68.15% 68.16%
=======================================
Files 1506 1506
Lines 255354 255354
=======================================
+ Hits 174049 174061 +12
+ Misses 81305 81293 -12
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 8 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Use rate limit instead. After #13144 , thanks to @wangrunji0408's help, we support rate limit in madsim. Then in cancel tests, it was failing, even with rate limit, because the MV finished creating too fast before it could be cancelled.
So now we just ingest more data when creating the background MV which will be recovered, then cancelled.
We can now remove the env var in
no_shuffle_backfill
.Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.