Remove pip errors from mochitest logs

RESOLVED FIXED

Status

Taskcluster
General
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: RyanVM, Assigned: lightsofapollo)

Tracking

(Blocks: 1 bug)

Details

(Reporter)

Description

3 years ago
On a B2G mochitest runs, numerous setup warnings add noise and make it more difficult to quickly see what's failing in a run. We need to silence them or at least train Treeherder's log parser to ignore them. The below all appear prior to the actual test failures in a run.

--------------

list index out of range
Errors received:
The directory '/home/worker/.cache/pip/log' or its parent directory is not owned by the current user and the debug log has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want the -H flag.
The directory '/home/worker/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want the -H flag.
Return code: 0
Errors received:
The directory '/home/worker/.cache/pip/log' or its parent directory is not owned by the current user and the debug log has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want the -H flag.
The directory '/home/worker/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want the -H flag.
Return code: 0
I'm sure something could be done to silence this short term. Easiest is probably some in-tree hack
that hides this from the log :)

Long term we have to fix or defined permissions settings for cache folder mounts.
This work is tracked in bug 1093833.
Depends on: 1093833
My bad, this /home/worker/.cache/ is not cache folder.
Clearing bug 1093833 as blocking.
No longer depends on: 1093833
(Reporter)

Comment 3

3 years ago
This makes sheriffing TC jobs a massive PITA. Can we please prioritize this?
Flags: needinfo?(jlal)
(Assignee)

Updated

3 years ago
Assignee: nobody → jlal
Status: NEW → ASSIGNED
Flags: needinfo?(jlal)
(Assignee)

Comment 4

3 years ago
https://hg.mozilla.org/integration/b2g-inbound/rev/8169d9fae061
Summary: Lots of setup warning noise on B2G mochitest runs → Remove pip errors from mochitest logs
https://hg.mozilla.org/mozilla-central/rev/8169d9fae061
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
status-firefox39: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
(Reporter)

Comment 6

3 years ago
https://treeherder.mozilla.org/logviewer.html#?job_id=8198506&repo=mozilla-inbound indicates that this isn't fixed yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Updated

3 years ago
Blocks: 1148847
(Assignee)

Comment 7

3 years ago
marking this fixed the title reflects the work here I never actually updated the builder images with this log suppression (filed 1148847 to remove this from the builder logs...)
No longer blocks: 1148847
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 years ago
Resolution: --- → FIXED
status-firefox39: fixed → ---
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: mozilla39 → mozilla41
Resetting Version and Target Milestone that accidentally got changed...
Target Milestone: mozilla41 → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.