Skip to content

Improve unexpected error scanner for compile-fail tests (Closes #1476) #3460

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
wants to merge 1 commit into from

Conversation

0c0w3
Copy link
Contributor

@0c0w3 0c0w3 commented Sep 11, 2012

This is for issue #1476. It's the first Rust code I've ever written!

@brson
Copy link
Contributor

brson commented Sep 12, 2012

Merged. Thanks!

@brson brson closed this Sep 12, 2012
bors pushed a commit to rust-lang-ci/rust that referenced this pull request May 15, 2021
show the HEAD of the integration branch to faciliate reproducing an error with rustfmt
RalfJung pushed a commit to RalfJung/rust that referenced this pull request Jul 14, 2024
Currently cargo-miri uses the first target specified in the command
line. However, when multiple targets are specified in a `cargo build`
invocation, cargo will build for all of them.

Miri should match this behaviour to reduce surprises.

Fixes: rust-lang#3460
RalfJung pushed a commit to RalfJung/rust that referenced this pull request Jul 14, 2024
Run tests for all specified targets

Currently cargo-miri uses the first target specified in the command line. However, when multiple targets are specified in a `cargo build` invocation, cargo will build for all of them.

Miri should match this behaviour to reduce surprises.

Fixes: rust-lang#3460
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants