-
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/cgroup/read-write/logs-too=true failed #101904
Comments
roachtest.disk-stalled/cgroup/read-write/logs-too=true failed with artifacts on release-23.1.0 @ 06fea49dd3b665758ff016a38622e3ce0f1ccfc5:
Parameters: |
We've seen two of these failures on the release-23.1.0 branch but none on master. The transactions per second post-stall was just a hair shy of half the pre-stall transactions-per-second. I'll run this a few times on the .0 branch today to see if it's possible there's some kind of regression here. It might be the case that the roachtest's post-recoveryTPS threshold is still too aggressive. |
roachtest.disk-stalled/cgroup/read-write/logs-too=true failed with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:
Parameters: Same failure on other branches
|
roachtest.disk-stalled/cgroup/read-write/logs-too=true failed with artifacts on release-23.1.0 @ 4524616140097c0f6b921e5d1e94ebd405f0809f:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=4
,ROACHTEST_encrypted=false
,ROACHTEST_fs=ext4
,ROACHTEST_localSSD=false
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-27302
The text was updated successfully, but these errors were encountered: