backup: TestDataDriven_restore_on_fail_or_cancel_schema_objects failed

[github-actions]

backup.TestDataDriven_restore_on_fail_or_cancel_schema_objects failed on master @ e1c179459b31b4608d29f6d66e2108cb72143f46:

=== RUN   TestDataDriven_restore_on_fail_or_cancel_schema_objects
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestDataDriven_restore_on_fail_or_cancel_schema_objects1629364266
    test_log_scope.go:76: use -show-logs to present logs inline
    datadriven_test.go:467: Mock HTTP Storage "http://127.0.0.1:35171"
    test_server_shim.go:154: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
    datadriven_test.go:489: 
        /mnt/engflow/worker/work/0/exec/bazel-out/k8-fastbuild/bin/pkg/backup/backup_test_/backup_test.runfiles/com_github_cockroachdb_cockroach/pkg/backup/testdata/backup-restore/restore-on-fail-or-cancel-schema-objects:1:
          new-cluster name=s1 nodes=1 splits=1000
          ----
    testutils.go:307: no Invalid Descriptors
    panic.go:635: -- test log scope end --
test logs left over in: outputs.zip/logTestDataDriven_restore_on_fail_or_cancel_schema_objects1629364266
--- FAIL: TestDataDriven_restore_on_fail_or_cancel_schema_objects (10.23s)
=== RUN   TestDataDriven_restore_on_fail_or_cancel_schema_objects/restore-cleanup-type-back-references
    datadriven.go:262: 
        /mnt/engflow/worker/work/0/exec/bazel-out/k8-fastbuild/bin/pkg/backup/backup_test_/backup_test.runfiles/com_github_cockroachdb_cockroach/pkg/backup/testdata/backup-restore/restore-on-fail-or-cancel-schema-objects:99:
          exec-sql
          CREATE DATABASE d;
          CREATE TYPE d.ty AS ENUM ('hello');
          CREATE TABLE d.tb (x d.ty);
          INSERT INTO d.tb VALUES ('hello'), ('hello');
          ----
    datadriven.go:262: 
        /mnt/engflow/worker/work/0/exec/bazel-out/k8-fastbuild/bin/pkg/backup/backup_test_/backup_test.runfiles/com_github_cockroachdb_cockroach/pkg/backup/testdata/backup-restore/restore-on-fail-or-cancel-schema-objects:106:
          exec-sql
          BACKUP TABLE d.tb INTO 'nodelocal://1/bar';
          ----
    datadriven.go:262: 
        /mnt/engflow/worker/work/0/exec/bazel-out/k8-fastbuild/bin/pkg/backup/backup_test_/backup_test.runfiles/com_github_cockroachdb_cockroach/pkg/backup/testdata/backup-restore/restore-on-fail-or-cancel-schema-objects:111:
          exec-sql
          DROP TABLE d.tb;
          ----
    datadriven.go:262: 
        /mnt/engflow/worker/work/0/exec/bazel-out/k8-fastbuild/bin/pkg/backup/backup_test_/backup_test.runfiles/com_github_cockroachdb_cockroach/pkg/backup/testdata/backup-restore/restore-on-fail-or-cancel-schema-objects:115:
          exec-sql
          SET CLUSTER SETTING jobs.debug.pausepoints = 'restore.after_publishing_descriptors';
          ----
    datadriven_test.go:521: 
        	Error Trace:	pkg/backup/datadriven_test.go:521
        	            				pkg/backup/datadriven_test.go:851
        	            				external/com_github_cockroachdb_datadriven/datadriven.go:119
        	            				external/com_github_cockroachdb_datadriven/datadriven.go:340
        	            				external/com_github_cockroachdb_datadriven/datadriven.go:345
        	            				external/com_github_cockroachdb_datadriven/datadriven.go:214
        	            				external/com_github_cockroachdb_datadriven/datadriven.go:262
        	            				external/com_github_cockroachdb_datadriven/test_interface.go:27
        	Error:      	Expect "pq: aborted in DistSender: result is ambiguous: context canceled" to match "pause point .* hit$"
        	Test:       	TestDataDriven_restore_on_fail_or_cancel_schema_objects/restore-cleanup-type-back-references
--- FAIL: TestDataDriven_restore_on_fail_or_cancel_schema_objects/restore-cleanup-type-back-references (5.66s)

Parameters:

• attempt=1
• run=1
• shard=16

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-51336

[github-actions]

We have marked this test failure issue as stale because it has been
inactive for 1 month. If this failure is still relevant, removing the
stale label or adding a comment will keep it active. Otherwise,
we'll close it in 5 days to keep the test failure queue tidy.