-
Notifications
You must be signed in to change notification settings - Fork 13.3k
removes syntax diagnostic err code uniqueness check #25603
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
removes syntax diagnostic err code uniqueness check #25603
Conversation
r? @sfackler (rust_highfive has picked a reviewer for you, use r? to override) |
Looks good 👍 |
@bors r+ |
📌 Commit 760daf1 has been approved by |
@bors p=1 unblock those bots |
Sorry for breaking the build 😬 |
@bors: p=100 No worries @michaelsproul! |
⌛ Testing commit 760daf1 with merge a32db93... |
💔 Test failed - auto-mac-32-opt |
@bors: retry |
⌛ Testing commit 760daf1 with merge 35b01e2... |
💔 Test failed - auto-linux-64-x-android-t |
Note that the failure there is because there was an error outputting the metadata. I think for now it may just be best to remove it and then re-add it at a later date. |
Damn... yeah, disabling it seems like our only option. We'll also have to prevent the error index from trying to build, just in case it fails in the absence of data. |
Sorry I can't put a PR together myself, I'm travelling interstate at the moment. |
(Commenting out/removing the dependency that the |
…guing the bots for two separate reasons and needs a quick fix for now: 1. It's possible to read the stale metadata of previous builds, causing spurious failures that can only be solved by blowing away `tmp`. 2. The code does not currently handle concurrent compilations where JSON files in the metadata directory may be half-written and hence contain invalid JSON when read. This validation should come back, but it should likely be part of a lint pass run at the very end of the build that doesn't run into consistency or concurrency problems. ---- This commit is a revised version of PR rust-lang#25592; this approach differs in that it continues to output the JSON metadata, so that the error index page continues to work (assuming that people do not accidentally put in duplicate entries in the meantime).
(I'm currently revising this PR to provide better feedback about the particular error that was encountered during the metadata-output step. Admittedly such feedback won't actually fix the problem immediately, so if someone would prefer to take the more severe step of removing the error index generation and all of the other code, that's fine; I just figured i would try to acquire more knowledge from the build bots in the meantime...) |
Yeah, it would also be nice to know why the output is failing... we should probably pass the |
760daf1
to
723d1df
Compare
(I'm hoping that this will either (1.) fail in the same way, but provide much better error feedback, or (2.) magically succeed this time, unwedging various builds, and then future failures will likewise provide much better error feedback...) |
⌛ Testing commit 723d1df with merge 7e1e838... |
💔 Test failed - auto-linux-64-opt |
Well, apparently we get the unpredicted variant (3.):
At this point I'm going to go with @alexcrichton 's original plan (augmented with @michaelsproul 's note) to entirely remove the error code checking and error index page generation. |
closing in favor of PR #25706 |
This commit removes the syntax diagnostic validation as it's been plaguing the bots for two separate reasons and needs a quick fix for now:
tmp
.This validation should come back, but it should likely be part of a lint pass run at the very end of the build that doesn't run into consistency or concurrency problems.
This commit is a revised version of PR #25592; this approach differs in that it continues to output the JSON metadata, so that the error index page continues to work (assuming that people do not accidentally put in duplicate entries in the meantime).