Colliding filenames cause a panic when a build is re-run #10231
Labels
A-diagnostics
Area: Error and warning messages generated by Cargo itself.
A-layout
Area: target output directory layout, naming, and organization
C-bug
Category: bug
E-easy
Experience: Easy
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: