I tried this locally, and am not able to reproduce the failure. $ git status On branch stable/beryllium ...
------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.opendaylight.sfc.util.openflow.SfcOpenflowUtilsTest Tests run: 49, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.208 sec - in org.opendaylight.sfc.util.openflow.SfcOpenflowUtilsTest Results : Tests run: 49, Failures: 0, Errors: 0, Skipped: 0 Could there be some sort of infrastructure problems here? The stack trace is kindof strange, the failure isnt anywhere in the SFC code: 03:11:56 org.opendaylight.sfc.util.openflow.SfcOpenflowUtilsTest Time elapsed: 0.053 sec <<< ERROR! 03:11:56 java.lang.NullPointerException: null 03:11:56 at junitparams.internal.ParameterisedTestMethodRunner.findChildForParams(ParameterisedTestMethodRunner.java:66) 03:11:56 at junitparams.internal.ParameterisedTestMethodRunner.runTestMethod(ParameterisedTestMethodRunner.java:40) 03:11:56 at junitparams.internal.ParameterisedTestClassRunner.runParameterisedTest(ParameterisedTestClassRunner.java:143) 03:11:56 at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:393) 03:11:56 at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:371) 03:11:56 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) 03:11:56 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) 03:11:56 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) 03:11:56 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) 03:11:56 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) 03:11:56 at org.junit.runners.ParentRunner.run(ParentRunner.java:309) 03:11:56 at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) 03:11:56 at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) 03:11:56 at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) 03:11:56 at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) 03:11:56 at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) 03:11:56 at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) 03:11:56 at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Regards, Brady -----Original Message----- From: David Suarez Fuentes <david.suarez.fuen...@ericsson.com<mailto:david%20suarez%20fuentes%20%3cdavid.suarez.fuen...@ericsson.com%3e>> To: thanh...@linuxfoundation.org <thanh...@linuxfoundation.org<mailto:%22thanh...@linuxfoundation.org%22%20%3cthanh...@linuxfoundation.org%3e>>, sfc-dev@lists.opendaylight.org <sfc-dev@lists.opendaylight.org<mailto:%22sfc-...@lists.opendaylight.org%22%20%3csfc-...@lists.opendaylight.org%3e>> Cc: rele...@lists.opendaylight.org <rele...@lists.opendaylight.org<mailto:%22rele...@lists.opendaylight.org%22%20%3crele...@lists.opendaylight.org%3e>> Subject: Re: [release] Autorelease beryllium failed to build sfc-openflow-utils Date: Fri, 3 Mar 2017 08:24:33 +0000 Hi Thanh, I am looking at it. Regards, David Suárez. On jue, 2017-03-02 at 23:20 -0500, Thanh Ha wrote: Adding sfc-dev. Thanh On Thu, Mar 2, 2017 at 10:12 PM, Jenkins <jenkins-dontreply@opendayli ght.org> wrote: Attention OpenDaylight-devs, Autorelease beryllium failed to build sfc-openflow-utils in build 164. 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 -beryllium/164 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-ber yllium/164/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team _______________________________________________ release mailing list rele...@lists.opendaylight.org<mailto:rele...@lists.opendaylight.org> https://lists.opendaylight.org/mailman/listinfo/release _______________________________________________ release mailing list rele...@lists.opendaylight.org<mailto:rele...@lists.opendaylight.org> https://lists.opendaylight.org/mailman/listinfo/release _______________________________________________ release mailing list rele...@lists.opendaylight.org<mailto:rele...@lists.opendaylight.org> https://lists.opendaylight.org/mailman/listinfo/release
_______________________________________________ sfc-dev mailing list sfc-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/sfc-dev
