From e684725016d9da89eeacbca7662b078377d5abfd Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Fri, 4 Aug 2017 09:16:15 -0700 Subject: [PATCH] Refactor how we track pip errors There are two major class of pip error, the first is fatal the second is not. First we have the complete inability to find a distribution for a package. This can happen due to network errors or the package simply not existing. Track that in 1449136 our long standing pip had a problem bug. Second there is the pip had a retriable network problem and is retrying. By default 5 attempts are made and typically pip will eventually succeed. If it does not succeed it logs the error from the first issue. We track this retry issue in 1708686 because while not fatal it may indicate larger underlying problems we should be aware of but also don't want it distracting from actual failures in jobs. Change-Id: I2dbe4b887ed868bd57c58a79a6f2b5600366e116 Related-bug: 1449136 Related-bug: 1708686 --- queries/1449136.yaml | 4 ++-- queries/1708686.yaml | 4 ++++ 2 files changed, 6 insertions(+), 2 deletions(-) create mode 100644 queries/1708686.yaml diff --git a/queries/1449136.yaml b/queries/1449136.yaml index ab5e59ce..9cee042e 100644 --- a/queries/1449136.yaml +++ b/queries/1449136.yaml @@ -1,3 +1,3 @@ query: >- - message:"ReadTimeoutError: HTTPConnectionPool" - AND tags:console \ No newline at end of file + message:"No matching distribution found for" + AND tags:console diff --git a/queries/1708686.yaml b/queries/1708686.yaml new file mode 100644 index 00000000..30e41407 --- /dev/null +++ b/queries/1708686.yaml @@ -0,0 +1,4 @@ +query: >- + message:"ReadTimeoutError: HTTPConnectionPool" + AND message:"pypi" + AND tags:console