sql/catalog/externalcatalog: TestExtractIngestExternalCatalog failed

[github-actions]

sql/catalog/externalcatalog.TestExtractIngestExternalCatalog failed on master @ f18cf53e67c1c6eab453eb7be40743b86cdbf349:

=== RUN   TestExtractIngestExternalCatalog
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestExtractIngestExternalCatalog1496863546
    test_log_scope.go:76: use -show-logs to present logs inline
    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.
    external_catalog_test.go:174: -- test log scope end --
--- FAIL: TestExtractIngestExternalCatalog (6.98s)
=== RUN   TestExtractIngestExternalCatalog/udt
    external_catalog_test.go:154: error scanning '&{0xc008fa9200 <nil>}': pq: referenced descriptor ID 109: looking up ID 109: descriptor not found
    --- FAIL: TestExtractIngestExternalCatalog/udt (0.22s)

Parameters:

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

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

[msbutler]

@fqazi this looks like a strange flake. i think it suggests that certain descriptors may have actually gotten written in the WriteDescriptors call?

[github-actions]

sql/catalog/externalcatalog.TestExtractIngestExternalCatalog failed on master @ 6ac05b1ff123d0fd21227433f67a2c3457e5ac64:

=== RUN   TestExtractIngestExternalCatalog
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestExtractIngestExternalCatalog2551319749
    test_log_scope.go:76: use -show-logs to present logs inline
    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.
    external_catalog_test.go:174: -- test log scope end --
test logs left over in: outputs.zip/logTestExtractIngestExternalCatalog2551319749
--- FAIL: TestExtractIngestExternalCatalog (5.12s)
=== RUN   TestExtractIngestExternalCatalog/udt
    external_catalog_test.go:154: error scanning '&{0xc0086786c0 <nil>}': pq: referenced descriptor ID 109: looking up ID 109: descriptor not found
    --- FAIL: TestExtractIngestExternalCatalog/udt (0.33s)

Parameters:

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

Help

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

This test on roachdash | Improve this report!

[github-actions]

sql/catalog/externalcatalog.TestExtractIngestExternalCatalog failed on master @ a4fe3aab892743a0d1f4d6f11609c3c632f43e05:

=== RUN   TestExtractIngestExternalCatalog
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestExtractIngestExternalCatalog2813556124
    test_log_scope.go:76: use -show-logs to present logs inline
    external_catalog_test.go:174: -- test log scope end --
test logs left over in: outputs.zip/logTestExtractIngestExternalCatalog2813556124
--- FAIL: TestExtractIngestExternalCatalog (4.93s)
=== RUN   TestExtractIngestExternalCatalog/udt
    external_catalog_test.go:154: error scanning '&{0xc00263b440 <nil>}': pq: referenced descriptor ID 109: looking up ID 109: descriptor not found
    --- FAIL: TestExtractIngestExternalCatalog/udt (0.16s)

Parameters:

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

Help

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

This test on roachdash | Improve this report!

[fqazi]

@fqazi this looks like a strange flake. i think it suggests that certain descriptors may have actually gotten written in the WriteDescriptors call?

@msbutler The flake disappears if I skip the previous basic test, so its linked to the clean up in that test I think.