-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Revert enabling parallelism by default #67379
Conversation
…, r=alexcrichton" This reverts commit 3ed3b8b, reversing changes made to 99b8953. We will reland a similar patch at a future date but for now we should get a nightly released in a few hours with the parallel patch, so this should be reverted to make sure that the next nightly is not parallel-enabled.
@bors r+ p=100 This is safe to approve now as we're less than 4 hours from the deadline (3.5ish) and we have another PR currently testing. I've also gone ahead and given this a pretty high priority, but it should be entirely safe to rollup (as it fully reverts a bors merge commit). |
📌 Commit 7f00a5f has been approved by |
🌲 The tree is currently closed for pull requests below priority 100, this pull request will be tested once the tree is reopened |
…t, r=Mark-Simulacrum Revert enabling parallelism by default We will re-land a similar patch at a future date but for now we should get a nightly released in a few hours with the parallel patch, so this should be reverted to make sure that the next nightly is not parallel-enabled. r? @ghost
⌛ Testing commit 7f00a5f with merge bf3790f9993a067ec56eee5234b9533bba06f720... |
…t, r=Mark-Simulacrum Revert enabling parallelism by default We will re-land a similar patch at a future date but for now we should get a nightly released in a few hours with the parallel patch, so this should be reverted to make sure that the next nightly is not parallel-enabled. r? @ghost
@bors retry yield to rollup including this |
⌛ Testing commit 7f00a5f with merge 16c58f8f6676336d9b98fdb25563c056fdc35947... |
…t, r=Mark-Simulacrum Revert enabling parallelism by default We will re-land a similar patch at a future date but for now we should get a nightly released in a few hours with the parallel patch, so this should be reverted to make sure that the next nightly is not parallel-enabled. r? @ghost
@bors retry yielding to new rollup (including this) |
…imulacrum Revert enabling parallelism by default We will re-land a similar patch at a future date but for now we should get a nightly released in a few hours with the parallel patch, so this should be reverted to make sure that the next nightly is not parallel-enabled. r? @ghost
Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-azure |
@bors retry |
…imulacrum Revert enabling parallelism by default We will re-land a similar patch at a future date but for now we should get a nightly released in a few hours with the parallel patch, so this should be reverted to make sure that the next nightly is not parallel-enabled. r? @ghost
☀️ Test successful - checks-azure |
We will re-land a similar patch at a future date but for now we should get a nightly
released in a few hours with the parallel patch, so this should be
reverted to make sure that the next nightly is not parallel-enabled.
r? @ghost