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

kv/kvnemesis: TestKVNemesisSingleNode_ReproposalChaos failed #118624

Closed
cockroach-teamcity opened this issue Feb 2, 2024 · 0 comments · Fixed by #118673
Closed

kv/kvnemesis: TestKVNemesisSingleNode_ReproposalChaos failed #118624

cockroach-teamcity opened this issue Feb 2, 2024 · 0 comments · Fixed by #118673
Assignees
Labels
A-testing Testing tools and infrastructure branch-master Failures and bugs on the master branch. 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-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
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Feb 2, 2024

kv/kvnemesis.TestKVNemesisSingleNode_ReproposalChaos failed on master @ fce4d4723519bc4ca6e9ef5da0ae19960c84752c:

Fatal error:

panic: test timed out after 4m57s
running tests:
	TestKVNemesisSingleNode_ReproposalChaos (4m43s)

Stack:

goroutine 66149 [running]:
testing.(*M).startAlarm.func1()
	GOROOT/src/testing/testing.go:2259 +0x3b9
created by time.goFunc
	GOROOT/src/time/sleep.go:176 +0x2d
Log preceding fatal error

=== RUN   TestKVNemesisSingleNode_ReproposalChaos
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestKVNemesisSingleNode_ReproposalChaos114964883
    test_log_scope.go:81: use -show-logs to present logs inline
    kvnemesis_test.go:328: seed: 8510271265405000902
    kvnemesis_test.go:235: kvnemesis logging to /var/lib/engflow/worker/work/0/exec/bazel-out/k8-fastbuild/testlogs/pkg/kv/kvnemesis/kvnemesis_test/run_7_of_30/test.outputs/kvnemesis2524568587

Parameters:

  • attempt=1
  • run=7
  • shard=1
Help

See also: How To Investigate a Go Test Failure (internal)

Same failure on other branches

/cc @cockroachdb/kv

This test on roachdash | Improve this report!

Jira issue: CRDB-35811

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). 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 2, 2024
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone Feb 2, 2024
@arulajmani arulajmani self-assigned this Feb 2, 2024
craig bot pushed a commit that referenced this issue Feb 3, 2024
116958: rpc: move system ranges to system RPC class r=lunevalex a=lunevalex

Move all the ranges between /Min and /System/tsd to use the default RPC class. This will allow for
isolation from network congestion for all system
ranges, which crucial for the stability of the system.

Fixes: #111239

Release note: None

118555: workflows: run UI lint and test in experimental github actions build r=rail a=rickystewart

Epic: [CRDB-8308](https://cockroachlabs.atlassian.net/browse/CRDB-8308)
Release note: None

118581: roachtest: stop ignoring activerecord failures r=rafiss a=rafiss

The adapter has been stabilized, so we should enable this test again.

fixes #108938
Release note: None

118659: tests: use `test.Pool` instead of `Pool` r=rail a=rickystewart

This tells Bazel to use the pool only for test actions instead of the compile action associated with each test.

Epic: CRDB-8308
Release note: None

118673: kv: mark kvnemesis tests as "large" sized r=nvanbenschoten a=arulajmani

We've recently seen these time out exclusively on eng flow. In all those instances, we can see the test is making some progress from the stack traces -- it's slow though. We mark KVNemesis tests as large, which in turn bumps their timeout in CI.

Closes #118624
Closes #118005

Release note: None

118675: ui: remove warning when auto refresh enable r=maryliag a=maryliag

The warning being displayed about old active executions was not bein properly removed when the auto refresh was turned back on.
This commit fixes this for both Statements and Transactions pages, on Active Executions.

Fixes CRDB-35837

https://www.loom.com/share/76b57eba17ab44758fe81f178f07fecd

Release note (ui change): Properly remove warning of old date on Active Executions when auto refresh is enabled.

Co-authored-by: Alex Lunev <[email protected]>
Co-authored-by: Ricky Stewart <[email protected]>
Co-authored-by: Rafi Shamim <[email protected]>
Co-authored-by: Arul Ajmani <[email protected]>
Co-authored-by: maryliag <[email protected]>
@craig craig bot closed this as completed in 174bb2b Feb 3, 2024
@kvoli kvoli added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. A-testing Testing tools and infrastructure labels Feb 5, 2024
wenyihu6 pushed a commit to wenyihu6/cockroach that referenced this issue Feb 21, 2024
We've recently seen these time out exclusively on eng flow. In all
those instances, we can see the test is making some progress from
the stack traces -- it's slow though. We mark KVNemesis tests as
large, which in turn bumps their timeout in CI.

Closes cockroachdb#118624
Closes cockroachdb#118005

Release note: None
@github-project-automation github-project-automation bot moved this to Closed in KV Aug 28, 2024
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-master Failures and bugs on the master branch. 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-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
Projects
No open projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

3 participants