Skip to content
Cross-Version Tests and Upload

Cross-Version Tests and Upload #2327

Sign in to view logs

Cross-Version Tests and Upload

Cross-Version Tests and Upload #2327

Triggered via schedule June 5, 2025 15:06
@progwriterprogwriter
⁠ 6b84283
master
Status Failure
Total duration 30d 0h 11m 56s
Artifacts 7

cross_version_test.yml

on: schedule
precommit  /  Setup Build Metadata
7s
precommit / Setup Build Metadata
precommit  /  bf_build
2m 20s
precommit / bf_build
precommit  /  pybf_build
18s
precommit / pybf_build
precommit  /  image_build
2m 24s
precommit / image_build
test  /  bf_image_test
6m 22s
test / bf_image_test
test  /  allinone_image_test
6m 48s
test / allinone_image_test
test  /  get_bf_versions
9s
test / get_bf_versions
test  /  get_pybf_versions
7s
test / get_pybf_versions
Matrix: test / bf_cross_version_tests
Matrix: test / pybf_cross_version_tests
upload  /  prod_image_upload
30d 0h
upload / prod_image_upload
Release Containers review time expired
upload  /  prod_whl_upload
30d 0h
upload / prod_whl_upload
Release Pybatfish review time expired
upload  /  check_repos
0s
upload / check_repos
upload  /  dev_image_upload
1m 23s
upload / dev_image_upload
upload  /  dev_whl_upload
4m 39s
upload / dev_whl_upload
notify_slack_on_failure
0s
notify_slack_on_failure
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
upload / prod_whl_upload
The deployment was rejected or didn't satisfy other protection rules.
upload / prod_image_upload
The deployment was rejected or didn't satisfy other protection rules.
Cross-Version Tests and Upload
The job was rejected because the gates for the environment Release Containers are not open
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):
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
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.

Artifacts

Produced during runtime
Name Size Digest
allinone_image Expired
553 MB
sha256:fecb435522b0f39f59863d57dc170670075d13618ec878413c822852fca29f0c
bf_image Expired
181 MB
sha256:8de80d5b7ecd8a19e4963230bdb07a870d3d906b7eaeea7993ec02af52873cca
bf_jar Expired
61.7 MB
sha256:2e73478ad2412f9b2b709f75ab2770a551f24afddb622291d907cbf0c7f25579
bf_questions Expired
17.7 KB
sha256:6fe8bf3b8fa25d4d514875ee0f216b2339c2a56d36a570f68727983d31085443
pybf_notebooks Expired
885 KB
sha256:d80db33bd01c950894a7af9399e5dbdb988b876884816a19ae8479f2790b2dfd
pybf_tests Expired
45.2 KB
sha256:e37799fad64a3f8ee84a742d9ec7f8020bd10afa0354cd651cdb7d9dd113be9b
pybf_whl Expired
295 KB
sha256:10b4a3416a234cc9b2bf8fae4f083f2876f3c567c1489d9f3d6032536bac3211