-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Update E0206 message to new format #35402
Conversation
91726cf
to
5bab0e6
Compare
Great work, thanks! @bors: r+ rollup |
📌 Commit 5bab0e6 has been approved by |
…Gomez Update E0206 message to new format Part of rust-lang#35233. Fixes rust-lang#35301. r? @GuillaumeGomez
…Gomez Update E0206 message to new format Part of rust-lang#35233. Fixes rust-lang#35301. r? @GuillaumeGomez
…Gomez Update E0206 message to new format Part of rust-lang#35233. Fixes rust-lang#35301. r? @GuillaumeGomez
From a local build of the rollup #35462 which included this PR, I believe that this PR causes the |
@TimNN - it may be the combination of PRs that are causing the failures, since TravisCI passed this one by itself. Looking into it... |
|
@bors r- Ah, I missed that. |
@KiChjang - can you make sure your PR is rebased against the latest master? This failure may be coming from something that was added after you first submitted your PR. |
I've rebased, but I didn't run into any merge conflicts. |
Let's give it a retry then (didn't see the problem the first time but whatever). @bors: r+ rollup |
📌 Commit 413c321 has been approved by |
Wait, I see the problem. #35454 didn't update |
…Gomez Update E0206 message to new format Part of rust-lang#35233. Fixes rust-lang#35301. r? @GuillaumeGomez
@bors: r- |
@bors: r+ rollup |
📌 Commit 53baa09 has been approved by |
Update E0206 message to new format Part of #35233. Fixes #35301. r? @GuillaumeGomez
Part of #35233.
Fixes #35301.
r? @GuillaumeGomez