Closed Bug 1244746 Opened 6 years ago Closed 6 years ago
.1 .2 -> 8 .0 .2 errors make using treeherder's log viewer more difficult
58 bytes, text/x-review-board-request
https://treeherder.mozilla.org/logviewer.html#?job_id=16163275&repo=try Jumps me to an error about pip versions: 15:31:33 ERROR - Errors received: 15:31:33 INFO - Reading from file tmpfile_stderr 15:31:33 ERROR - You are using pip version 7.1.2, however version 8.0.2 is available. 15:31:33 ERROR - You should consider upgrading via the 'pip install --upgrade pip' command. I don't really care about this error, it's out of my control, and it doesn't actually cause problems for the build. Worse, Treeherder's log viewer thinks this is the interesting error that caused my build to fail, and wants to direct my attention to it. Can we either ignore stderr from pip invocations, patch pip to not emit this message, or upgrade? (Why is our version of pip even informing us about new versions, anyway?)
Greg - was this fixed in recent changes to th/tc log processing?
This is an error matching regular expression that was not added by our team and is something living in treeherder. It catches all errors and displays them rather than just when the task itself has failed. The harness outputs this error but chooses to not treat it as fatal. As far as something on the taskcluster side, the image should/could be updated to have a newer version of pip.
Moving over to TH. I'll add a bug to update pip.
Component: General → Treeherder: Log Viewer
Product: Taskcluster → Tree Management
Version: unspecified → ---
This is a mozharness (or some other upstream script) issue. Treeherder is correctly highlighting lines that have the mozharness error prefix, such as: 15:31:33 ERROR - Errors received: This line should have been output as: 15:31:33 INFO - Errors received: ...if it wasn't an issue. (Or to be more precise, the mozharness log strings should match the exit code; either it's an error or it's not).
Component: Treeherder: Log Viewer → Mozharness
Product: Tree Management → Release Engineering
QA Contact: jlund
Upgrading pip is overall the best solution. Mozharness could run |pip install --upgrade pip| after venv creation, or we can upgrade pip in bug 1269853. I think the latter is cleaner. To stem the bleeding sooner, we may be able to add |--disable-pip-version-check| to the |pip freeze| command in mozharness. (Looks like :emorley fixed this in travis: https://github.com/travis-ci/travis-ci/issues/5499 :) That fix would address this symptom and make upgrading pip less urgent.
Review commit: https://reviewboard.mozilla.org/r/50269/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/50269/
Comment on attachment 8748418 [details] MozReview Request: bug 1244746 - silence mozharness pip upgrade errors in pip freeze. r?jlund From try: |pip: error: no such option: --disable-pip-version-check| https://treeherder.mozilla.org/logviewer.html#?job_id=20316661&repo=try#L396
Setting PIP_DISABLE_PIP_VERSION_CHECK=1 in env seems to break windows for some reason. Trying ignore_errors=True, which is my last quick'n'dirty fix idea.
Review commit: https://reviewboard.mozilla.org/r/50319/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/50319/
Attachment #8748487 - Flags: review?(jlund)
Attachment #8748418 - Attachment is obsolete: true
Comment on attachment 8748487 [details] MozReview Request: bug 1244746 - mozharness pip freeze ignore_errors=True. r?jlund https://reviewboard.mozilla.org/r/50319/#review47285 r+ as a stop gap for Bug 1269853
Attachment #8748487 - Flags: review?(jlund) → review+
(In reply to Aki Sasaki [:aki] from comment #10) > Setting PIP_DISABLE_PIP_VERSION_CHECK=1 in env seems to break windows for > some reason. Perhaps needed to set "1" instead of 1. The other issue I've hit is unicode strings making it barf.
https://hg.mozilla.org/try/rev/b05608eb2c8d3d8cedb4ca5eb6bd4b1586eaee48 Probably the latter. Or maybe I needed to self.query_env(...) to not drop the other env vars on the floor.
Wow, that's really weird, and quite different from what i hit.
You need to log in before you can comment on or make changes to this bug.