Allow ui tests to have dependencies in a reliable way#2373
Conversation
|
Could you describe the design at a high level? That would help with reviewing. :) |
coincidentally this removes the implicit trick of using |
I never heard of this, no idea what you are talking about here. |
we have lots of tests that use |
|
Oh lol, I had no idea. Like, taking the sysroot libc seems fine, but I didn't know the other thing would have worked. Good thing I didn't.^^ |
|
☔ The latest upstream changes (presumably #2380) made this pull request unmergeable. Please resolve the merge conflicts. |
5c97ff3 to
cf74b1f
Compare
cf74b1f to
e5736f9
Compare
|
Do you want to review this? Or can I merge myself? |
|
It's in my queue :) |
RalfJung
left a comment
There was a problem hiding this comment.
Wow this is clever, I like it a lot. :)
|
We will probably want to move some tests from test-cargo-miri to here, in particular the getrandom tests. Those use the renaming feature of cargo: Will that work? |
|
Oh also please check that this works in the rustc workspace via |
I was afraid of this ^^ it doesn't work with my current scheme. The fix is obvious and I knew I should've done it this way, but 🤷 Basically what I need to do is to also run EDIT: works now correctly |
even the latest version doesn't work from rustc yet, so this PR is not ready yet |
@rustbot author |
0c41b5a to
b0353b5
Compare
|
status update I can reproduce the failure with x.py now: running via the bootstrap machinery will suceed to build edit: manually adding |
|
@rustbot ready |
|
@rustbot author |
|
@rustbot ready |
|
r=me with run-test.py fixed and commits squashed |
5474f13 to
ab6fb9d
Compare
|
@bors r=RalfJung |
|
☀️ Test successful - checks-actions |
| //@only-target-linux: the errors differ too much between platforms | ||
|
|
||
| #[tokio::main] | ||
| async fn main() {} |
There was a problem hiding this comment.
Btw would be nice to also have a 'pass' test for #602 (comment).
Should we have these tests of non-stdlib crates in a subdir in our test folders? The root dirs are already quite messy, so something like {pass,fail}/crates or so might make sense?
There was a problem hiding this comment.
yea grouping them into a custom folder makes sense.
avoid duplicating commands
This completely sidesteps the issue that compiletest-rs has where old artifacts of a dependency cause
multiple available crates of name XXXerrors. At this point I think we've reached feature parity for clippy, too, so I'm going to try publishing a version once this is merged.