-
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
ccl/kvccl/kvtenantccl: TestTenantUpgradeFailure failed #98555
Comments
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ 4215b86090794a78649aa4463c7bf95d74c57c37:
Parameters: |
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ ca5ae38022c45aec434fa1dd98f58c76e37643f5:
|
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ 9b43dc50d468171bc9919dc684b7274b63e13da2: Fatal error:
Stack:
Log preceding fatal error
Parameters: |
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ 9b43dc50d468171bc9919dc684b7274b63e13da2:
Parameters: |
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ 9b43dc50d468171bc9919dc684b7274b63e13da2:
Parameters: |
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ d68f5cdfb25476aaf874bff0bb6515eba02efcd2: Fatal error:
Stack:
Log preceding fatal error
Parameters: |
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ d68f5cdfb25476aaf874bff0bb6515eba02efcd2:
Parameters: |
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ d68f5cdfb25476aaf874bff0bb6515eba02efcd2:
Parameters: |
|
Added GA-blocker since this is new, just to make sure it gets looked at |
This stack trace tells me it's overlapping with @healthy-pod 's recent work and the assignment of tracers to different contexts. @abarganier could you perhaps help Ahmad investigating this?
|
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ f0489334a0ee6980a9d365b361d2fce4b2cdc05b: Fatal error:
Stack:
Log preceding fatal error
Parameters: |
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ f0489334a0ee6980a9d365b361d2fce4b2cdc05b:
Parameters: |
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ f0489334a0ee6980a9d365b361d2fce4b2cdc05b: Fatal error:
Stack:
Log preceding fatal error
Parameters: |
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ 0a4b38348c6d4874a619126e5273829d7a5bc894:
|
Refs: cockroachdb#98555 Reason: flaky test Generated by bin/skip-test. Release justification: non-production code changes Release note: None Epic: None
98853: ccl/kvccl/kvtenantccl: skip TestTenantUpgradeFailure r=smg260 a=smg260 Refs: #98555 Reason: flaky test Generated by bin/skip-test. Release justification: non-production code changes Release note: None Epic: None Co-authored-by: Miral Gadani <[email protected]>
I have analyzed the test and I am confident this is not a GA blocker, so I'm removing the label. However we still need to investigate it further. |
Update: This change fixes the test by bumping Unanswered question: |
The code change unskips `TestTenantUpgradeFailure` after making the following changes to fix it: 1. Bump `slinstance.DefaultTTL.Override` from 3s to 15s 2. Ensure v2 isn't higher than `TestingBinaryVersion` It also updates the registry override to let the test run all migrations. Release note: None Epic: none Closes cockroachdb#98555
101956: ugpradeccl: fix and unskip `TestTenantUpgradeFailure` r=knz a=healthy-pod The code change unskips `TestTenantUpgradeFailure` after making the following changes to fix it: 1. Bump `slinstance.DefaultTTL.Override` from 3s to 15s 2. Ensure v2 isn't higher than `TestingBinaryVersion` It also updates the registry override to let the test run all migrations. Release note: None Epic: none Closes #98555 Co-authored-by: healthy-pod <[email protected]>
ccl/kvccl/kvtenantccl.TestTenantUpgradeFailure failed with artifacts on master @ 4215b86090794a78649aa4463c7bf95d74c57c37:
Parameters:
TAGS=bazel,gss
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-25327
Epic CRDB-27931
The text was updated successfully, but these errors were encountered: