-
Notifications
You must be signed in to change notification settings - Fork 13k
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 "Promote missing_fragment_specifier to hard error" #75516 #80210
Conversation
|
@bors r+ rollup=never p=1 |
📌 Commit f2c8a38 has been approved by |
The job Click to see the possible cause of the failure (guessed by this bot)
|
⌛ Testing commit f2c8a38 with merge 71f9e69c89b63435b3d9ebf6706684140a23e257... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors r+ |
📌 Commit 773af1b6ec36ea47cc5327c29ca23ef306c08477 has been approved by |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors r- (But please reapprove once things are working, or ping me on Zulip and I can drive this to conclusion). |
I'm having issue running this locally so we should wait until CI is green before r+'ing again. |
773af1b
to
483668b
Compare
Seems that did it! @bors r=Mark-Simulacrum |
📌 Commit 483668b has been approved by |
⌛ Testing commit 483668b with merge 0d24b4260d227ccef37e1be8e776320ef0e287b0... |
💔 Test failed - checks-actions |
@Mark-Simulacrum any idea why this failed? I can't seem to access the log for the failed builder. |
@bors retry I think the self hosted runners sometimes just die midbuild. |
☀️ Test successful - checks-actions |
This was attempted in [1] then reverted in [2] because of fallout. Recently, this was made an edition-dependent error in [3]. Make missing fragment specifiers an unconditional error again. [1]: rust-lang#75516 [2]: rust-lang#80210 [3]: rust-lang#128006
…unconditional, r=<try> [crater] Make `missing_fragment_specifier` an unconditional error This was attempted in [1] then reverted in [2] because of fallout. Recently, this was made an edition-dependent error in [3]. Experiment with turning missing fragment specifiers an unconditional error again. More context: rust-lang#128006 [1]: rust-lang#75516 [2]: rust-lang#80210 [3]: rust-lang#128006
Revert of #75516 per #76605.
r? @Mark-Simulacrum
Note: I only reverted the two commits in #75516 which made the lint a hard error. I did not revert the other two commits in the PR as they seemed fine to leave IMO (commits 84fcd0d and eb4d6b5).