ccl/sqlproxyccl/tenant: TestResume failed #106571
Assignees
Labels
branch-release-23.1
Used to mark GA and release blockers, technical advisories, and bugs for 23.1
C-test-failure
Broken test (automatically or manually discovered).
O-robot
Originated from a bot.
T-serverless
Milestone
Comments
cockroach-teamcity
added
branch-release-23.1
rafiss
removed
the
T-sql-foundations
|
ccl/sqlproxyccl/tenant.TestResume failed with artifacts on release-23.1 @ 7bfb0ce4cf4e5d3c6c51fd97ced445f4c05fbdc8: Parameters: |
|
ccl/sqlproxyccl/tenant.TestResume failed with artifacts on release-23.1 @ 8897f4d13a030381997ff30aeaf633a9f8e87340: Parameters: |
|
ccl/sqlproxyccl/tenant.TestResume failed with artifacts on release-23.1 @ aaedb3dd0d97097cff7afeb2532c6265d3d62818: Parameters: |
|
ccl/sqlproxyccl/tenant.TestResume failed with artifacts on release-23.1 @ 8b970683af4630cbb30b4c92f0be86cfadd97993: Parameters: |
craig bot
pushed a commit
that referenced
this issue
Aug 1, 2023
107294: ttl: show table name for jobs in SHOW SCHEDULES r=chrisseto a=chrisseto Previously, `SHOW SCHEDULES` would only show a table's ID for row level TTL jobs. For the convenience of debugging, this commit upgrades the `label` column to contain the table's name instead of its ID. Rather than performing table name resolution at query time, the job name is set at creation time and updated by the schema change during table renames. This minimizes the likelihood of `SHOW SCHEDULES` being rendered unusable when a cluster is in an unstable state. Epic: CRDB-18322 Fixes: #93774 107316: sqlproxyccl: simplify NewSubStopper r=JeffSwenson a=JeffSwenson The lock in NewSubStopper caused lock ordering warnings when run under deadlock detection. The justification given for the lock's existence is wrong. If a closer is added to an already stopped stopper, the closer is called immediately. Release note: None Part of: #106571 107941: storage: don't import `testing` for `DisableMetamorphicSimpleValueEncoding` r=erikgrinaker a=erikgrinaker We shouldn't link `testing` in binaries. Epic: none Release note: None 107950: testutils: fix determinism in random predecessor history tests r=jayshrivastava a=renatolabs Previously, the `rng` instance used by the tests was initialized once in the `var` block. That meant that every assertion that relied on that rng was order-dependent: running a single test in that file in isolation would lead to failed assertions. This commit ensures that every test resets the rng before making any assertions, guaranteeing we get the same values regardless of execution order. Epic: none Release note: None Co-authored-by: Chris Seto <[email protected]> Co-authored-by: Jeff <[email protected]> Co-authored-by: Erik Grinaker <[email protected]> Co-authored-by: Renato Costa <[email protected]>
blathers-crl bot
pushed a commit
that referenced
this issue
Aug 1, 2023
The lock in NewSubStopper caused lock ordering warnings when run under deadlock detection. The justification given for the lock's existence is wrong. If a closer is added to an already stopped stopper, the closer is called immediately. Release note: None Fixes: #106571
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ccl/sqlproxyccl/tenant.TestResume failed with artifacts on release-23.1 @ 17d14efc67f680945eb3a38dd0840ec70f766709:
Parameters:
TAGS=bazel,gss,deadlockHelp
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-29621
The text was updated successfully, but these errors were encountered: