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

pkg/ccl/logictestccl/tests/3node-tenant/3node-tenant_test: TestTenantLogic_temp_table failed #140552

Closed
cockroach-teamcity opened this issue Feb 5, 2025 · 1 comment · Fixed by #140607
Assignees
Labels
branch-release-24.1 Used to mark GA and release blockers, technical advisories, and bugs for 24.1 branch-release-24.2 Used to mark GA and release blockers, technical advisories, and bugs for 24.2 branch-release-24.3 Used to mark GA and release blockers, technical advisories, and bugs for 24.3 branch-release-25.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Feb 5, 2025

pkg/ccl/logictestccl/tests/3node-tenant/3node-tenant_test.TestTenantLogic_temp_table failed with artifacts on release-25.1 @ 6a2a5553f517db8a484860f043bbbbeefc19829e:

=== RUN   TestTenantLogic_temp_table
    test_log_scope.go:165: test logs captured to: /artifacts/tmp/_tmp/b5b01cdf18c474581f3b037c806fc673/logTestTenantLogic_temp_table1794324725
    test_log_scope.go:76: use -show-logs to present logs inline
    logic.go:1574: apply knob opt logictest.knobOptSynchronousEventLog
    logic.go:1649: apply knob opt logictest.knobOptSynchronousEventLog to tenant
    logic.go:1649: apply knob opt logictest.knobOptSynchronousEventLog to tenant
    logic.go:1649: apply knob opt logictest.knobOptSynchronousEventLog to tenant
[22:11:17] setting distsql_workmem='83997B';
[22:11:17] setting distsql_workmem='83997B';
    logic.go:4425: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/b5b01cdf18c474581f3b037c806fc673/logTestTenantLogic_temp_table1794324725
--- FAIL: TestTenantLogic_temp_table (11.33s)
=== RUN   TestTenantLogic_temp_table/temporary_views
    logictestbase.go:542: statement/query skipped with reason: unsupported configuration 3node-tenant, statement/query only supports weak-iso-level-configs (no issue given)
    logic.go:2273: 
         
        /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/30688/execroot/com_github_cockroachdb_cockroach/bazel-out/aarch64-fastbuild/bin/pkg/ccl/logictestccl/tests/3node-tenant/3node-tenant_test_/3node-tenant_test.runfiles/com_github_cockroachdb_cockroach/pkg/sql/logictest/testdata/logic_test/temp_table:171: 
        expected success, but found
        (40001) restart transaction: TransactionRetryWithProtoRefreshError: TransactionAbortedError(ABORT_REASON_CLIENT_REJECT): "sql txn" meta={id=3e05c5d8 key=/Tenant/10/Table/3/1/120/2/1 iso=Serializable pri=0.01488738 epo=0 ts=1738793480.534027617,0 min=1738793480.534027617,0 seq=26} lock=true stat=PENDING rts=1738793480.534027617,0 wto=false gul=1738793481.034027617,0
[22:11:25] --- done: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/30688/execroot/com_github_cockroachdb_cockroach/bazel-out/aarch64-fastbuild/bin/pkg/ccl/logictestccl/tests/3node-tenant/3node-tenant_test_/3node-tenant_test.runfiles/com_github_cockroachdb_cockroach/pkg/sql/logictest/testdata/logic_test/temp_table with config 3node-tenant: 38 tests, 1 failures
[22:11:26] --- total progress: 38 statements
--- total: 38 tests, 1 failures
    --- FAIL: TestTenantLogic_temp_table/temporary_views (5.80s)
Help

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

This test on roachdash | Improve this report!

Jira issue: CRDB-47228

@cockroach-teamcity cockroach-teamcity added branch-release-25.1 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-sql-queries SQL Queries Team labels Feb 5, 2025
@github-project-automation github-project-automation bot moved this to Triage in SQL Queries Feb 5, 2025
@yuzefovich yuzefovich added T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) and removed release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-sql-queries SQL Queries Team labels Feb 6, 2025
@yuzefovich yuzefovich removed this from SQL Queries Feb 6, 2025
@rafiss rafiss self-assigned this Feb 6, 2025
@craig craig bot closed this as completed in #140607 Feb 6, 2025
@craig craig bot closed this as completed in 215d16b Feb 6, 2025
Copy link

blathers-crl bot commented Feb 6, 2025

Based on the specified backports for linked PR #140607, I applied the following new label(s) to this issue: branch-release-24.1, branch-release-24.2, branch-release-24.3. Please adjust the labels as needed to match the branches actually affected by this issue, including adding any known older branches.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@blathers-crl blathers-crl bot added branch-release-24.1 Used to mark GA and release blockers, technical advisories, and bugs for 24.1 branch-release-24.2 Used to mark GA and release blockers, technical advisories, and bugs for 24.2 branch-release-24.3 Used to mark GA and release blockers, technical advisories, and bugs for 24.3 labels Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-release-24.1 Used to mark GA and release blockers, technical advisories, and bugs for 24.1 branch-release-24.2 Used to mark GA and release blockers, technical advisories, and bugs for 24.2 branch-release-24.3 Used to mark GA and release blockers, technical advisories, and bugs for 24.3 branch-release-25.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants