`./mach lint` spews a lot of errors on windows
Categories
(Developer Infrastructure :: Lint and Formatting, defect, P3)
Tracking
(Not tracked)
People
(Reporter: bryce, Unassigned)
Details
Attachments
(2 files)
2020-11-03 central, bootstrap after pull, using mozilla build. When running ./mach lint on the central commit gives me a lot of errors. I figure linting central is not a normal workflow (ran across this while trying to debug linting issues), but this many failures makes me think there's something wrong.
I note that the errors include not being able to see cargo, which my normal build can see. I wonder if this is symptomatic of something going wrong with paths.
Attached output of a ./mach lint 2>&1 | tee lintOutput.txt.
Comment 1•5 years ago
|
||
The severity field is not set for this bug.
:ahal, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 2•5 years ago
|
||
Looks like there are multiple failures related to cargo and black. I know there have been recent fixes related to black on Windows that (I believe) have landed since this was filed.. so those ones may be fixed at least. Not sure it isn't finding cargo though. Have you run ./mach bootstrap?
| Reporter | ||
Comment 3•5 years ago
|
||
Retesting after a hg pull + ./mach bootstrap today and attaching output. Cargo isn't on my path in my build env, but ./mach finds it when doing others tasks like builds. Does linting expect it to be on the path?
Updated•4 years ago
|
Description
•