Skip to content

Two concurrent create_namespace requests should raise a NamespaceAlreadyExistsError #6764

Two concurrent create_namespace requests should raise a NamespaceAlreadyExistsError

Two concurrent create_namespace requests should raise a NamespaceAlreadyExistsError #6764

Triggered via pull request November 18, 2026 19:19
Status Success
Total duration 22m 21s
Artifacts 4

python-integration.yml

on: pull_request
integration-test
12m 1s
integration-test
integration-test-s3
1m 42s
integration-test-s3
integration-test-adls
1m 37s
integration-test-adls
integration-test-gcs
1m 39s
integration-test-gcs
integration-coverage-report
2m 51s
integration-coverage-report
python-integration-required
4s
python-integration-required
Fit to window
Zoom out
Zoom in

Annotations

1 warning
integration-test
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.16-044aabaf2eb35a1986a786e3091ed8dab2fc1124d4ecd77e1fe245e3b588e401, another job may be creating this cache.

Artifacts

Produced during runtime
Name Size Digest
coverage-adls
9.17 KB
sha256:c814e96caea8e1293654f2d7a348e160fa674b704af13f1ab481513822c6572c
coverage-gcs
9.16 KB
sha256:f94e725372b951b88cfa7a22abb0ac35c683e31c2c4796c8fa745d3db2fd7c83
coverage-integration
10.2 KB
sha256:9c9097b622d94d2061062cf0cc6a618ff9ec80ea1ed82dfd924c40db5c2f892d
coverage-s3
9.17 KB
sha256:48b79c0f3acfbb9433baa9f054a2044d7f8a61fe813d76e4177c9b7161d049a5