Skip to content

chore(deps): update dependency jsonpath-plus to v10 #11805

chore(deps): update dependency jsonpath-plus to v10

chore(deps): update dependency jsonpath-plus to v10 #11805

Triggered via pull request November 10, 2024 00:50
Status Failure
Total duration 24m 2s
Artifacts

ci.yaml

on: pull_request
matrix-prep
2s
matrix-prep
Matrix: test
conclusion
8s
conclusion
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 9 warnings
test (6, 6.5.0, 1, windows, e2e/bzlmod, local)
Process completed with exit code 1.
test (7, 7.4.0, 1, windows, e2e/bzlmod, local)
Process completed with exit code 1.
test (7, 7.4.0, 0, ubuntu, .)
Process completed with exit code 1.
test (6, 6.5.0, 1, ubuntu, .)
Process completed with exit code 1.
test (7, 7.4.0, 1, ubuntu, .)
Process completed with exit code 1.
conclusion
Process completed with exit code 1.
test (7, 7.4.0, 1, ubuntu, e2e/vendored_node)
Failed to save: Cache service responded with 429 during upload chunk.
test (7, 7.4.0, 1, ubuntu, e2e/verify_patches)
Failed to save: Cache service responded with 429 during upload chunk.
test (7, 7.4.0, 0, ubuntu, e2e/js_image_oci)
Failed to save: Cache service responded with 429 during upload chunk.
test (7, 7.4.0, 0, ubuntu, e2e/webpack_devserver_esm)
Failed to save: Cache service responded with 429 during upload chunk.
test (7, 7.4.0, 0, ubuntu, e2e/webpack_devserver)
Failed to save: Cache service responded with 429 during upload chunk.
test (7, 7.4.0, 1, ubuntu, e2e/webpack_devserver)
Failed to save: Cache service responded with 429 during upload chunk.
test (7, 7.4.0, 1, ubuntu, e2e/js_image_oci)
Failed to save: Cache service responded with 429 during upload chunk.
test (6, 6.5.0, 1, ubuntu, e2e/js_image_oci)
Failed to save: Cache service responded with 429 during upload chunk.
conclusion
The following actions use a deprecated Node.js version and will be forced to run on node20: technote-space/workflow-conclusion-action@45ce8e0eb155657ab8ccf346ade734257fd196a5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/