Properties
Properties
Drydock: Run Command
Drydock: Run Command
- When
- Completed at May 18 2016, 9:43 AM · Built for 27 s
- Status
Failed
| 82 | Switched to a new branch 'pykolab-0.7' |
|---|---|
| 83 | http://download.fedoraproject.org/pub/epel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 302 - Found |
| 84 | Trying other mirror. |
| 85 | |
| 86 | |
| 87 | One of the configured repositories failed (Extra Packages for Enterprise Linux 7 - x86_64), |
| 88 | and yum doesn't have enough cached data to continue. At this point the only |
| 89 | safe thing yum can do is fail. There are a few ways to work "fix" this: |
| 90 | |
| 91 | 1. Contact the upstream for the repository and get them to fix the problem. |
| 92 | |
| 93 | 2. Reconfigure the baseurl/etc. for the repository, to point to a working |
| 94 | upstream. This is most often useful if you are using a newer |
| 95 | distribution release than is supported by the repository (and the |
| 96 | packages for the previous distribution release still work). |
| 97 | |
| 98 | 3. Disable the repository, so yum won't use it by default. Yum will then |
| 99 | just ignore the repository until you permanently enable it again or use |
| 100 | --enablerepo for temporary usage: |
| 101 | |
| 102 | yum-config-manager --disable epel |
| 103 | |
| 104 | 4. Configure the failing repository to be skipped, if it is unavailable. |
| 105 | Note that yum will try to contact the repo. when it runs most commands, |
| 106 | so will have to try and fail each time (and thus. yum will be be much |
| 107 | slower). If it is a very temporary problem though, this is often a nice |
| 108 | compromise: |
| 109 | |
| 110 | yum-config-manager --save --setopt=epel.skip_if_unavailable=true |
| 111 | |
| 112 | failure: repodata/repomd.xml from epel: [Errno 256] No more mirrors to try. |
| 113 | http://download.fedoraproject.org/pub/epel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 302 - Found |
| 114 | Note: checking out '67e65cd5271658bd106a42f427904cf0374c8cd2'. |
| 115 | |
| 116 | You are in 'detached HEAD' state. You can look around, make experimental |
| 117 | changes and commit them, and you can discard any commits you make in this |
| 118 | state without impacting any branches by performing another checkout. |
| 119 | |
| 120 | If you want to create a new branch to retain commits you create, you may |
| 121 | do so (now or later) by using -b with the checkout command again. Example: |
| 122 | |
| 123 | git checkout -b new_branch_name |
| 124 | |
| 125 | HEAD is now at 67e65cd... Determine shared folder resource using kolabTargetFolder attribute (#5337) |
| 126 | cat: /tmp/report.log: No such file or directory |
| 127 | + exit 1 |
| 128 | + retval=1 |
| 129 | + popd |
| 130 | + exit 1 |
| 131 |
| 1 | /var/drydock/workingcopy-215829/repo/pykolab/pykolab.git /var/drydock/workingcopy-215829/repo/pykolab |
|---|---|
| 2 | HEAD is now at 67e65cd Determine shared folder resource using kolabTargetFolder attribute (#5337) |
| 3 | /var/drydock/workingcopy-215829/repo/pykolab |
| 4 | /var/drydock/workingcopy-215829/repo/pykolab/stick.git /var/drydock/workingcopy-215829/repo/pykolab |
| 5 | HEAD is now at 7205806 Add a kickstart to provision a phoenix system |
| 6 | /var/drydock/workingcopy-215829/repo/pykolab |
| 7 | /var/drydock/workingcopy-215829/repo/pykolab/pykolab.git /var/drydock/workingcopy-215829/repo/pykolab |
| 8 | Cloning into '/srv/stick.git'... |
| 9 | Cloning into '/srv/pykolab.git'... |
| 10 | /srv/pykolab.git /srv/closure-compiler.git |
| 11 | Branch dev/boddie set up to track remote branch dev/boddie from origin. |
| 12 | Branch dev/boddie-new/combined set up to track remote branch dev/boddie-new/combined from origin. |
| 13 | Branch dev/boddie-new/setup set up to track remote branch dev/boddie-new/setup from origin. |
| 14 | Branch dev/confmgmt set up to track remote branch dev/confmgmt from origin. |
| 15 | Branch dev/entitlements set up to track remote branch dev/entitlements from origin. |
| 16 | Branch dev/kolab-test-suite set up to track remote branch dev/kolab-test-suite from origin. |
| 17 | Branch dev/kolab-test-tools set up to track remote branch dev/kolab-test-tools from origin. |
| 18 | Branch pykolab-0.2 set up to track remote branch pykolab-0.2 from origin. |
| 19 | Branch pykolab-0.3 set up to track remote branch pykolab-0.3 from origin. |
| 20 | Branch pykolab-0.4 set up to track remote branch pykolab-0.4 from origin. |
| 21 | Branch pykolab-0.5 set up to track remote branch pykolab-0.5 from origin. |
| 22 | Branch pykolab-0.6 set up to track remote branch pykolab-0.6 from origin. |
| 23 | Branch pykolab-0.7 set up to track remote branch pykolab-0.7 from origin. |
| 24 | /srv/closure-compiler.git |
| 25 | Loaded plugins: ovl, priorities |
| 26 | Cleaning repos: Kolab_16 Kolab_3.4 Kolab_3.4_Updates Kolab_Winterfell base epel |
| 27 | : extras openSUSE_Tools updates |
| 28 | 0 metadata files removed |
| 29 | 0 sqlite files removed |
| 30 | 0 metadata files removed |
| 31 | Loaded plugins: ovl, priorities |
| 32 | /srv/pykolab.git /srv/closure-compiler.git |
| 33 | ======================================================================== |
| 34 | ======================================================================== |
| 35 | /var/drydock/workingcopy-215829/repo/pykolab |
| 36 |
Lease Working Copy
Lease Working Copy
- When
- Completed at May 18 2016, 9:43 AM · Built instantly
- Status
Passed
Wait for Previous Commits to Build
Wait for Previous Commits to Build
- When
- Completed at May 18 2016, 9:43 AM · Built instantly
- Status
Passed