Skip to content

Cross-Version Tests and Upload #3442

Cross-Version Tests and Upload

Cross-Version Tests and Upload #3442

Triggered via schedule June 10, 2026 01:12
Status Success
Total duration 37m 41s
Artifacts 15

cross_version_test.yml

on: schedule
precommit  /  Setup Build Metadata
8s
precommit / Setup Build Metadata
Matrix: precommit / image_build
Matrix: test / allinone_image_test
Matrix: test / bf_image_test
test  /  get_bf_versions
14s
test / get_bf_versions
test  /  get_pybf_versions
9s
test / get_pybf_versions
Matrix: test / bf_cross_version_tests
Matrix: test / pybf_cross_version_tests
upload_dev  /  prod_image_upload
upload_dev / prod_image_upload
upload_dev  /  prod_whl_upload
upload_dev / prod_whl_upload
upload_dev  /  check_repos
upload_dev / check_repos
upload_dev  /  dev_image_upload
17m 36s
upload_dev / dev_image_upload
upload_dev  /  dev_whl_upload
40s
upload_dev / dev_whl_upload
lab_validation  /  discover-labs
8s
lab_validation / discover-labs
lab_validation  /  build-batfish
0s
lab_validation / build-batfish
Matrix: lab_validation / lab-integration-test
lab_validation  /  all-labs-passed
2s
lab_validation / all-labs-passed
upload_prod  /  prod_image_upload
upload_prod / prod_image_upload
upload_prod  /  prod_whl_upload
upload_prod / prod_whl_upload
upload_prod  /  check_repos
upload_prod / check_repos
upload_prod  /  dev_image_upload
upload_prod / dev_image_upload
upload_prod  /  dev_whl_upload
upload_prod / dev_whl_upload
notify_slack_on_failure
0s
notify_slack_on_failure
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
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.
upload_dev / dev_image_upload
Failed to save: Unable to reserve cache with key docker.io--tonistiigi--binfmt-latest-linux-x64, another job may be creating this cache.

Artifacts

Produced during runtime
Name Size Digest
allinone_image
569 MB
sha256:db9c5742e2257f9edba2a8e6a6657a116b3c07a81274cb428b191b0d9a161d23
allinone_image_arm64
560 MB
sha256:24066ff256b23b622f51e497ecdf6291a5ad3c15f18d3f110bee17e505d60755
batfish~docker~08XW30.dockerbuild
83.8 KB
sha256:fdfebf819c9046a4783c9423e425f718aa0b621bf2267914404bc43ebc2d139a
batfish~docker~9NPSVQ.dockerbuild
65.7 KB
sha256:ddf6ab74cad8bcf3c09c3b50d93c3901e2de209aa91225b9bc758b030ff73bf7
batfish~docker~CHEY49.dockerbuild
38.1 KB
sha256:4f0518849ff00aa810c05e58f0fabeba29882fbaff9673e1397d2426aec9e6c6
batfish~docker~JMVVDO.dockerbuild
38.6 KB
sha256:5d9a5562ab58c712e10daf5c3cf34e548b1aabdb529602fa83171b66e75b88c9
batfish~docker~MEJAC7.dockerbuild
143 KB
sha256:77456707aa5a7b14b02b44ffd92ca8123aa034cf6997f979f670b2673e8cadcc
batfish~docker~VWH0DC.dockerbuild
66.2 KB
sha256:721d52ff2c8b0c33cdc1f07bb20bffbb0b36df1e1680c44b0aec4da35e81f390
bf_image
185 MB
sha256:bd383118ffa8b19a21a090c269e5560c31279afb7aa076b59fc22b064db2f036
bf_image_arm64
184 MB
sha256:848eb10d34f582b468c2898dffa3bc59f692299a8eda3972d57bd454c89f1493
bf_jar
61.4 MB
sha256:bad67ba0fa976b21af6bd80cbb6ac2d577bbe132dae6df7d7af19632242d524a
bf_questions
18.5 KB
sha256:f1f4b6e552c1c35d4e2203f13fbdced2c29b339fdb48cfb53be3139603e23468
pybf_notebooks
883 KB
sha256:60c1c844265d8919e0c7093206de80d12be6286b36b239ba3f0525f22ccf2fcb
pybf_tests
52.9 KB
sha256:39cb87c4178bb2f909dcf06d9d772a0d727922a95dbd24e2ecb27c5176a4beb3
pybf_whl
324 KB
sha256:5f36b0e3f9fd6c7a0ac1cf266439e6c14867e0974d4a78361d4f6e2eece0efb2