diffoscope tasks always contain failure line: TypeError: hilite() got an unexpected keyword argument 'ok'
Categories
(Firefox Build System :: Task Configuration, defect)
Tracking
(firefox-esr68 unaffected, firefox73 unaffected, firefox74 unaffected, firefox75 wontfix, firefox76 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr68 | --- | unaffected |
| firefox73 | --- | unaffected |
| firefox74 | --- | unaffected |
| firefox75 | --- | wontfix |
| firefox76 | --- | fixed |
People
(Reporter: aryx, Assigned: glandium)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Since bug 1620513 landed, diffoscope tasks always contain the line TypeError: hilite() got an unexpected keyword argument 'ok' which gets detected by Treeherder as an issue due to the TypeError. This will confuse if the Diffoscope task actually fails.
Comment 1•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
| Assignee | ||
Comment 2•6 years ago
|
||
The root cause is a bug in psutil. Filed https://github.com/giampaolo/psutil/issues/1714.
| Assignee | ||
Comment 3•6 years ago
|
||
We can, however, workaround the message on our end.
| Assignee | ||
Comment 4•6 years ago
|
||
Creating the virtualenv prints an error message in the diffoscope docker
image because it doesn't have a compiler or the python development
headers, and that triggers an error setting up psutil after bug 1620513,
which in turn leads to a noisy and unrelated error message appearing in
the diffoscope jobs when they fail.
We don't need psutil set up really in those jobs, let alone a full
fledged virtualenv, so we can avoid the psutil error message by
disabling the virtualenv.
Updated•6 years ago
|
Comment 6•6 years ago
|
||
| bugherder | ||
Comment 7•6 years ago
|
||
AFAIK we don't run diffoscope on beta.
Updated•6 years ago
|
Updated•6 years ago
|
Description
•