Closed
Bug 2085857
Opened 23 days ago
Closed 21 days ago
Run yamllint in process
Categories
(Developer Infrastructure :: Lint and Formatting, enhancement)
Developer Infrastructure
Lint and Formatting
Tracking
(firefox161 fixed)
RESOLVED
FIXED
161 Branch
| Tracking | Status | |
|---|---|---|
| firefox161 | --- | fixed |
People
(Reporter: ahochheiden, Assigned: ahochheiden)
References
(Blocks 1 open bug)
Details
Attachments
(1 external file)
Each yamllint job starts a second mach to run yamllint, which costs about a second each.
| Assignee | ||
Comment 1•23 days ago
|
||
Every yamllint job started a second mach through mach python to run the
vendored yamllint, which took about a second before yamllint ran. The
linter now calls the yamllint API the way its command line does. The
results also no longer collect in a module global, which reported the
issues of an earlier job again when a worker ran more than one.
Pushed by ahochheiden@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/daf09d52f5d3
https://hg.mozilla.org/integration/autoland/rev/241c4b049569
Run yamllint in process r=linter-reviewers,sergesanspaille
Comment 3•21 days ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 21 days ago
status-firefox161:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 161 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•