[no merge] crater pre-expansion gating #66063
Conversation
|
This reverts #66004 to get us to a point where we observed the regressions and applies #65974 to hopefully mitigate a known source of regressions. It also sets the release channel to beta. This first try build will be the 'end' commit in our crater run, i.e., with the pre-expansion gating applied. We'll also get the start commit momentarily by building off of master with the beta commit being the only commit applied... @bors try |
|
⌛ Trying commit c0a8ffe622f75d9e2e124bd47797553c410ccaad with merge 8810c24b0958114d8dbb32d878444e8956fce80f... |
Mark-Simulacrum
force-pushed
the
crater-pre-expansion-gate
branch
from
c0a8ffe to
61fec2f
Compare
|
@bors try And the start commit, hopefully... |
…try> [no merge] crater pre-expansion gating r? @ghost
|
☀️ Try build successful - checks-azure |
|
@craterbot run mode=check-only start=try#5e633973aa9255a88b65a39484627bb54e6044b3 end=try#8810c24b0958114d8dbb32d878444e8956fce80f cap-lints=allow |
|
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
craterbot
added
the
S-waiting-on-crater
|
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
|
🎉 Experiment
|
craterbot
added
S-waiting-on-review
|
Closing this PR as we've gathered what we wanted to here, I believe. Initial assessment looks quite good (surprisingly to me, to be honest - either this was not a successful test, or no one is using unstable syntax in the wild?). I suppose we don't have that many features that touch syntax. In any case, I'll try and followup on the original issue soon with these results. |
r? @ghost