On 2 Mar 2020, at 09:40, Michal Skrivanek <michal.skrivanek@redhat.com> wrote:

On 1 Mar 2020, at 17:54, Scott Dickerson <sdickers@redhat.com> wrote:

Hi,

On the merge phase on patch [1], both the el7 and fc30 build have been failing.  Examples are [2] and [3].  I'm guessing there are environmental issues that I can't fix from the project's perspective.  Typical example of the error from the log:

it seems to fail randomly, in run 93 el8 and fc30 fails while el7 and fc29 succeeds, in run 94 it’s fc30 that’s failing and el8 succeeded.

[2020-03-01T15:55:19.475Z] + yarn install --pure-lockfile --har
[2020-03-01T15:55:19.475Z] + /home/jenkins/workspace/ovirt-engine-nodejs-modules_standard-on-merge/ovirt-engine-nodejs-modules/yarn-1.17.3.js install --pure-lockfile --har
[2020-03-01T15:55:19.475Z] yarn install v1.17.3
[2020-03-01T15:55:19.475Z] [1/5] Resolving packages...
[2020-03-01T15:55:19.475Z] [2/5] Fetching packages...
[2020-03-01T15:55:19.475Z] error An unexpected error occurred: "https://registry.yarnpkg.com/@patternfly/react-core/-/react-core-3.134.2.tgz: unexpected end of file".

Running the build in mock_runner locally targeted for el7, el8, fc29 and fc30 work just fine.

Help please!

[1] - https://gerrit.ovirt.org/#/c/107309/

[2] - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine-nodejs-modules_standard-on-merge/detail/ovirt-engine-nodejs-modules_standard-on-merge/88/pipeline

[3] - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine-nodejs-modules_standard-on-merge/detail/ovirt-engine-nodejs-modules_standard-on-merge/92/pipeline 

--

Scott Dickerson

Senior Software Engineer

RHV-M Engineering - UX Team
Red Hat, Inc