-
Notifications
You must be signed in to change notification settings - Fork 13.3k
compile-fail tests ignore pattern after the first : #207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
oli-obk
pushed a commit
to oli-obk/rust
that referenced
this issue
Jul 19, 2017
update xargo usage example for new location of vecs.rs
keeperofdakeys
pushed a commit
to keeperofdakeys/rust
that referenced
this issue
Dec 12, 2017
Add select() to Android bindings
kazcw
pushed a commit
to kazcw/rust
that referenced
this issue
Oct 23, 2018
dlrobertson
pushed a commit
to dlrobertson/rust
that referenced
this issue
Nov 29, 2018
…patch-1 remove unwinding from UB
matthiaskrgr
pushed a commit
to matthiaskrgr/rust
that referenced
this issue
Mar 7, 2023
Regenerate intrinsics
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Dec 6, 2024
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am adding a test to compile-fail that has
// error-pattern: unresolved name: a
to test the test I changed the line to
// error-pattern: unresolved name: x
and to my surprise the test passed
changing it to something like
// error-pattern: unresolved namex: a
correctly causes it to fail
The text was updated successfully, but these errors were encountered: