-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Remove borrowck_graphviz_postflow
from test
#65629
Conversation
We should probably lint against this in tidy perhaps? Let's leave that for a future PR though @bors r+ for now |
📌 Commit 51a5b49 has been approved by |
Feels like the cleaner way to handle this is via |
The problem here isn't that the files are getting committed -- it is there existence that is the issue. gitignore does not help with their existence, only hides the problem. |
Doesn't feel like their existence is the problem tbh (although not adding junk to the git root is good); it feels like them dirtying up |
…ark-Simulacrum Remove `borrowck_graphviz_postflow` from test Resolves rust-lang#65071 (again). Sorry. I've added a commit hook to prevent this from happening in the future. r? @petrochenkov
Rollup of 8 pull requests Successful merges: - #65314 (rustdoc: forward -Z options to rustc) - #65592 (clarify const_prop ICE protection comment) - #65603 (Avoid ICE when include! is used by stdin crate) - #65614 (Improve error message for APIT with explicit generic arguments) - #65629 (Remove `borrowck_graphviz_postflow` from test) - #65633 (Remove leading :: from paths in doc examples) - #65638 (Rename the default argument 'def' to 'default') - #65639 (Fix parameter name in documentation) Failed merges: r? @ghost
Check all files in `src/test` for `borrowck_graphviz_postflow` This attribute causes DOT files to be generated in the top-level directory. It is intended to be used only temporarily and should never appear on master. This also tells git to ignore DOT files in the root or the `mir_dump` directory, which `-Z dump-mir` uses by default. This will prevent #65071 from occurring again. It needs to be merged after #65629, otherwise `tidy` will start failing. r? @Mark-Simulacrum
Resolves #65071 (again).
Sorry. I've added a commit hook to prevent this from happening in the future.
r? @petrochenkov