-
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
Add check to ensure error code explanations are not removed anymore even if not emitted #86623
Add check to ensure error code explanations are not removed anymore even if not emitted #86623
Conversation
This comment has been minimized.
This comment has been minimized.
57833d6
to
820dd02
Compare
f83a7f3
to
bc0aa3f
Compare
bc0aa3f
to
685915c
Compare
Moved the check into |
This is unrelated to validating toolstate, so it should go in a separate file. |
685915c
to
5a6d8f1
Compare
This comment has been minimized.
This comment has been minimized.
5a6d8f1
to
6efe8c6
Compare
Created a new bash script I'm now calling in the |
This comment has been minimized.
This comment has been minimized.
Please push a temp commit to make sure this works (mingw-check should fail on the PR) and also we may need to somehow skip this script in local docker invocations (where FETCH_HEAD is meaningless). I'm not sure what the best way of doing that would be, but it may also be OK to not worry too much about it -- if you could check that src/ci/docker/run.sh mingw-check works locally that would be sufficient for me (it may not actually detect deleted error codes but that's OK, just shouldn't fail). |
6efe8c6
to
dd5995d
Compare
So this part is working fine apparently. Even with:
|
It looks like CI here is passing, but the E0001 code is deleted so presumably CI should fail. My guess is that the BASE_COMMIT variable is not set in the script -- you'll need to find a way to pipe it through. I'm not sure where it gets set, though, so there's likely some investigation that needs to be done. |
c069f7e
to
8819021
Compare
This comment has been minimized.
This comment has been minimized.
IT WORKS! 🎉 Removing unwanted commit and it's good to go. :) |
…ven if not emitted
95be4f9
to
13bdc5c
Compare
@Mark-Simulacrum This is now ready. |
Updated! Only setting |
This comment has been minimized.
This comment has been minimized.
24ce2b5
to
d6962ff
Compare
@Mark-Simulacrum Should be ready now. |
@bors r+ rollup |
📌 Commit d6962ff has been approved by |
Rollup of 8 pull requests Successful merges: - rust-lang#86477 (E0716: clarify that equivalent code example is erroneous) - rust-lang#86623 (Add check to ensure error code explanations are not removed anymore even if not emitted) - rust-lang#86856 (Make x.py less verbose on failures) - rust-lang#86858 (Stabilize `string_drain_as_str`) - rust-lang#86859 (Add a regression test for issue-69323) - rust-lang#86862 (re-export SwitchIntEdgeEffects) - rust-lang#86864 (Add missing code example for Write::write_vectored) - rust-lang#86874 (Bump deps) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
…crum Prepare beta 1.55.0 Included backports: * rust-lang#86696 * rust-lang#87390 (squashed) Reverted: * rust-lang#86623 cc `@rust-lang/release` `@Mark-Simulacrum`
…bini Remove git fetch from CI rust-lang#86623 added a call to `git fetch`, which is problematic for releases. r? `@pietroalbini`
…bini Remove git fetch from CI rust-lang#86623 added a call to `git fetch`, which is problematic for releases. r? ``@pietroalbini``
Remove git fetch from CI rust-lang#86623 added a call to `git fetch`, which is problematic for releases. r? `@pietroalbini`
The error explanations are useful in case you use older version of the compiler. Even more if they had an explanation. If they are not emitted, their explanations should be updated but not removed (as we did for a few of them, like E0001).
r? @Mark-Simulacrum