-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Fix x.py test for librustc crates. #74153
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
Looks like as a result some tests are failing :/ r=me on the patch though. |
@bors r=Mark-Simulacrum |
📌 Commit 7238726 has been approved by |
@bors p=20 we should get tests running as quickly as possible to prevent further regressions |
…r=Mark-Simulacrum Fix x.py test for librustc crates. rust-lang#73352 introduced a bug where `x.py test src/librustc_ast` would fail to actually run the tests. The issue is that `krate` and `all_krates` were changed to return relative paths. This caused the code to do a test of "relative_path ends with absolute path" which is always false. The solution is to swap that around. The change to `Crate` isn't necessary, it just simplifies the code and makes it uniform with `CrateLibrustc`.
☀️ Test successful - checks-actions, checks-azure |
#73352 introduced a bug where
x.py test src/librustc_ast
would fail to actually run the tests. The issue is thatkrate
andall_krates
were changed to return relative paths. This caused the code to do a test of "relative_path ends with absolute path" which is always false. The solution is to swap that around.The change to
Crate
isn't necessary, it just simplifies the code and makes it uniform withCrateLibrustc
.