Repository navigation
./x.py check library panics #89490
Description
Activity
@lopopolo you want
x.py check library/std. It wouldn't hurt to makelibraryan alias for that I suppose.- addedT-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.and removedC-bugCategory: This is a bug.Category: This is a bug.
on Oct 3, 2021 I would prefer to avoid those aliases, but we should have the full list of paths on hand so we could do something like "did you mean" and print out paths that could start with library/
Reacted by jyn, Ryan Lopopolo and Hans KratzI think
libraryan alias doesn't have a clear default: would it be justlibrary/std, or bothlibrary/std,library/allocandlibrary/core, or all thelibrary/*? I feel like a shortcut forlibrary/std,library/allocandlibrary/coremight be useful though, since often a change incoremight have an impact in a test of the other two crates, so you might want to test all of them just to be sure.Going back to this issue, I think a panic gives a bad UX here, it's not an unexpected error that should never happen!
@SkiFire13 right now x.py treats all four of those paths you mention as the same, it doesn't know how to build individual crates.
@jyn514 that doesn't seem to include tests though. If I make a test fail in
library/coreand then runx.py test library/stdI don't see any failure pop up, but I do when I runx.py test library/core.Reacted by jynImplemented in #95504.
I ran
./x.py check library.I expected this command to check all crates defined in the
librarydirectory or at least print a useful error.Instead, I got a panic.
Meta
rust HEAD: