Skip to content

Fix certain symbols being incorrectly identified as incomplete boolea… #68

Fix certain symbols being incorrectly identified as incomplete boolea…

Fix certain symbols being incorrectly identified as incomplete boolea… #68

Triggered via push July 11, 2024 13:25
Status Failure
Total duration 1m 27s
Artifacts

miri.yml

on: push
Matrix: Test with Miri
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 14 warnings
Test with Miri (macos-latest, experimental)
Process completed with exit code 1.
Test with Miri (ubuntu-latest, experimental)
The job was canceled because "macos-latest_experimental" failed.
Test with Miri (ubuntu-latest, experimental)
The operation was canceled.
Test with Miri (windows-latest, experimental)
The job was canceled because "macos-latest_experimental" failed.
Test with Miri (windows-latest, experimental)
The operation was canceled.
`assert!(false, ..)` should probably be replaced: src/lazy/text/buffer.rs#L2331
error: `assert!(false, ..)` should probably be replaced --> src/lazy/text/buffer.rs:2331:21 | 2331 | / assert!( 2332 | | false, 2333 | | "Parser reported an unexpected error for input: {}, Result: {:?}", 2334 | | self.input, err 2335 | | ); | |_____________________^ | = help: use `panic!(..)` or `unreachable!(..)` = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#assertions_on_constants
`assert!(false, ..)` should probably be replaced: src/lazy/text/buffer.rs#L2303
error: `assert!(false, ..)` should probably be replaced --> src/lazy/text/buffer.rs:2303:21 | 2303 | / assert!( 2304 | | false, 2305 | | "parser reported an incomplete match rather than a mismatch: {}", 2306 | | self.input 2307 | | ) | |_____________________^ | = help: use `panic!(..)` or `unreachable!(..)` = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#assertions_on_constants = note: `-D clippy::assertions-on-constants` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::assertions_on_constants)]`
Test with Miri (macos-latest, experimental)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test with Miri (macos-latest, experimental)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test with Miri (macos-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (macos-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (macos-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (macos-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (ubuntu-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (ubuntu-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (ubuntu-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (ubuntu-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (windows-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (windows-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (windows-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test with Miri (windows-latest, experimental)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/