Skip to content
Back to pull request #11845

Implement re-lexing logic for better error recovery #29510

Sign in to view logs

Implement re-lexing logic for better error recovery

Implement re-lexing logic for better error recovery #29510

Triggered via pull request June 17, 2024 06:43
@dhruvmaniladhruvmanila
synchronize #11845
dhruv/re-lexing
Status Failure
Total duration 19m 12s
Artifacts 3

ci.yaml

on: pull_request
Determine changes
7s
Determine changes
cargo fmt
14s
cargo fmt
python package
1m 17s
python package
pre-commit
39s
pre-commit
mkdocs
2m 18s
mkdocs
cargo test (linux)
3m 14s
cargo test (linux)
cargo clippy
1m 41s
cargo clippy
cargo test (windows)
6m 53s
cargo test (windows)
cargo test (wasm)
1m 12s
cargo test (wasm)
cargo build (release)
4m 15s
cargo build (release)
cargo build (msrv)
2m 43s
cargo build (msrv)
cargo fuzz
17s
cargo fuzz
test scripts
54s
test scripts
cargo shear
22s
cargo shear
formatter instabilities and black similarity
4m 10s
formatter instabilities and black similarity
benchmarks
5m 50s
benchmarks
Fuzz the parser
5m 22s
Fuzz the parser
ecosystem
15m 22s
ecosystem
test ruff-lsp
19s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
cargo fuzz
Process completed with exit code 1.
cargo test (wasm)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: jetli/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
mkdocs
The `python-version` input is not set. The version of Python currently in `PATH` will be used.

Artifacts

Produced during runtime
Name Size
ecosystem-result Expired
245 Bytes
pr-number Expired
140 Bytes
ruff Expired
75.4 MB