Refactor MethodTypeToParserNodePrism for cleaner code and better organization #6936
Triggered via pull request
December 15, 2025 19:17
allcre
Status
Failure
Total duration
24m 17s
Artifacts
–
ci.yml
on: pull_request
Prism Parser Regression Tests
24m 11s
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>0a2RAaQAAAADRe6y1cGEQT52h0H4jG1F6UEhMMzBFREdFMDQxOABFZGdl
|
|
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>0aWRAaQAAAADeS7mxBqVxR79x5vDdEJ24UEhMMzBFREdFMDQxOABFZGdl
|
|
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
|