-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Colliding filenames cause a panic when a build is re-run #10231
Comments
I found this with crater among the published versions on crates.io. You can use |
After an investigation, this panic exists for a long time since 1.36.0 released. Although it acts like a "hard error" but I don't think we can turn the warning to an error until an actual fix is landed. |
It looks like these packages set both In the future, there might be something like #9778 which would allow setting different filenames for things like cdylibs, but it isn't supported now (and might be difficult to add). |
@rustbot claim |
Problem
When cargo emits a warning about output filename collision, running a second build produces a panic inside cargo.
Steps
Download either one of
chipo-2.1.0
orparanoia-caller-0.1.0
, runcargo build
twice. The first run emits a warning, the second panics.Possible Solution(s)
Promote the warning to a hard error.
Notes
This was found browsing crater outputs. Here are the two published crates that produce the error:
https://crater-reports.s3.amazonaws.com/beta-1.58-1/1.57.0/reg/chipo-2.1.0/log.txt
https://crater-reports.s3.amazonaws.com/beta-1.58-1/1.57.0/reg/paranoia-caller-0.1.0/log.txt
Version
The text was updated successfully, but these errors were encountered: