-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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: schemachange/mixed-versions-compat failed #112376
Comments
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ 96ab72f95759b6a40c5c2bc67c37101f3590ddd3:
Parameters: Same failure on other branches
|
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ fbbf7ef7869c725a73663f13347d38a413b33abd:
Parameters: Same failure on other branches
|
This error appears ~100 times. They all reference
|
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ 45f6344a2fc7d2d52f410e1ecad98f8c928cfeea:
Parameters: Same failure on other branches
|
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ d8946998badb1562fa60318f3b24a7ece5483ddd:
Parameters: Same failure on other branches
|
112456: testcluster: clone Settings for each server r=RaduBerinde a=RaduBerinde #### testserver: unembed Settings, RaftConfig There is no reason these should be embedded. Epic: none Release note: None #### testcluster: clone Settings for each server Currently there are many tests where multi-node test clusters share the same `*Settings` object. This is problematic - on one hand, it can make some test failures very hard to debug, and on the other hand, we are missing out on testing more realistic scenarios where nodes in a cluster don't magically have their settings in sync. This change adds some test-only code to clone the Settings object. Fixes #112395 Release note: None 112623: scplan: Remove extra rule in `rule/release_23_1` directory r=Xiang-Gu a=Xiang-Gu We removed a few rule changes present in `rule/release_23_1` directory on master but not present in `rule/current` on `release-23.1` branch. It should have been excluded but was mistakenly added in PR #103349. Informs #112376 Release note: None Co-authored-by: Radu Berinde <[email protected]> Co-authored-by: Xiang Gu <[email protected]>
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ fbee0764a4a2953a1178ea8c3edd352545caa227:
Parameters: Same failure on other branches
|
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ cacb4f39d1f88cde17d1abffcbbeb611adc440f8:
Parameters: Same failure on other branches
|
Copying @Xiang-Gu's observations:
|
That's probably since #112271 just bumped the version to 24.1 |
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ 07915532f9a7def000127029c667c3a91ce90e47:
Parameters: |
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ 4f26bd1b3f90c4f1c9dd530f9692e8125207b4c8:
Parameters: |
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ 4f26bd1b3f90c4f1c9dd530f9692e8125207b4c8:
Parameters: |
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ f3c7285d89afd63b2f7cae762638b86f237c1d72:
Parameters: |
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ 8315a4bc997fb8b8d679079e14d6d7ca94d53bc6:
Parameters: |
roachtest.schemachange/mixed-versions-compat failed with artifacts on master @ f2bfa2a140fa302e79c9d31b84b944a6ac5e98ce:
Parameters:
ROACHTEST_arch=amd64
,ROACHTEST_cloud=gce
,ROACHTEST_cpu=4
,ROACHTEST_encrypted=false
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
This test on roachdash | Improve this report!
Jira issue: CRDB-32381
The text was updated successfully, but these errors were encountered: