On Mon, Jul 16, 2018, 11:33 AM Lalatendu Mohanty <lmohanty at redhat.com> wrote: > Hi, > > On Mon, Jul 16, 2018 at 5:31 AM, <ci at centos.org> wrote: > >> The build has failed. Check the build URL for failure logs: >> https://ci.centos.org/job/minishift-nightly-centos/218/ > > > Our nightly builds are failing because of a CICO issue. Here is the error > from last test run. > > *00:01:21* ++ cico node get -f value -c ip_address -c comment --retry-count 12*00:01:25* Starting new HTTP connection (1): admin.ci.centos.org*00:01:28* Resetting dropped connection: admin.ci.centos.org*00:01:30* + [[ '' != '' ]]*00:01:30* + echo 'CICO: Unable to get Node.'*00:01:30* CICO: Unable to get Node.*00:01:30* + exit 1*00:01:30* Build step 'Execute shell' marked build as failure*00:01:30* Email was triggered for: Failure - Any*00:01:30* Sending email for trigger: Failure - Any > xxxxxx > *00:01:31* Finished: FAILURE > > > We have been seeing issues like this for our nightly runs. Refer [1]. How > can we fix the issue from CentOS ci side? > Most of time this is cause of failure, looks like a certain time nodes are not allocated, better to ask Fabian or any other person who is responsible for ci infra. > [1] https://ci.centos.org/job/minishift-nightly-centos/218/ > > -Lala > > > _______________________________________________ > Ci-users mailing list > Ci-users at centos.org > https://lists.centos.org/mailman/listinfo/ci-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/ci-users/attachments/20180716/c0718ac9/attachment-0002.html>