Skip to content

make tidy trips over Emacs lockfile with opaque message #38417

Closed
@zackmdavis

Description

@zackmdavis

Emacs drops a broken symlink in a file's directory to indicate that the file has unsaved changes. When scanning Rust source files for features, the rustc development tidy tool will fail if such a lockfile exists in the source tree, with (this part being the actual bug, being that a dirty tree should fail tidy) a message that doesn't make it clear what happened:

thread 'main' panicked at 'File::open(file) failed with No such file or directory (os error 2)', /home/zmd/Code/rust/src/tools/tidy/src/features.rs:71

(The novice compiler developer wonders: what file?)

I think this is likely too obscure to be worth doing anything about, but somehow managed to fall slightly over my subjective threshold of "worth filing an Issue for"; sorry if I'm miscalibrated in this matter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions