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

ccl/backupccl: TestDataDriven_procedures failed #124392

Closed
cockroach-teamcity opened this issue May 19, 2024 · 1 comment
Closed

ccl/backupccl: TestDataDriven_procedures failed #124392

cockroach-teamcity opened this issue May 19, 2024 · 1 comment
Labels
branch-master Failures 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-disaster-recovery

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented May 19, 2024

ccl/backupccl.TestDataDriven_procedures failed on master @ 93ad913106b6f0f6ec98bc2cfa788ff6d8085bd4:

=== RUN   TestDataDriven_procedures
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestDataDriven_procedures2886408359
    test_log_scope.go:81: use -show-logs to present logs inline
    datadriven_test.go:445: Mock HTTP Storage "http://127.0.0.1:35341"
    test_server_shim.go:157: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.
    datadriven.go:144: 
        /var/lib/engflow/worker/work/3/exec/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/procedures:2:
        new-cluster [1 args]
        <no input to command>
        ----
    datadriven.go:144: 
        /var/lib/engflow/worker/work/3/exec/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/procedures:5:
         CREATE DATABASE db1;
        USE db1;
        CREATE SCHEMA sc1;
        CREATE TABLE sc1.tbl1(a INT PRIMARY KEY);
        CREATE TYPE sc1.enum1 AS ENUM('Good');
        CREATE SEQUENCE sc1.sq1;
        CREATE PROCEDURE sc1.p1(a sc1.enum1) LANGUAGE SQL AS $$
          SELECT a FROM sc1.tbl1;
          SELECT 'Good'::sc1.enum1;
          SELECT nextval('sc1.sq1');
        $$;
        CREATE SCHEMA sc2;
        CREATE TABLE sc2.tbl2(a INT PRIMARY KEY);
        CREATE PROCEDURE sc2.p2(i INT) LANGUAGE SQL AS $$
          INSERT INTO sc2.tbl2 VALUES (i)
        $$;
        expected:
        
        found:
        pq: type with ID 111 does not exist
    testutils.go:290: no Invalid Descriptors
    testutils.go:267: Warning: Could not check for invalid descriptors: sql: database is closed
    panic.go:626: -- test log scope end --
test logs left over in: outputs.zip/logTestDataDriven_procedures2886408359
--- FAIL: TestDataDriven_procedures (1.19s)

Parameters:

  • attempt=1
  • run=16
  • shard=42
Help

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

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-38865

@cockroach-teamcity cockroach-teamcity added branch-master Failures 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-disaster-recovery labels May 19, 2024
@DrewKimball
Copy link
Collaborator

Dupe of #122353.

Disaster Recovery Backlog automation moved this from Backlog to Done May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures 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-disaster-recovery
Development

No branches or pull requests

2 participants