buildbot failure in on ofbiz-branch16
Locked
 
|
The Buildbot has detected a new failure on builder ofbiz-branch16 while building . Full details are available at:
https://ci.apache.org/builders/ofbiz-branch16/builds/71 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: silvanus_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' triggered this build Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 Blamelist: mbrohl BUILD FAILED: failed shell_2 Sincerely, -The Buildbot |
Re: buildbot failure in on ofbiz-branch16
|
|
There seems to be a problem with shutting down previous instances:
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-nio-8080"] java.net.BindException: Address already in use SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-8080]] This should be covered with the latest activities from Jacques regarding shutdown, right? There is also a warning about gradle (no error, just a warning): The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. I'll file a Jira for this. Regards, Michael Brohl ecomify GmbH www.ecomify.de Am 26.06.17 um 10:19 schrieb [hidden email]: > The Buildbot has detected a new failure on builder ofbiz-branch16 while building . Full details are available at: > https://ci.apache.org/builders/ofbiz-branch16/builds/71 > > Buildbot URL: https://ci.apache.org/ > > Buildslave for this Build: silvanus_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' triggered this build > Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 > Blamelist: mbrohl > > BUILD FAILED: failed shell_2 > > Sincerely, > -The Buildbot > > > |
smime.p7s (5K)
Re: buildbot failure in on ofbiz-branch16
|
|
Done in https://issues.apache.org/jira/browse/OFBIZ-9433
Am 26.06.17 um 10:27 schrieb Michael Brohl: > There seems to be a problem with shutting down previous instances: > > SEVERE: Failed to initialize end point associated with ProtocolHandler > ["http-nio-8080"] java.net.BindException: Address already in use > > SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] > org.apache.catalina.LifecycleException: Failed to initialize component > [Connector[HTTP/1.1-8080]] > > This should be covered with the latest activities from Jacques > regarding shutdown, right? > > > There is also a warning about gradle (no error, just a warning): > > The Task.leftShift(Closure) method has been deprecated and is > scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) > instead. > > I'll file a Jira for this. > > Regards, > > Michael Brohl > ecomify GmbH > www.ecomify.de > > > Am 26.06.17 um 10:19 schrieb [hidden email]: >> The Buildbot has detected a new failure on builder ofbiz-branch16 >> while building . Full details are available at: >> https://ci.apache.org/builders/ofbiz-branch16/builds/71 >> >> Buildbot URL: https://ci.apache.org/ >> >> Buildslave for this Build: silvanus_ubuntu >> >> Build Reason: The AnyBranchScheduler scheduler named >> 'on-ofbiz16-commit' triggered this build >> Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 >> Blamelist: mbrohl >> >> BUILD FAILED: failed shell_2 >> >> Sincerely, >> -The Buildbot >> >> >> > > |
Re: buildbot failure in on ofbiz-branch16
Administrator
|
In reply to this post by Michael Brohl-3
Hi Michael,
Unfortunately it's unrelated. The change I made are only for the demos (trunk and stable). It's still not clear to me what is keeping the 8080 port open. I don't think it's a pending previous OFBiz instance. Because each build is started anew. At some point it was (not clear) another Tomcat instance running on the same machine: https://s.apache.org/YTqW BTW it started with INFRA-13573 One thing we could to is, before starting tests, to kill any process which keep the 8080 port open I did not do that yet, because it could interfere with another build (not OFBiz build) or something else on this VM You might say that it could be also that another OFBiz build is running on the same machine But it was not the case for the "last" trunk and R16 builds (both on silvanus_ubuntu) https://ci.apache.org/builders/ofbiz-trunk-framework-plugins https://ci.apache.org/builders/ofbiz-branch16 https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/186 Start Mon Jun 26 06:05:36 2017 End Mon Jun 26 06:14:27 2017 https://ci.apache.org/builders/ofbiz-branch16/builds/71 Start Mon Jun 26 08:13:43 2017 End Mon Jun 26 08:19:02 2017 https://ci.apache.org/builders/ofbiz-branch16/builds/72 Start Mon Jun 26 08:30:36 2017 End Mon Jun 26 08:36:01 2017 Also if it was OFBiz we would have issues with 8443 port and we have not I think we should ask infra if they agree about us killing any process which keeps the 8080 ports open on any Buildbot slave OFBiz uses, ie lares_ubuntu, orcus_ubuntu, and silvanus_ubuntu This was already suggested by Chris Lambertus https://s.apache.org/h0yU so I guess we have a chance... Jacques Le 26/06/2017 à 10:27, Michael Brohl a écrit : > There seems to be a problem with shutting down previous instances: > > SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-nio-8080"] java.net.BindException: Address already in use > > SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] org.apache.catalina.LifecycleException: Failed to initialize component > [Connector[HTTP/1.1-8080]] > > This should be covered with the latest activities from Jacques regarding shutdown, right? > > > There is also a warning about gradle (no error, just a warning): > > The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. > > I'll file a Jira for this. > > Regards, > > Michael Brohl > ecomify GmbH > www.ecomify.de > > > Am 26.06.17 um 10:19 schrieb [hidden email]: >> The Buildbot has detected a new failure on builder ofbiz-branch16 while building . Full details are available at: >> https://ci.apache.org/builders/ofbiz-branch16/builds/71 >> >> Buildbot URL: https://ci.apache.org/ >> >> Buildslave for this Build: silvanus_ubuntu >> >> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' triggered this build >> Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 >> Blamelist: mbrohl >> >> BUILD FAILED: failed shell_2 >> >> Sincerely, >> -The Buildbot >> >> >> > > |
|
In reply to this post by Michael Brohl-3
I think the buildbot scripts might be faulty. I'll work on refactoring
it to at least start using the embedded gradle wrapper with --no-daemon flag. We need to slowly isolate all causes On Mon, Jun 26, 2017 at 11:29 AM, Michael Brohl <[hidden email]> wrote: > Done in https://issues.apache.org/jira/browse/OFBIZ-9433 > > Am 26.06.17 um 10:27 schrieb Michael Brohl: > >> There seems to be a problem with shutting down previous instances: >> >> SEVERE: Failed to initialize end point associated with ProtocolHandler >> ["http-nio-8080"] java.net.BindException: Address already in use >> >> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] >> org.apache.catalina.LifecycleException: Failed to initialize component >> [Connector[HTTP/1.1-8080]] >> >> This should be covered with the latest activities from Jacques regarding >> shutdown, right? >> >> >> There is also a warning about gradle (no error, just a warning): >> >> The Task.leftShift(Closure) method has been deprecated and is scheduled to >> be removed in Gradle 5.0. Please use Task.doLast(Action) instead. >> >> I'll file a Jira for this. >> >> Regards, >> >> Michael Brohl >> ecomify GmbH >> www.ecomify.de >> >> >> Am 26.06.17 um 10:19 schrieb [hidden email]: >>> >>> The Buildbot has detected a new failure on builder ofbiz-branch16 while >>> building . Full details are available at: >>> https://ci.apache.org/builders/ofbiz-branch16/builds/71 >>> >>> Buildbot URL: https://ci.apache.org/ >>> >>> Buildslave for this Build: silvanus_ubuntu >>> >>> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' >>> triggered this build >>> Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 >>> Blamelist: mbrohl >>> >>> BUILD FAILED: failed shell_2 >>> >>> Sincerely, >>> -The Buildbot >>> >>> >>> >> >> > > |
Re: buildbot failure in on ofbiz-branch16
|
Administrator
|
Yes indeed, we already spoke about that in OFBIZ-9182 and it's surely better to use the Gradle wrapper (no need to ask infra to update Gradle) and to
avoid the daemon default. Not sure it will be enough though, I see no reason why a Gradle daemon would keep the 8080 port open (never happened to me locally), do you? Anyway, I agree cleaning that will remove questions on this subject Jacques Le 26/06/2017 à 12:39, Taher Alkhateeb a écrit : > I think the buildbot scripts might be faulty. I'll work on refactoring > it to at least start using the embedded gradle wrapper with > --no-daemon flag. We need to slowly isolate all causes > > On Mon, Jun 26, 2017 at 11:29 AM, Michael Brohl > <[hidden email]> wrote: >> Done in https://issues.apache.org/jira/browse/OFBIZ-9433 >> >> Am 26.06.17 um 10:27 schrieb Michael Brohl: >> >>> There seems to be a problem with shutting down previous instances: >>> >>> SEVERE: Failed to initialize end point associated with ProtocolHandler >>> ["http-nio-8080"] java.net.BindException: Address already in use >>> >>> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] >>> org.apache.catalina.LifecycleException: Failed to initialize component >>> [Connector[HTTP/1.1-8080]] >>> >>> This should be covered with the latest activities from Jacques regarding >>> shutdown, right? >>> >>> >>> There is also a warning about gradle (no error, just a warning): >>> >>> The Task.leftShift(Closure) method has been deprecated and is scheduled to >>> be removed in Gradle 5.0. Please use Task.doLast(Action) instead. >>> >>> I'll file a Jira for this. >>> >>> Regards, >>> >>> Michael Brohl >>> ecomify GmbH >>> www.ecomify.de >>> >>> >>> Am 26.06.17 um 10:19 schrieb [hidden email]: >>>> The Buildbot has detected a new failure on builder ofbiz-branch16 while >>>> building . Full details are available at: >>>> https://ci.apache.org/builders/ofbiz-branch16/builds/71 >>>> >>>> Buildbot URL: https://ci.apache.org/ >>>> >>>> Buildslave for this Build: silvanus_ubuntu >>>> >>>> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' >>>> triggered this build >>>> Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 >>>> Blamelist: mbrohl >>>> >>>> BUILD FAILED: failed shell_2 >>>> >>>> Sincerely, >>>> -The Buildbot >>>> >>>> >>>> >>> >> |
Re: buildbot failure in on ofbiz-branch16
|
Administrator
|
In reply to this post by taher
Hi Taher,
I saw your changes (wanted to do exactly the same so the resolving merge went perfectly well, rare thing :)) It was yesterday at 15:26:26 Revision: 1014588 Author: taher Date: mardi 27 juin 2017 15:26:26 Message: Replace all instances of gradle with ./gradlew --no-daemon for OFBiz builds ---- Modified : /infrastructure/buildbot/aegis/buildmaster/master1/projects/ofbiz.conf Then you committed Author: taher Date: Tue Jun 27 15:39:34 2017 New Revision: 1800073 URL:http://svn.apache.org/viewvc?rev=1800073&view=rev Log: Improved: refactored and improved the createPlugin task in gradle script (OFBIZ-9436) Without luck: https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/188 I discussed with the infra team (after some other issues due to Buildbot itself) and the tests issue is still a Tomcat instance running on Sylvanus (not Lares for instance) So we have still the same issue than INFRA-13496 <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-13496> and INFRA-13573 <https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-13573> They manually (so temporarily) stopped Tomcat on Sylvanus and my forced tests worked: https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/189 Here is our recurring problem https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 This is supposed to install Tomcat but not run it, somehow it does not totally work Compare with https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 I have created https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-14463 for that Jacques Le 26/06/2017 à 12:39, Taher Alkhateeb a écrit : > I think the buildbot scripts might be faulty. I'll work on refactoring > it to at least start using the embedded gradle wrapper with > --no-daemon flag. We need to slowly isolate all causes > > On Mon, Jun 26, 2017 at 11:29 AM, Michael Brohl > <[hidden email]> wrote: >> Done in https://issues.apache.org/jira/browse/OFBIZ-9433 >> >> Am 26.06.17 um 10:27 schrieb Michael Brohl: >> >>> There seems to be a problem with shutting down previous instances: >>> >>> SEVERE: Failed to initialize end point associated with ProtocolHandler >>> ["http-nio-8080"] java.net.BindException: Address already in use >>> >>> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] >>> org.apache.catalina.LifecycleException: Failed to initialize component >>> [Connector[HTTP/1.1-8080]] >>> >>> This should be covered with the latest activities from Jacques regarding >>> shutdown, right? >>> >>> >>> There is also a warning about gradle (no error, just a warning): >>> >>> The Task.leftShift(Closure) method has been deprecated and is scheduled to >>> be removed in Gradle 5.0. Please use Task.doLast(Action) instead. >>> >>> I'll file a Jira for this. >>> >>> Regards, >>> >>> Michael Brohl >>> ecomify GmbH >>> www.ecomify.de >>> >>> >>> Am 26.06.17 um 10:19 schrieb [hidden email]: >>>> The Buildbot has detected a new failure on builder ofbiz-branch16 while >>>> building . Full details are available at: >>>> https://ci.apache.org/builders/ofbiz-branch16/builds/71 >>>> >>>> Buildbot URL: https://ci.apache.org/ >>>> >>>> Buildslave for this Build: silvanus_ubuntu >>>> >>>> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' >>>> triggered this build >>>> Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 >>>> Blamelist: mbrohl >>>> >>>> BUILD FAILED: failed shell_2 >>>> >>>> Sincerely, >>>> -The Buildbot >>>> >>>> >>>> >>> >> |
Re: buildbot failure in on ofbiz-branch16
|
Administrator
|
BTW the "some other issues due to Buildbot itself" I had are still there. Buildbot does not autoreload on config change (not only OFBiz)
[5:47 PM] Daniel Takamori (pono): configscanner might be busted again [5:47 PM] Daniel Takamori (pono): it's affecting all the projects it looks like So be patient if you make a Buildbot config change. Hopefully the configscanner will be fixed then ;) Jacques Le 28/06/2017 à 17:32, Jacques Le Roux a écrit : > Hi Taher, > > I saw your changes (wanted to do exactly the same so the resolving merge went perfectly well, rare thing :)) > > It was yesterday at 15:26:26 > > Revision: 1014588 > Author: taher > Date: mardi 27 juin 2017 15:26:26 > Message: > Replace all instances of gradle with ./gradlew --no-daemon for OFBiz builds > ---- > Modified : /infrastructure/buildbot/aegis/buildmaster/master1/projects/ofbiz.conf > > Then you committed > > Author: taher > Date: Tue Jun 27 15:39:34 2017 > New Revision: 1800073 > > URL:http://svn.apache.org/viewvc?rev=1800073&view=rev > Log: > Improved: refactored and improved the createPlugin task in gradle script > (OFBIZ-9436) > > Without luck: https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/188 > > I discussed with the infra team (after some other issues due to Buildbot itself) and the tests issue is still a Tomcat instance running on Sylvanus > (not Lares for instance) > So we have still the same issue than > INFRA-13496 <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-13496> > > and > INFRA-13573 <https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-13573> > > They manually (so temporarily) stopped Tomcat on Sylvanus and my forced tests worked: > https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/189 > > Here is our recurring problem https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 > This is supposed to install Tomcat but not run it, somehow it does not totally work > Compare with https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 > I have created https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-14463 for that > > Jacques > > > Le 26/06/2017 à 12:39, Taher Alkhateeb a écrit : >> I think the buildbot scripts might be faulty. I'll work on refactoring >> it to at least start using the embedded gradle wrapper with >> --no-daemon flag. We need to slowly isolate all causes >> >> On Mon, Jun 26, 2017 at 11:29 AM, Michael Brohl >> <[hidden email]> wrote: >>> Done in https://issues.apache.org/jira/browse/OFBIZ-9433 >>> >>> Am 26.06.17 um 10:27 schrieb Michael Brohl: >>> >>>> There seems to be a problem with shutting down previous instances: >>>> >>>> SEVERE: Failed to initialize end point associated with ProtocolHandler >>>> ["http-nio-8080"] java.net.BindException: Address already in use >>>> >>>> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] >>>> org.apache.catalina.LifecycleException: Failed to initialize component >>>> [Connector[HTTP/1.1-8080]] >>>> >>>> This should be covered with the latest activities from Jacques regarding >>>> shutdown, right? >>>> >>>> >>>> There is also a warning about gradle (no error, just a warning): >>>> >>>> The Task.leftShift(Closure) method has been deprecated and is scheduled to >>>> be removed in Gradle 5.0. Please use Task.doLast(Action) instead. >>>> >>>> I'll file a Jira for this. >>>> >>>> Regards, >>>> >>>> Michael Brohl >>>> ecomify GmbH >>>> www.ecomify.de >>>> >>>> >>>> Am 26.06.17 um 10:19 schrieb [hidden email]: >>>>> The Buildbot has detected a new failure on builder ofbiz-branch16 while >>>>> building . Full details are available at: >>>>> https://ci.apache.org/builders/ofbiz-branch16/builds/71 >>>>> >>>>> Buildbot URL: https://ci.apache.org/ >>>>> >>>>> Buildslave for this Build: silvanus_ubuntu >>>>> >>>>> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' >>>>> triggered this build >>>>> Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 >>>>> Blamelist: mbrohl >>>>> >>>>> BUILD FAILED: failed shell_2 >>>>> >>>>> Sincerely, >>>>> -The Buildbot >>>>> >>>>> >>>>> >>>> >>> > > |
Re: buildbot failure in on ofbiz-branch16
|
Administrator
|
Orcus must have the same issue:
https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/orcus.apache.org.yaml#L27 BTW, I have launched the tests for the framework only https://ci.apache.org/builders/ofbiz-trunk-framework/builds/240 But I did not yet put in place the necessary to see the results at ci.apache.org/projects/ofbiz/logs/ Jacques Le 28/06/2017 à 17:49, Jacques Le Roux a écrit : > BTW the "some other issues due to Buildbot itself" I had are still there. Buildbot does not autoreload on config change (not only OFBiz) > > [5:47 PM] Daniel Takamori (pono): configscanner might be busted again > [5:47 PM] Daniel Takamori (pono): it's affecting all the projects it looks like > > So be patient if you make a Buildbot config change. Hopefully the configscanner will be fixed then ;) > > Jacques > > > Le 28/06/2017 à 17:32, Jacques Le Roux a écrit : >> Hi Taher, >> >> I saw your changes (wanted to do exactly the same so the resolving merge went perfectly well, rare thing :)) >> >> It was yesterday at 15:26:26 >> >> Revision: 1014588 >> Author: taher >> Date: mardi 27 juin 2017 15:26:26 >> Message: >> Replace all instances of gradle with ./gradlew --no-daemon for OFBiz builds >> ---- >> Modified : /infrastructure/buildbot/aegis/buildmaster/master1/projects/ofbiz.conf >> >> Then you committed >> >> Author: taher >> Date: Tue Jun 27 15:39:34 2017 >> New Revision: 1800073 >> >> URL:http://svn.apache.org/viewvc?rev=1800073&view=rev >> Log: >> Improved: refactored and improved the createPlugin task in gradle script >> (OFBIZ-9436) >> >> Without luck: https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/188 >> >> I discussed with the infra team (after some other issues due to Buildbot itself) and the tests issue is still a Tomcat instance running on Sylvanus >> (not Lares for instance) >> So we have still the same issue than >> INFRA-13496 <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-13496> >> >> and >> INFRA-13573 <https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-13573> >> >> They manually (so temporarily) stopped Tomcat on Sylvanus and my forced tests worked: >> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/189 >> >> Here is our recurring problem https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 >> This is supposed to install Tomcat but not run it, somehow it does not totally work >> Compare with https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 >> I have created https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-14463 for that >> >> Jacques >> >> >> Le 26/06/2017 à 12:39, Taher Alkhateeb a écrit : >>> I think the buildbot scripts might be faulty. I'll work on refactoring >>> it to at least start using the embedded gradle wrapper with >>> --no-daemon flag. We need to slowly isolate all causes >>> >>> On Mon, Jun 26, 2017 at 11:29 AM, Michael Brohl >>> <[hidden email]> wrote: >>>> Done in https://issues.apache.org/jira/browse/OFBIZ-9433 >>>> >>>> Am 26.06.17 um 10:27 schrieb Michael Brohl: >>>> >>>>> There seems to be a problem with shutting down previous instances: >>>>> >>>>> SEVERE: Failed to initialize end point associated with ProtocolHandler >>>>> ["http-nio-8080"] java.net.BindException: Address already in use >>>>> >>>>> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] >>>>> org.apache.catalina.LifecycleException: Failed to initialize component >>>>> [Connector[HTTP/1.1-8080]] >>>>> >>>>> This should be covered with the latest activities from Jacques regarding >>>>> shutdown, right? >>>>> >>>>> >>>>> There is also a warning about gradle (no error, just a warning): >>>>> >>>>> The Task.leftShift(Closure) method has been deprecated and is scheduled to >>>>> be removed in Gradle 5.0. Please use Task.doLast(Action) instead. >>>>> >>>>> I'll file a Jira for this. >>>>> >>>>> Regards, >>>>> >>>>> Michael Brohl >>>>> ecomify GmbH >>>>> www.ecomify.de >>>>> >>>>> >>>>> Am 26.06.17 um 10:19 schrieb [hidden email]: >>>>>> The Buildbot has detected a new failure on builder ofbiz-branch16 while >>>>>> building . Full details are available at: >>>>>> https://ci.apache.org/builders/ofbiz-branch16/builds/71 >>>>>> >>>>>> Buildbot URL: https://ci.apache.org/ >>>>>> >>>>>> Buildslave for this Build: silvanus_ubuntu >>>>>> >>>>>> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' >>>>>> triggered this build >>>>>> Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 >>>>>> Blamelist: mbrohl >>>>>> >>>>>> BUILD FAILED: failed shell_2 >>>>>> >>>>>> Sincerely, >>>>>> -The Buildbot >>>>>> >>>>>> >>>>>> >>>>> >>>> >> >> > > |
Re: buildbot failure in on ofbiz-branch16
|
Administrator
|
With INFRA-14464 a directory at https://ci.apache.org/projects/ofbiz/logs/ for the OFBiz framework only tests has been created
I have changed the Buildbot config to populate it. I test because I know Builbot is failing to load config changes and don't know if it's fixed or if I need to create an Infra request for that... Jacques Le 28/06/2017 à 18:15, Jacques Le Roux a écrit : > Orcus must have the same issue: > > https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/orcus.apache.org.yaml#L27 > > BTW, I have launched the tests for the framework only > > https://ci.apache.org/builders/ofbiz-trunk-framework/builds/240 > > But I did not yet put in place the necessary to see the results at ci.apache.org/projects/ofbiz/logs/ > > Jacques > > > Le 28/06/2017 à 17:49, Jacques Le Roux a écrit : >> BTW the "some other issues due to Buildbot itself" I had are still there. Buildbot does not autoreload on config change (not only OFBiz) >> >> [5:47 PM] Daniel Takamori (pono): configscanner might be busted again >> [5:47 PM] Daniel Takamori (pono): it's affecting all the projects it looks like >> >> So be patient if you make a Buildbot config change. Hopefully the configscanner will be fixed then ;) >> >> Jacques >> >> >> Le 28/06/2017 à 17:32, Jacques Le Roux a écrit : >>> Hi Taher, >>> >>> I saw your changes (wanted to do exactly the same so the resolving merge went perfectly well, rare thing :)) >>> >>> It was yesterday at 15:26:26 >>> >>> Revision: 1014588 >>> Author: taher >>> Date: mardi 27 juin 2017 15:26:26 >>> Message: >>> Replace all instances of gradle with ./gradlew --no-daemon for OFBiz builds >>> ---- >>> Modified : /infrastructure/buildbot/aegis/buildmaster/master1/projects/ofbiz.conf >>> >>> Then you committed >>> >>> Author: taher >>> Date: Tue Jun 27 15:39:34 2017 >>> New Revision: 1800073 >>> >>> URL:http://svn.apache.org/viewvc?rev=1800073&view=rev >>> Log: >>> Improved: refactored and improved the createPlugin task in gradle script >>> (OFBIZ-9436) >>> >>> Without luck: https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/188 >>> >>> I discussed with the infra team (after some other issues due to Buildbot itself) and the tests issue is still a Tomcat instance running on >>> Sylvanus (not Lares for instance) >>> So we have still the same issue than >>> INFRA-13496 <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-13496> >>> >>> and >>> INFRA-13573 <https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-13573> >>> >>> They manually (so temporarily) stopped Tomcat on Sylvanus and my forced tests worked: >>> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/189 >>> >>> Here is our recurring problem https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 >>> This is supposed to install Tomcat but not run it, somehow it does not totally work >>> Compare with https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 >>> I have created https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-14463 for that >>> >>> Jacques >>> >>> >>> Le 26/06/2017 à 12:39, Taher Alkhateeb a écrit : >>>> I think the buildbot scripts might be faulty. I'll work on refactoring >>>> it to at least start using the embedded gradle wrapper with >>>> --no-daemon flag. We need to slowly isolate all causes >>>> >>>> On Mon, Jun 26, 2017 at 11:29 AM, Michael Brohl >>>> <[hidden email]> wrote: >>>>> Done in https://issues.apache.org/jira/browse/OFBIZ-9433 >>>>> >>>>> Am 26.06.17 um 10:27 schrieb Michael Brohl: >>>>> >>>>>> There seems to be a problem with shutting down previous instances: >>>>>> >>>>>> SEVERE: Failed to initialize end point associated with ProtocolHandler >>>>>> ["http-nio-8080"] java.net.BindException: Address already in use >>>>>> >>>>>> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] >>>>>> org.apache.catalina.LifecycleException: Failed to initialize component >>>>>> [Connector[HTTP/1.1-8080]] >>>>>> >>>>>> This should be covered with the latest activities from Jacques regarding >>>>>> shutdown, right? >>>>>> >>>>>> >>>>>> There is also a warning about gradle (no error, just a warning): >>>>>> >>>>>> The Task.leftShift(Closure) method has been deprecated and is scheduled to >>>>>> be removed in Gradle 5.0. Please use Task.doLast(Action) instead. >>>>>> >>>>>> I'll file a Jira for this. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Michael Brohl >>>>>> ecomify GmbH >>>>>> www.ecomify.de >>>>>> >>>>>> >>>>>> Am 26.06.17 um 10:19 schrieb [hidden email]: >>>>>>> The Buildbot has detected a new failure on builder ofbiz-branch16 while >>>>>>> building . Full details are available at: >>>>>>> https://ci.apache.org/builders/ofbiz-branch16/builds/71 >>>>>>> >>>>>>> Buildbot URL: https://ci.apache.org/ >>>>>>> >>>>>>> Buildslave for this Build: silvanus_ubuntu >>>>>>> >>>>>>> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' >>>>>>> triggered this build >>>>>>> Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 >>>>>>> Blamelist: mbrohl >>>>>>> >>>>>>> BUILD FAILED: failed shell_2 >>>>>>> >>>>>>> Sincerely, >>>>>>> -The Buildbot >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>> >>> >> >> > > |
Re: buildbot failure in on ofbiz-branch16
|
Administrator
|
Works \o/ https://ci.apache.org/projects/ofbiz/logs/framework/
Jacques Le 29/06/2017 à 09:08, Jacques Le Roux a écrit : > With INFRA-14464 a directory at https://ci.apache.org/projects/ofbiz/logs/ for the OFBiz framework only tests has been created > > I have changed the Buildbot config to populate it. > > I test because I know Builbot is failing to load config changes and don't know if it's fixed or if I need to create an Infra request for that... > > Jacques > > > Le 28/06/2017 à 18:15, Jacques Le Roux a écrit : >> Orcus must have the same issue: >> >> https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/orcus.apache.org.yaml#L27 >> >> BTW, I have launched the tests for the framework only >> >> https://ci.apache.org/builders/ofbiz-trunk-framework/builds/240 >> >> But I did not yet put in place the necessary to see the results at ci.apache.org/projects/ofbiz/logs/ >> >> Jacques >> >> >> Le 28/06/2017 à 17:49, Jacques Le Roux a écrit : >>> BTW the "some other issues due to Buildbot itself" I had are still there. Buildbot does not autoreload on config change (not only OFBiz) >>> >>> [5:47 PM] Daniel Takamori (pono): configscanner might be busted again >>> [5:47 PM] Daniel Takamori (pono): it's affecting all the projects it looks like >>> >>> So be patient if you make a Buildbot config change. Hopefully the configscanner will be fixed then ;) >>> >>> Jacques >>> >>> >>> Le 28/06/2017 à 17:32, Jacques Le Roux a écrit : >>>> Hi Taher, >>>> >>>> I saw your changes (wanted to do exactly the same so the resolving merge went perfectly well, rare thing :)) >>>> >>>> It was yesterday at 15:26:26 >>>> >>>> Revision: 1014588 >>>> Author: taher >>>> Date: mardi 27 juin 2017 15:26:26 >>>> Message: >>>> Replace all instances of gradle with ./gradlew --no-daemon for OFBiz builds >>>> ---- >>>> Modified : /infrastructure/buildbot/aegis/buildmaster/master1/projects/ofbiz.conf >>>> >>>> Then you committed >>>> >>>> Author: taher >>>> Date: Tue Jun 27 15:39:34 2017 >>>> New Revision: 1800073 >>>> >>>> URL:http://svn.apache.org/viewvc?rev=1800073&view=rev >>>> Log: >>>> Improved: refactored and improved the createPlugin task in gradle script >>>> (OFBIZ-9436) >>>> >>>> Without luck: https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/188 >>>> >>>> I discussed with the infra team (after some other issues due to Buildbot itself) and the tests issue is still a Tomcat instance running on >>>> Sylvanus (not Lares for instance) >>>> So we have still the same issue than >>>> INFRA-13496 <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-13496> >>>> >>>> and >>>> INFRA-13573 <https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-13573> >>>> >>>> They manually (so temporarily) stopped Tomcat on Sylvanus and my forced tests worked: >>>> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/189 >>>> >>>> Here is our recurring problem https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 >>>> This is supposed to install Tomcat but not run it, somehow it does not totally work >>>> Compare with https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/silvanus.apache.org.yaml#L27 >>>> I have created https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-14463 for that >>>> >>>> Jacques >>>> >>>> >>>> Le 26/06/2017 à 12:39, Taher Alkhateeb a écrit : >>>>> I think the buildbot scripts might be faulty. I'll work on refactoring >>>>> it to at least start using the embedded gradle wrapper with >>>>> --no-daemon flag. We need to slowly isolate all causes >>>>> >>>>> On Mon, Jun 26, 2017 at 11:29 AM, Michael Brohl >>>>> <[hidden email]> wrote: >>>>>> Done in https://issues.apache.org/jira/browse/OFBIZ-9433 >>>>>> >>>>>> Am 26.06.17 um 10:27 schrieb Michael Brohl: >>>>>> >>>>>>> There seems to be a problem with shutting down previous instances: >>>>>>> >>>>>>> SEVERE: Failed to initialize end point associated with ProtocolHandler >>>>>>> ["http-nio-8080"] java.net.BindException: Address already in use >>>>>>> >>>>>>> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8080]] >>>>>>> org.apache.catalina.LifecycleException: Failed to initialize component >>>>>>> [Connector[HTTP/1.1-8080]] >>>>>>> >>>>>>> This should be covered with the latest activities from Jacques regarding >>>>>>> shutdown, right? >>>>>>> >>>>>>> >>>>>>> There is also a warning about gradle (no error, just a warning): >>>>>>> >>>>>>> The Task.leftShift(Closure) method has been deprecated and is scheduled to >>>>>>> be removed in Gradle 5.0. Please use Task.doLast(Action) instead. >>>>>>> >>>>>>> I'll file a Jira for this. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Michael Brohl >>>>>>> ecomify GmbH >>>>>>> www.ecomify.de >>>>>>> >>>>>>> >>>>>>> Am 26.06.17 um 10:19 schrieb [hidden email]: >>>>>>>> The Buildbot has detected a new failure on builder ofbiz-branch16 while >>>>>>>> building . Full details are available at: >>>>>>>> https://ci.apache.org/builders/ofbiz-branch16/builds/71 >>>>>>>> >>>>>>>> Buildbot URL: https://ci.apache.org/ >>>>>>>> >>>>>>>> Buildslave for this Build: silvanus_ubuntu >>>>>>>> >>>>>>>> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' >>>>>>>> triggered this build >>>>>>>> Build Source Stamp: [branch ofbiz/branches/release16.11] 1799858 >>>>>>>> Blamelist: mbrohl >>>>>>>> >>>>>>>> BUILD FAILED: failed shell_2 >>>>>>>> >>>>>>>> Sincerely, >>>>>>>> -The Buildbot >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>> >>>> >>> >>> >> >> > > |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |