-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Add a CI job for parallel rustc using x.py check #49120
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
9ca0210
to
4bfb537
Compare
It seems to take 3 minutes to check things. Maybe we could add it to PR builds too then? |
76ce6e1 is probably not supposed to be in this PR. I'm not entirely certain that I like this approach since it adds an extremely short CI builder.. I'm wondering if we can put this on top of some other builder instead, maybe via re-configuring mid run? I'm not sure how it would work, though. |
5582a51
to
906f51e
Compare
I moved it to the start of |
@bors: r+ |
📌 Commit 906f51e has been approved by |
@bors r- This needs the fixes for |
It's probably a good idea to nuke the build directory after the first build too. |
Hm, okay. I'd somewhat prefer to land those in a separate PR, but it does seem fine to include them here. Yes, we should probably go ahead and delete the build directory... |
Ping from triage, @alexcrichton ! Looks like there have been some new commits pushed. |
This is just waiting on #49030 to land. |
@bors r=alexcrichton |
📌 Commit efa9016 has been approved by |
⌛ Testing commit efa9016 with merge 424d67bf95e422c922865ef623f017f043305f51... |
@bors retry rollup |
Add a CI job for parallel rustc using x.py check r? @alexcrichton
Add a CI job for parallel rustc using x.py check r? @alexcrichton
r? @alexcrichton