Skip to content

[TST] Commit the manually reconstructed test flake. (#3124) #630

[TST] Commit the manually reconstructed test flake. (#3124)

[TST] Commit the manually reconstructed test flake. (#3124) #630

Triggered via push November 21, 2024 18:59
Status Failure
Total duration 51m 14s
Billable time 1h 34m
Artifacts 62
check-tag
0s
check-tag
Matrix: Go tests / test
Matrix: python-tests / test-single-node-integration-stress
Matrix: python-tests / test-single-node-integration
Matrix: python-tests / test-stress
Matrix: python-tests / test-thin-client
Matrix: python-tests / test
Matrix: Rust tests / test-benches
Matrix: Rust tests / test-integration
Matrix: Rust tests / test
get-version
46s
get-version
JavaScript client tests  /  test
2m 25s
JavaScript client tests / test
Go tests  /  cluster-test
4m 53s
Go tests / cluster-test
Matrix: python-tests / test-cluster-integration
Deploy docs to Vercel
2m 2s
Deploy docs to Vercel
python-tests  /  merge-cluster-logs
5s
python-tests / merge-cluster-logs
Publish to DockerHub and GHCR
6m 9s
Publish to DockerHub and GHCR
Publish to PyPI
1m 10s
Publish to PyPI
Publish thin client to PyPI
1m 18s
Publish thin client to PyPI
Make GitHub release
0s
Make GitHub release
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
Deploy docs to Vercel
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Publish to DockerHub and GHCR
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/login-action@v2.1.0, docker/build-push-action@v3.2.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
built-chromadb-package
32.1 MB
cluster_logs_test_add_3.10
824 KB
cluster_logs_test_add_3.11
852 KB
cluster_logs_test_add_3.12
741 KB
cluster_logs_test_add_3.8
655 KB
cluster_logs_test_add_3.9
929 KB
cluster_logs_test_collection_3.10
38.1 KB
cluster_logs_test_collection_3.11
38.1 KB
cluster_logs_test_collection_3.12
37.8 KB
cluster_logs_test_collection_3.8
37.8 KB
cluster_logs_test_collection_3.9
37.8 KB
cluster_logs_test_collections_3.10
66.1 KB
cluster_logs_test_collections_3.11
201 KB
cluster_logs_test_collections_3.12
197 KB
cluster_logs_test_collections_3.8
188 KB
cluster_logs_test_collections_3.9
298 KB
cluster_logs_test_collections_with_database_tenant_3.10
585 KB
cluster_logs_test_collections_with_database_tenant_3.11
88.2 KB
cluster_logs_test_collections_with_database_tenant_3.12
597 KB
cluster_logs_test_collections_with_database_tenant_3.8
79.3 KB
cluster_logs_test_collections_with_database_tenant_3.9
541 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.10
36.1 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.11
35.3 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.12
36.1 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.8
36 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.9
35.9 KB
cluster_logs_test_embeddings_3.10
579 KB
cluster_logs_test_embeddings_3.11
782 KB
cluster_logs_test_embeddings_3.12
1010 KB
cluster_logs_test_embeddings_3.8
487 KB
cluster_logs_test_embeddings_3.9
604 KB
cluster_logs_test_filtering_3.10
457 KB
cluster_logs_test_filtering_3.11
562 KB
cluster_logs_test_filtering_3.12
508 KB
cluster_logs_test_filtering_3.8
393 KB
cluster_logs_test_filtering_3.9
576 KB
cluster_logs_test_logservice_3.10
42.4 KB
cluster_logs_test_logservice_3.11
42.6 KB
cluster_logs_test_logservice_3.12
42.7 KB
cluster_logs_test_logservice_3.8
42.7 KB
cluster_logs_test_logservice_3.9
42 KB
cluster_logs_test_memberlist_provider_3.10
36.4 KB
cluster_logs_test_memberlist_provider_3.11
36.5 KB
cluster_logs_test_memberlist_provider_3.12
37 KB
cluster_logs_test_memberlist_provider_3.8
36.4 KB
cluster_logs_test_memberlist_provider_3.9
36.4 KB
cluster_logs_test_producer_consumer_3.10
35 KB
cluster_logs_test_producer_consumer_3.11
34.8 KB
cluster_logs_test_producer_consumer_3.12
34.9 KB
cluster_logs_test_producer_consumer_3.8
35.2 KB
cluster_logs_test_producer_consumer_3.9
35.2 KB
cluster_logs_test_sanity_3.10
73.9 KB
cluster_logs_test_sanity_3.11
79.5 KB
cluster_logs_test_sanity_3.12
73.3 KB
cluster_logs_test_sanity_3.8
73.3 KB
cluster_logs_test_sanity_3.9
77.2 KB
cluster_logs_test_system_3.10
49.4 KB
cluster_logs_test_system_3.11
49.6 KB
cluster_logs_test_system_3.12
50.2 KB
cluster_logs_test_system_3.8
49.9 KB
cluster_logs_test_system_3.9
50 KB
cluster_test_logs
14 MB