Skip to content
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: perturbation/full/decommission failed #140784

Closed
cockroach-teamcity opened this issue Feb 8, 2025 · 3 comments
Closed

roachtest: perturbation/full/decommission failed #140784

cockroach-teamcity opened this issue Feb 8, 2025 · 3 comments
Labels
A-testing Testing tools and infrastructure branch-release-24.3.5-rc C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-kv KV Team X-duplicate Closed as a duplicate of another issue.

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Feb 8, 2025

roachtest.perturbation/full/decommission failed with artifacts on release-24.3.5-rc @ 435e0d8a9286bf0e4bc899ebf9eadbb3ce1440bb:

(assertions.go:363).Fail: 
	Error Trace:	pkg/cmd/roachtest/tests/admission_control_latency.go:904
	            				pkg/cmd/roachtest/test_runner.go:1301
	            				src/runtime/asm_amd64.s:1695
	Error:      	Should be true
	Test:       	perturbation/full/decommission
	Messages:   	FAILURE: follower-read  : Increase 5.5461 > 5.0000 BASE: 5.734018ms SCORE: 31.801371ms
	            	
	            	FAILURE: read           : Increase 5.0289 > 5.0000 BASE: 6.288029ms SCORE: 31.621662ms
(require.go:1950).True: FailNow called
test artifacts and logs in: /artifacts/perturbation/full/decommission/run_1

Parameters:

  • arch=amd64
  • cloud=gce
  • coverageBuild=false
  • cpu=16
  • encrypted=false
  • fs=ext4
  • localSSD=true
  • runtimeAssertionsBuild=false
  • ssd=2
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

/cc @cockroachdb/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-47367

@cockroach-teamcity cockroach-teamcity added branch-release-24.3.5-rc C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-kv KV Team labels Feb 8, 2025
@tbg tbg removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Feb 10, 2025
@tbg
Copy link
Member

tbg commented Feb 10, 2025

perturbation test -> not a release blocker.

@tbg
Copy link
Member

tbg commented Feb 10, 2025

Also duplicate of #139978.

@tbg tbg added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. X-duplicate Closed as a duplicate of another issue. A-testing Testing tools and infrastructure labels Feb 10, 2025
@tbg
Copy link
Member

tbg commented Feb 10, 2025

Closing since it's on 24.3.5-rc and unlikely to reoccur there.

@tbg tbg closed this as completed Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testing Testing tools and infrastructure branch-release-24.3.5-rc C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-kv KV Team X-duplicate Closed as a duplicate of another issue.
Projects
None yet
Development

No branches or pull requests

2 participants