-
Notifications
You must be signed in to change notification settings - Fork 61
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
Incorrect folder name is printed for each test #76
Comments
Ah, I think I found it -- in make_test_name. |
That does seem to be a bug... The assumption is that the |
Would it be |
@laumann Yes it is in |
Nice :-) Just submit a PR here as well, or ping me when it's in, then I'll replicate it here and release a new version |
Looking at miri, you might want to update to compiletest 0.3.0 - it might cause some breakage though as the update changed the type of some fields in |
Well I guess I'll see and fix that breakage as I update to the version that fixes this. ;) |
Yeah ok :-) I was just thinking that 0.3.0 is much closer to the current rustc/compiletest, the 0.2 series was getting behind a bit. |
…crum compiletest: print the correct basename of the src dir See <Manishearth/compiletest-rs#76>. Fixes rust-lang#40712
…crum compiletest: print the correct basename of the src dir See <Manishearth/compiletest-rs#76>. Fixes rust-lang#40712
…crum compiletest: print the correct basename of the src dir See <Manishearth/compiletest-rs#76>. Fixes rust-lang#40712
The upstream rustc PR has been merged. |
Nice! |
Any chance of a release with this fix? :D |
Yeah, sure thing :-) |
0.3.1 is out |
Thanks, that was fast. :-) |
In miri, we have a folder
compile-fail-fullmir
for compile-fail tests that need a different setup than those in compile-fail. This reveals that compiletest prints the wrong path to the file that it is testing:This says the file name is
compile-fail/undefined_byte_read.rs
while it really iscompile-fail-fullmir/undefined_byte_read.rs
. compiletest seems to use the suite name when printing the folder name, which is not in general correct.I tried to fix this myself, but unfortunately I could not even find the place in the code that does this printing...
The text was updated successfully, but these errors were encountered: