-
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: decommission/mixed-versions failed #55798
Comments
This is expected. ccd12ed needs to be picked up by release-20.1 (and used in roachtest) for this test to pass. |
(roachtest).decommission/mixed-versions failed on master@61c96aaca632dfba5154d55d82c5af0732053b72:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash |
Since this is a mixed-version test, the new failure is probably fallout from the version on master now being 21.1. |
(roachtest).decommission/mixed-versions failed on master@be84ae4a59e6a5e50694c1756e05b0ba7c3a54d8:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash |
(roachtest).decommission/mixed-versions failed on master@f2b53d1080f1ccc503263dd178ee31b4878d2360:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash |
(roachtest).decommission/mixed-versions failed on master@f2b53d1080f1ccc503263dd178ee31b4878d2360:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash |
(roachtest).decommission/mixed-versions failed on master@df21e5065a79d1dd5b0fd76018724dd26660beb2:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash |
The test was fully decommissioning and then recommissioning nodes, which does no longer work now that the master branch is 21.1 and thus the predecessor version in this test is 20.2, which does know about fully decommissioning (decommission attempts run via 20.1 nodes never set the status to fully decommissioned, so we got away with it so far). Pare down the test so that it carries out one random partial and full decommission cycle alongside a partial version upgrade, which is reasonably all we can do unless we want to get into the business of wiping and re-adding nodes to the cluster in this test, which I don't think we do as it doesn't work well with the step-driven format this test is using. Fixes cockroachdb#55798. Release note: None
(roachtest).decommission/mixed-versions failed on master@2d34be73030a0d114b84fc2785672eda072c5a50:
More
Artifacts: /decommission/mixed-versions See this test on roachdash |
(roachtest).decommission/mixed-versions failed on master@6b254f2d4a8e1470c1a7d5bd7c3f746d69de0797:
More
Artifacts: /decommission/mixed-versions See this test on roachdash |
(roachtest).decommission/mixed-versions failed on master@5d8f1d3dbc356573a1fb2d1d6bf564bf0370daff:
More
Artifacts: /decommission/mixed-versions See this test on roachdash |
(roachtest).decommission/mixed-versions failed on master@b4bf42c4fe10155717ac48f2e68ad8b501ca0b1a:
More
Artifacts: /decommission/mixed-versions See this test on roachdash |
56568: roachtest: de-flake decommission/mixed-versions r=andreimatei a=tbg The test was fully decommissioning and then recommissioning nodes, which does no longer work now that the master branch is 21.1 and thus the predecessor version in this test is 20.2, which does know about fully decommissioning (decommission attempts run via 20.1 nodes never set the status to fully decommissioned, so we got away with it so far). Pare down the test so that it carries out one random partial and full decommission cycle alongside a partial version upgrade, which is reasonably all we can do unless we want to get into the business of wiping and re-adding nodes to the cluster in this test, which I don't think we do as it doesn't work well with the step-driven format this test is using. Fixes #55798. Release note: None Co-authored-by: Tobias Grieger <[email protected]>
(roachtest).decommission/mixed-versions failed on master@1d46df77dbd8721cccf508fb5ed498f3de78022c:
More
Artifacts: /decommission/mixed-versions
Related:
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: