Skip to content

fix: build failure with bazel 8 #258

fix: build failure with bazel 8

fix: build failure with bazel 8 #258

Triggered via pull request October 16, 2025 15:56
Status Failure
Total duration 4m 40s
Artifacts

ci.yml

on: pull_request
Matrix: bazel-integration-tests
Matrix: cmake-integration-tests
Matrix: windows-bazel-build
Matrix: windows-cmake-build
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 8 warnings
bazel-integration-tests (instrumentation, ubuntu-latest)
Process completed with exit code 2.
bazel-integration-tests (walltime, codspeed-macro)
The strategy configuration was canceled because "bazel-integration-tests.instrumentation_ubuntu-la" failed
bazel-integration-tests (walltime, codspeed-macro)
The operation was canceled.
bazel-integration-tests (off, ubuntu-latest)
The strategy configuration was canceled because "bazel-integration-tests.instrumentation_ubuntu-la" failed
bazel-integration-tests (off, ubuntu-latest)
The operation was canceled.
windows-bazel-build (walltime, 9.0.0-pre.20250921.2)
Process completed with exit code 1.
windows-bazel-build (walltime, 7.6.2)
Process completed with exit code 1.
windows-bazel-build (off, 9.0.0-pre.20250921.2)
Process completed with exit code 1.
windows-bazel-build (walltime, 8.4.2)
Process completed with exit code 1.
windows-bazel-build (off, 8.4.2)
Process completed with exit code 1.
windows-bazel-build (off, 7.6.2)
Process completed with exit code 1.
bazel-integration-tests (walltime, codspeed-macro)
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. at /actions-runner/_work/_actions/bazel-contrib/setup-bazel/0.14.0/dist/node_modules/@actions/cache/lib/cache.js:384:1 at Generator.next (<anonymous>) at fulfilled (/actions-runner/_work/_actions/bazel-contrib/setup-bazel/0.14.0/dist/node_modules/@actions/cache/lib/cache.js:28:1)
bazel-integration-tests (walltime, codspeed-macro)
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. at /actions-runner/_work/_actions/bazel-contrib/setup-bazel/0.14.0/dist/node_modules/@actions/cache/lib/cache.js:384:1 at Generator.next (<anonymous>) at fulfilled (/actions-runner/_work/_actions/bazel-contrib/setup-bazel/0.14.0/dist/node_modules/@actions/cache/lib/cache.js:28:1)
bazel-integration-tests (off, ubuntu-latest)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-bazel-build (walltime, 7.6.2)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-bazel-build (off, 9.0.0-pre.20250921.2)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-bazel-build (walltime, 8.4.2)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-bazel-build (off, 8.4.2)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-bazel-build (off, 7.6.2)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists