[ 
https://issues.apache.org/jira/browse/IMPALA-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669344#comment-16669344
 ] 

Philip Zeyliger commented on IMPALA-7787:
-----------------------------------------

I added a retry loop (5 retries; sleep 30 seconds between) and separated out 
the "docker pull". We're dependent on the Docker public repos here, but perhaps 
their windows of failure are small enough that this will help.

> python26-incompatibility-check failed because of docker 503 Service 
> Unavailable
> -------------------------------------------------------------------------------
>
>                 Key: IMPALA-7787
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7787
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Tim Armstrong
>            Assignee: Philip Zeyliger
>            Priority: Major
>              Labels: flaky
>
> https://jenkins.impala.io/job/python26-incompatibility-check/529
> https://jenkins.impala.io/job/python26-incompatibility-check/528
> {noformat}
> 15:50:37 Initialized empty Git repository in /tmp/tmp.MKJUMZ3SBi/.git/
> 15:50:37 + git fetch http://gerrit.cloudera.org:8080/Impala-ASF 
> refs/changes/00/11800/5
> 15:50:54 From http://gerrit.cloudera.org:8080/Impala-ASF
> 15:50:54  * branch            refs/changes/00/11800/5 -> FETCH_HEAD
> 15:50:54 + git archive --prefix=impala/ -o /tmp/impala.tar FETCH_HEAD
> 15:50:54 + docker run -u nobody -v /tmp/impala.tar:/tmp/impala.tar centos:6 
> bash -o pipefail -c 'cd /tmp; python -c '\''import 
> tarfile;tarfile.TarFile("/tmp/impala.tar").extractall()'\''; python -m 
> compileall /tmp/impala'
> 15:50:54 Unable to find image 'centos:6' locally
> 15:50:55 docker: Error response from daemon: Get 
> https://registry-1.docker.io/v2/library/centos/manifests/6: received 
> unexpected HTTP status: 503 Service Unavailable.
> 15:50:55 See 'docker run --help'.
> 15:50:55 Build step 'Execute shell' marked build as failure
> 15:50:55 Set build name.
> 15:50:55 New build name is '#529 refs/changes/00/11800/5'
> 15:50:57 Finished: FAILURE
> {noformat}
> This happened a couple of times. Looks like flakiness but unsure if it was 
> just a transient infra issue or something we're doing wrong.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to