Skip to content

Implement TypeToParserNodePrism.cc #7157

Implement TypeToParserNodePrism.cc

Implement TypeToParserNodePrism.cc #7157

Triggered via push January 5, 2026 21:33
Status Failure
Total duration 23m 14s
Artifacts

ci.yml

on: push
Prism Parser Regression Tests
23m 11s
Prism Parser Regression Tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
Prism Parser Regression Tests
Process completed with exit code 1.
Prism Parser Regression Tests
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0oTNcaQAAAACURihtO7CpQ77ZuMTKM6kdUEhMMzBFREdFMDQyMQBFZGdl
Prism Parser Regression Tests
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0nzNcaQAAAAA2Ged86QDESaJNXxdiNeC5UEhMMzBFREdFMDQyMQBFZGdl
Prism Parser Regression Tests
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. at Object.<anonymous> (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.9.0/dist/node_modules/@actions/cache/lib/cache.js:175:1) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.9.0/dist/node_modules/@actions/cache/lib/cache.js:28:1)
Prism Parser Regression Tests
Failed to restore: Cache service responded with 400
Prism Parser Regression Tests
Failed to restore: Cache service responded with 400
Prism Parser Regression Tests
Failed to restore: Cache service responded with 400