[
https://ovirt-jira.atlassian.net/browse/OVIRT-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35286#comment-35286
]
Barak Korren commented on OVIRT-1655:
-------------------------------------
[[email protected]] Maybe I did not explain things clearly. The exception
you see in the groovy code is the result of the execution slave not being
available any more by the time the Groovy code runs. It seem that something
that the job was doing caused the slave to lose network connectivity with
Jenkins. That is the kind of exception we cannot really anticipate of handle
properly.
The groovy exception is not the reason behind longs not being available, the
slave not being available to pull logs from is...
In any case the failing run was not kept, so we cannot debug further. Next time
please mark it to be kept forever and set the description to clearly link to
the relevant Jira ticket.
Closing this ticket with CANNOT-REPRODUCE. Please re-open if the issue
re-occurs.
> Groovy script failed
> --------------------
>
> Key: OVIRT-1655
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1655
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: sbonazzo
> Assignee: infra
>
> Hi, I had an ovirt-node-ng build failure and didn't get logs about what
> happened due to:
> *Groovy script failed:*
> java.lang.NullPointerException: Cannot invoke method child() on null object
> Failed job is
> http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64/279/
> CAn you please check what happened?
> --
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
> Red Hat EMEA <https://www.redhat.com/>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
