-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: disk-stalled/log=true,data=true failed #52181
Comments
(roachtest).disk-stalled/log=true,data=true failed on release-19.1@7c03505d8daa19dee7f5f0268c9e728e38d4ba6d:
More
Artifacts: /disk-stalled/log=true,data=true See this test on roachdash |
(roachtest).disk-stalled/log=true,data=true failed on release-19.1@86b7271623ad797e9c42d5f7900a5cb424fed436:
More
Artifacts: /disk-stalled/log=true,data=true See this test on roachdash |
@irfansharif This looks like fallout from the |
This test doesn't make use of all the cockroach/pkg/cmd/roachtest/disk_stall.go Line 108 in 5102c97
Given our support policy, I'm just going to bump the minimum version this test expects to run. Another instance where #51897 seems the right direction we should be going towards. |
51959: backupccl: distribute RESTORE work using DistSQL r=dt,yuzefovich a=pbardea This commit replaces restore's old method of coordinating work on a single node to instead use DistSQL. It creates a 2 stage DistSQL flow. The first stage assigns chunks to SplitAndScatter processors which forward spans that they scattered to the second stage made up of the RestoreData processors which ingest the data. The SplitAndScatter processors attempt to send the work to the RestoreData colocated with the leaseholder of the span after the scattering. Release note: None. 52269: roachtest: correctly start crdb in acceptance/rapid_restart r=andreimatei a=andreimatei --start-single-node was needed. Without it, I think the test's killing of a node raced with that node dieing by itself, and sometimes the race resulted in `cockroach stop` first seeing the process but then `/bin/bash: line 8: kill: (16016) - No such proces` Fixes #52060 Release note: None 52273: roachtest: remove confusing "--- PASS" log lines r=andreimatei a=andreimatei Two workloads were printing PASS/FAIL lines from inside the predicates passed to Searcher.Search. This is really confusing when reading the test's output, because they don't correspond to the test's disposition. Release note: None 52343: roachtest: reflake (skip) disk-stalled test for release-19.1 r=irfansharif a=irfansharif Fixes #52181. This test doesn't make use of all the `roachtest start` smartness to figure out what sub-command to use and instead constructs the raw start command by hand. Given our support policy, let's just bump the minimum version this test expects to run. This feels like another instance where #51897 would be nice to have. Release note: None Co-authored-by: Paul Bardea <[email protected]> Co-authored-by: Andrei Matei <[email protected]> Co-authored-by: irfan sharif <[email protected]>
(roachtest).disk-stalled/log=true,data=true failed on release-19.1@f02b6abab9b5688fe06c28105f77c4be4f4c2623:
More
Artifacts: /disk-stalled/log=true,data=true
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: