Closed Bug 1518762 Opened 11 months ago Closed 11 months ago

resourcemonitor.py:266: UserWarning: psutil failed to run: not sure how to interpret line

Categories

(Firefox Build System :: General, defect)

defect
Not set

Tracking

(firefox66 fixed, firefox68 fixed)

RESOLVED FIXED
mozilla66
Tracking Status
firefox66 --- fixed
firefox68 --- fixed

People

(Reporter: robwu, Assigned: robwu)

Details

Attachments

(1 file)

When I run "mach build", the following warning is printed by testing/mozbase/mozsystemmonitor/mozsystemmonitor/resourcemonitor.py:26:

UserWarning: psutil failed to run: not sure how to interpret line '...'

This is apparently caused by the fact that my Linux system has kernel version 4.18+, which triggers this bug: https://github.com/giampaolo/psutil/issues/1354

Assignee: nobody → rob
Status: NEW → ASSIGNED
Attachment #9035276 - Attachment description: Bug 1518762 - Catch error in psutil.disk_io_counters in resourcemonitor → Bug 1518762 - Avoid error in psutil.disk_io_counters in resourcemonitor
Pushed by rob@robwu.nl:
https://hg.mozilla.org/integration/autoland/rev/e26eda77b71c
Avoid error in psutil.disk_io_counters in resourcemonitor r=ahal
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
https://hg.mozilla.org/projects/cedar/rev/e26eda77b71c6c02db69441236dd95fc0db5c7f2
Bug 1518762 - Avoid error in psutil.disk_io_counters in resourcemonitor r=ahal

This is third-party code, has the fix been upstreamed?

Flags: needinfo?(rob)

Yes. The change is based on an upstream patch that is referenced in the commit message:

Bug 1518762 - Avoid error in psutil.disk_io_counters in resourcemonitor r=ahal

Imports https://github.com/giampaolo/psutil/commit/8f99f3782663959062ee868bbfdbc336307a3a4d
to fix a bug with Linux kernel 4.18+, https://github.com/giampaolo/psutil/issues/1354
(to be included in a future release of psutil, version 5.5.0)

Differential Revision: https://phabricator.services.mozilla.com/D16028

Flags: needinfo?(rob)
You need to log in before you can comment on or make changes to this bug.