[release] Autorelease oxygen failed to build odl-alto-simpleecs from alto
|
Jenkins <jenkins-dontreply@...>
Attention alto-devs,
Autorelease oxygen failed to build odl-alto-simpleecs from alto in build 24. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/jenkins092/autorelease-release-oxygen/24 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-oxygen/24/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team |
|
|
|
Gao Kai
It seems to me that the error is not directly related to the
odl-alto-simpleecs feature. The stack trace seems to indicate that
the error occurs when the test is already finished but collapses
during the clean-up. Unfortunately no ETA can be provided. Regards, On 10/22/2017 09:24 AM, Jenkins wrote:
Attention alto-devs, Autorelease oxygen failed to build odl-alto-simpleecs from alto in build 24. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/jenkins092/autorelease-release-oxygen/24 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-oxygen/24/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team |
|
|
|
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES@Cisco) <vrpolak@...>
> The stack trace seems to indicate that the error occurs > when the test is already finished but collapses during the clean-up.
Which stack trace? Looking at surefire report [2], it seems to be cut off at a benign place (bundle installation, before any ODL code is executed).
Perhaps there was a genuine loss of network connectivity due to some infra problem?
Vratko.
From:
release-bounces@... [mailto:release-bounces@...]
On Behalf Of Kai
It seems to me that the error is not directly related to the odl-alto-simpleecs feature. The stack trace seems to indicate that the error occurs when the test is already finished but collapses during the clean-up. Unfortunately no ETA can be provided. Regards,
On 10/22/2017 09:24 AM, Jenkins wrote:
|
|
|
|
Kai Gao <gaok12@...>
On 10/24/2017 01:03 AM, Vratko Polak -X
(vrpolak - PANTHEON TECHNOLOGIES at Cisco) wrote:
I was looking at the console log from the Jenkins page. A similar error happens in the nitrogen build as well. Could be. However, I would be curious to know why the errors happen on (different) ALTO features. Could be related to resources.
|
|
|