-
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: scbench/randomload/nodes=3/ops=10000/conc=20 failed #56230
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The schemachange after write error will be anticipated and handled after #56184 is merged in |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
56184: workload/schemachange: screen for errors in operations r=ajwerner a=jayshrivastava workload/schemachange: screen for errors in operations These changes add error screening for the following (#56119): - createEnum op - createSchema op - dropColumn op - dropColumnDefault op - dropColumnNotNull op - dropSchema op - renameColumn op - renameTable op - renameView op Also, errors caused by schema changes after writes in the same txn are handled (#56230) It also resolves a bug related to ambiguity in column names that was caused by views/tables referencing the same columns (#56235). Co-authored-by: Jayant Shrivastava <[email protected]>
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
roachtest.scbench/randomload/nodes=3/ops=10000/conc=20 failed with artifacts on master @ 4c65a10fea9762b97559c1a488cd5b96cb2cf81a:
Same failure on other branches
|
roachtest.scbench/randomload/nodes=3/ops=10000/conc=20 failed with artifacts on master @ 1d13605e2aeb1af0a5536f1f460e45d557119128:
Same failure on other branches
|
roachtest.scbench/randomload/nodes=3/ops=10000/conc=20 failed with artifacts on master @ a7449866f3229872d92e1de973e209838f07de35:
Same failure on other branches
|
See cockroachdb#56230. I don't usually go around skipping other team's tests, but this one regularly times out, occupying a cluster for 10h, and possibly contributing to timeouts of the roachtest suite as a whole. Looking at the failure issue it's also clear that the owning team is not deriving any signal whatsoever from this test at the moment. Release note: None
Skipping this test in #76970. |
76970: roachtest: skip scbench r=otan a=tbg See #56230. I don't usually go around skipping other team's tests, but this one regularly times out, occupying a cluster for 10h, and possibly contributing to timeouts of the roachtest suite as a whole. Looking at the failure issue it's also clear that the owning team is not deriving any signal whatsoever from this test at the moment. Release note: None Co-authored-by: Tobias Grieger <[email protected]>
See cockroachdb#56230. I don't usually go around skipping other team's tests, but this one regularly times out, occupying a cluster for 10h, and possibly contributing to timeouts of the roachtest suite as a whole. Looking at the failure issue it's also clear that the owning team is not deriving any signal whatsoever from this test at the moment. Release note: None
See cockroachdb#56230. I don't usually go around skipping other team's tests, but this one regularly times out, occupying a cluster for 10h, and possibly contributing to timeouts of the roachtest suite as a whole. Looking at the failure issue it's also clear that the owning team is not deriving any signal whatsoever from this test at the moment. Release note: None
Retriaging to either unskip or remove. I can't remember why I closed this. |
As per the convo in https://cockroachlabs.slack.com/archives/C04N0AS14CT/p1686856008458059, let's just remove this test. |
105771: sql: increase time buffer for TestCaptureIndexUsageStats r=gtr a=gtr Note to reviewers: this builds on top of #105755, please only consider the second commit. Previously, the `pkg/sql/scheduleslogging/TestCaptureIndexUsageStats` test failed on CI, despire passing locally. This commit increases the time buffer from 3s to 4s to give a larger tolerance for non-determinism. Fixes #102980 Release note: None 105919: roachtest: Delete scbench randomload test r=rafiss a=rimadeodhar This test has been skipped for a year and based on the history of the test hasn't been providing much value. We can delete it now. Random schema change testing is covered by schemachange/randomload. Epic: none Fixes: #56230 Release note: None Co-authored-by: gtr <[email protected]> Co-authored-by: rimadeodhar <[email protected]>
(jayshrivastava) resolved by #56379, but there still some different errors left to solve in the comments
(roachtest).scbench/randomload/nodes=3/ops=10000/conc=20 failed on master@e25ee7ad4bcdeda49f40eb52c24d2d1b1aa67a86:
More
Artifacts: /scbench/randomload/nodes=3/ops=10000/conc=20
See this test on roachdash
powered by pkg/cmd/internal/issues
Jira issue: CRDB-2965
The text was updated successfully, but these errors were encountered: