Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

OK, I made another review, put a comment in INFRA-15394, reopened but did not 
revert Gavin's commit

To be discussed...

Jacques


Le 31/12/2017 à 23:50, Jacques Le Roux a écrit :

Thanks for your help

Jacques


Le 31/12/2017 à 15:06, Taher Alkhateeb a écrit :

So let's examine what was done here:
- You broke buildbot with a faulty commit in r1006626 that was later
fixed by gavin in INFRA-15394 in revision r1023028
- As a result, hundreds of messages spammed our mailing list from buildbot
- You insisted that nothing is wrong with the buildbot script
throughout this thread and when I asked you why do you believe that,
you theorized that it was related to network and infrastructure
without any justification to your reasoning.
- You wasted my time
- You wasted INFRA's time
- You wasted your time

Quite honestly, based on your lack of knowledge, I'm not reassured by
your statement "I'm confident". It seems you did not understand the
problem at all and just came up with theories while insisting nothing
is wrong with buildbot scripts. I hope you exercise more caution and
scrutiny in the future.

On Sun, Dec 31, 2017 at 10:23 AM, Jacques Le Roux
 wrote:

I think you were were right Taher, Gavin just removed a duplicate
declaration of ofbiz-trunk-framework-plugins, see INFRA-15394

Let's see, but I'm confident

Jacques


Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM,  wrote:

The Buildbot has detected a new failure on builder
ofbiz-trunk-framework-plugins while building . Full details are available
at:

https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
   -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

Thanks for your help

Jacques


Le 31/12/2017 à 15:06, Taher Alkhateeb a écrit :

So let's examine what was done here:
- You broke buildbot with a faulty commit in r1006626 that was later
fixed by gavin in INFRA-15394 in revision r1023028
- As a result, hundreds of messages spammed our mailing list from buildbot
- You insisted that nothing is wrong with the buildbot script
throughout this thread and when I asked you why do you believe that,
you theorized that it was related to network and infrastructure
without any justification to your reasoning.
- You wasted my time
- You wasted INFRA's time
- You wasted your time

Quite honestly, based on your lack of knowledge, I'm not reassured by
your statement "I'm confident". It seems you did not understand the
problem at all and just came up with theories while insisting nothing
is wrong with buildbot scripts. I hope you exercise more caution and
scrutiny in the future.

On Sun, Dec 31, 2017 at 10:23 AM, Jacques Le Roux
 wrote:

I think you were were right Taher, Gavin just removed a duplicate
declaration of ofbiz-trunk-framework-plugins, see INFRA-15394

Let's see, but I'm confident

Jacques


Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM,   wrote:

The Buildbot has detected a new failure on builder
ofbiz-trunk-framework-plugins while building . Full details are available
at:

https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
   -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Taher Alkhateeb]

So let's examine what was done here:
- You broke buildbot with a faulty commit in r1006626 that was later
fixed by gavin in INFRA-15394 in revision r1023028
- As a result, hundreds of messages spammed our mailing list from buildbot
- You insisted that nothing is wrong with the buildbot script
throughout this thread and when I asked you why do you believe that,
you theorized that it was related to network and infrastructure
without any justification to your reasoning.
- You wasted my time
- You wasted INFRA's time
- You wasted your time

Quite honestly, based on your lack of knowledge, I'm not reassured by
your statement "I'm confident". It seems you did not understand the
problem at all and just came up with theories while insisting nothing
is wrong with buildbot scripts. I hope you exercise more caution and
scrutiny in the future.

On Sun, Dec 31, 2017 at 10:23 AM, Jacques Le Roux
 wrote:
> I think you were were right Taher, Gavin just removed a duplicate
> declaration of ofbiz-trunk-framework-plugins, see INFRA-15394
>
> Let's see, but I'm confident
>
> Jacques
>
>
> Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :
>>
>> These error messages are becoming excessive and indicating a faulty
>> buildbot implementation. I would like to work on it. Is anyone
>> interested in helping me or has background information that might
>> help?
>>
>> On Wed, Dec 13, 2017 at 5:36 PM,   wrote:
>>>
>>> The Buildbot has detected a new failure on builder
>>> ofbiz-trunk-framework-plugins while building . Full details are available
>>> at:
>>>
>>> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877
>>>
>>> Buildbot URL: https://ci.apache.org/
>>>
>>> Buildslave for this Build: silvanus_ubuntu
>>>
>>> Build Reason: The AnyBranchScheduler scheduler named
>>> 'on-ofbiz-framework-commit' triggered this build
>>> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
>>> Blamelist: jleroux
>>>
>>> BUILD FAILED: failed shell_4
>>>
>>> Sincerely,
>>>   -The Buildbot
>>>
>>>
>>>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

I think you were were right Taher, Gavin just removed a duplicate declaration 
of ofbiz-trunk-framework-plugins, see INFRA-15394

Let's see, but I'm confident

Jacques


Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM,   wrote:

The Buildbot has detected a new failure on builder 
ofbiz-trunk-framework-plugins while building . Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

That's surely possible, I have used Jenkins in the past and it's the nice tool.

So we could indeed ask infra to take care of INFRA-15394, else we switch to 
Jenkins.

But I'll not do it, so please feel free :)

Jacques


Le 17/12/2017 à 21:12, Michael Brohl a écrit :

With so much hassle using buildbot, would it be possible to set up another 
build server like Jenkins?

We use it here at ecomify and have none of these issues with OFBiz.

Regards,

Michael


Am 17.12.17 um 21:06 schrieb Jacques Le Roux:

Ah also, normally Buildbot should only send email when the status change, from 
good to bad or reverse.

And it does not always. It's done randomly (see email today at 13:15, 18:04, 20:14) and completely independent of our script, we don't decide on 
this, Buildbot does.


I just wrote also that in INFRA-15394

Jacques


Le 17/12/2017 à 13:18, Jacques Le Roux a écrit :

Hi Taher,

I did not find something specific.

The message I try to convey is this is an external random condition, not 
related to Buildbot or our script but the network+servers context.

From time to time (more often since the date I put in the Infra Jira, but I can't see a relation with changes then in our script and it was 
happening before also) the tests fail and when I manually restart the same build they pass.


So for me it's not due to our script, which is only starting the tests, but to another conditions(/s?) on the network+servers context. Note that 
we use 3 test servers.


Note also that it happens that the "svn up"' phase fails. I once asked Gavin and he the told me that in such case I simply have to manually 
restart the tests...


That's when I learnt how to do it and that's what, among other things but 
mostly, I want to document

Thanks to care!

Jacques


Le 17/12/2017 à 12:37, Taher Alkhateeb a écrit :

Hi Jacques, I still don't understand how you determined that it is
_not_ a buildbot scripting issue? I need that information in order to
isolate the cause of these annoying error messages. I find it unlikely
to be a genuine bug in buildbot and more likely a bug in our scripts.
So perhaps you can share what you found so that I focus my efforts in
the right place?

On Wed, Dec 13, 2017 at 9:07 PM, Jacques Le Roux
 wrote:

Taher,

Look at
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins?numbuilds=150

 From time to time, when I find weird that a build fails on Buildbot but not
locally, I force a build on Buildbot manually (ie redo an existing commit)
and then it passes
Eg:
Dec 05 06:47

 1817154 success #797

forced: by IRC user  (privmsg): forces manual build after tests
errors Build successful
Dec 05 04:16    1817151 failure #796

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
this build Failed shell_4


Dec 08 19:40

 1817550 success #805

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
this build Build successful
Dec 08 10:14    1817479 success #804

forced: by IRC user  (privmsg): forces manual build after BuilBot
signaling a failure (OK locally) Build successful


Of course you can check there are no OFBiz commits between these forcings.
Remember we share SVN and Buildbot with other TLPs...

At contratrio, this one was a real issue I wanted to be sure about, see it
fails 2 times...
Dec 13 10:23

 1817994 failure #869

forced: by IRC user  (privmsg): forces manual build to check we
have a real error with testPerformFind Failed shell_4
Dec 13 09:23    1817989 failure #868

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
this build Failed shell_4


You can find the same on
https://ci.apache.org/builders/ofbiz-trunk-framework?numbuilds=150

BTW this was a good question and I'll add this info in the infra request.

I tend to forgot about how I do things. I'm really the kind of intuitive
people. But I can help myself when I need to help others :)

Jacques


Le 13/12/2017 à 17:12, Taher Alkhateeb a écrit :

How did you determine it's not the buildbot script?

On Wed, Dec 13, 2017 at 7:05 PM, Jacques Le Roux
 wrote:

I fear it's not part of our BuildBot config, so I asked help from infra.
Maybe this can help

https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394

Jacques



Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming 

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Michael Brohl]

With so much hassle using buildbot, would it be possible to set up 
another build server like Jenkins?


We use it here at ecomify and have none of these issues with OFBiz.

Regards,

Michael


Am 17.12.17 um 21:06 schrieb Jacques Le Roux:
Ah also, normally Buildbot should only send email when the status 
change, from good to bad or reverse.


And it does not always. It's done randomly (see email today at 13:15, 
18:04, 20:14) and completely independent of our script, we don't 
decide on this, Buildbot does.


I just wrote also that in INFRA-15394

Jacques


Le 17/12/2017 à 13:18, Jacques Le Roux a écrit :

Hi Taher,

I did not find something specific.

The message I try to convey is this is an external random condition, 
not related to Buildbot or our script but the network+servers context.


From time to time (more often since the date I put in the Infra Jira, 
but I can't see a relation with changes then in our script and it was 
happening before also) the tests fail and when I manually restart the 
same build they pass.


So for me it's not due to our script, which is only starting the 
tests, but to another conditions(/s?) on the network+servers context. 
Note that we use 3 test servers.


Note also that it happens that the "svn up"' phase fails. I once 
asked Gavin and he the told me that in such case I simply have to 
manually restart the tests...


That's when I learnt how to do it and that's what, among other things 
but mostly, I want to document


Thanks to care!

Jacques


Le 17/12/2017 à 12:37, Taher Alkhateeb a écrit :

Hi Jacques, I still don't understand how you determined that it is
_not_ a buildbot scripting issue? I need that information in order to
isolate the cause of these annoying error messages. I find it unlikely
to be a genuine bug in buildbot and more likely a bug in our scripts.
So perhaps you can share what you found so that I focus my efforts in
the right place?

On Wed, Dec 13, 2017 at 9:07 PM, Jacques Le Roux
 wrote:

Taher,

Look at
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins?numbuilds=150 



 From time to time, when I find weird that a build fails on 
Buildbot but not
locally, I force a build on Buildbot manually (ie redo an existing 
commit)

and then it passes
Eg:
Dec 05 06:47

 1817154 success #797
 

forced: by IRC user  (privmsg): forces manual build after 
tests

errors Build successful
Dec 05 04:16    1817151 failure #796
 

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' 
triggered

this build Failed shell_4


Dec 08 19:40

 1817550 success #805
 

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' 
triggered

this build Build successful
Dec 08 10:14    1817479 success #804
 

forced: by IRC user  (privmsg): forces manual build after 
BuilBot

signaling a failure (OK locally) Build successful


Of course you can check there are no OFBiz commits between these 
forcings.

Remember we share SVN and Buildbot with other TLPs...

At contratrio, this one was a real issue I wanted to be sure about, 
see it

fails 2 times...
Dec 13 10:23

 1817994 failure #869
 

forced: by IRC user  (privmsg): forces manual build to 
check we

have a real error with testPerformFind Failed shell_4
Dec 13 09:23    1817989 failure #868
 

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' 
triggered

this build Failed shell_4


You can find the same on
https://ci.apache.org/builders/ofbiz-trunk-framework?numbuilds=150

BTW this was a good question and I'll add this info in the infra 
request.


I tend to forgot about how I do things. I'm really the kind of 
intuitive

people. But I can help myself when I need to help others :)

Jacques


Le 13/12/2017 à 17:12, Taher Alkhateeb a écrit :

How did you determine it's not the buildbot script?

On Wed, Dec 13, 2017 at 7:05 PM, Jacques Le Roux
 wrote:
I fear it's not part of our BuildBot config, so I asked help from 
infra.

Maybe this can help

https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394 



Jacques



Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM, 

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

Ah also, normally Buildbot should only send email when the status change, from 
good to bad or reverse.

And it does not always. It's done randomly (see email today at 13:15, 18:04, 20:14) and completely independent of our script, we don't decide on this, 
Buildbot does.


I just wrote also that in INFRA-15394

Jacques


Le 17/12/2017 à 13:18, Jacques Le Roux a écrit :

Hi Taher,

I did not find something specific.

The message I try to convey is this is an external random condition, not 
related to Buildbot or our script but the network+servers context.

From time to time (more often since the date I put in the Infra Jira, but I can't see a relation with changes then in our script and it was 
happening before also) the tests fail and when I manually restart the same build they pass.


So for me it's not due to our script, which is only starting the tests, but to another conditions(/s?) on the network+servers context. Note that we 
use 3 test servers.


Note also that it happens that the "svn up"' phase fails. I once asked Gavin and he the told me that in such case I simply have to manually restart 
the tests...


That's when I learnt how to do it and that's what, among other things but 
mostly, I want to document

Thanks to care!

Jacques


Le 17/12/2017 à 12:37, Taher Alkhateeb a écrit :

Hi Jacques, I still don't understand how you determined that it is
_not_ a buildbot scripting issue? I need that information in order to
isolate the cause of these annoying error messages. I find it unlikely
to be a genuine bug in buildbot and more likely a bug in our scripts.
So perhaps you can share what you found so that I focus my efforts in
the right place?

On Wed, Dec 13, 2017 at 9:07 PM, Jacques Le Roux
 wrote:

Taher,

Look at
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins?numbuilds=150

 From time to time, when I find weird that a build fails on Buildbot but not
locally, I force a build on Buildbot manually (ie redo an existing commit)
and then it passes
Eg:
Dec 05 06:47

 1817154 success #797

forced: by IRC user  (privmsg): forces manual build after tests
errors Build successful
Dec 05 04:16    1817151 failure #796

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
this build Failed shell_4


Dec 08 19:40

 1817550 success #805

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
this build Build successful
Dec 08 10:14    1817479 success #804

forced: by IRC user  (privmsg): forces manual build after BuilBot
signaling a failure (OK locally) Build successful


Of course you can check there are no OFBiz commits between these forcings.
Remember we share SVN and Buildbot with other TLPs...

At contratrio, this one was a real issue I wanted to be sure about, see it
fails 2 times...
Dec 13 10:23

 1817994 failure #869

forced: by IRC user  (privmsg): forces manual build to check we
have a real error with testPerformFind Failed shell_4
Dec 13 09:23    1817989 failure #868

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
this build Failed shell_4


You can find the same on
https://ci.apache.org/builders/ofbiz-trunk-framework?numbuilds=150

BTW this was a good question and I'll add this info in the infra request.

I tend to forgot about how I do things. I'm really the kind of intuitive
people. But I can help myself when I need to help others :)

Jacques


Le 13/12/2017 à 17:12, Taher Alkhateeb a écrit :

How did you determine it's not the buildbot script?

On Wed, Dec 13, 2017 at 7:05 PM, Jacques Le Roux
 wrote:

I fear it's not part of our BuildBot config, so I asked help from infra.
Maybe this can help

https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394

Jacques



Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM,  wrote:

The Buildbot has detected a new failure on builder
ofbiz-trunk-framework-plugins while building . Full details are
available
at:

https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: 

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

Hi Taher,

I did not find something specific.

The message I try to convey is this is an external random condition, not 
related to Buildbot or our script but the network+servers context.

From time to time (more often since the date I put in the Infra Jira, but I can't see a relation with changes then in our script and it was happening 
before also) the tests fail and when I manually restart the same build they pass.


So for me it's not due to our script, which is only starting the tests, but to another conditions(/s?) on the network+servers context. Note that we 
use 3 test servers.


Note also that it happens that the "svn up"' phase fails. I once asked Gavin and he the told me that in such case I simply have to manually restart 
the tests...


That's when I learnt how to do it and that's what, among other things but 
mostly, I want to document

Thanks to care!

Jacques


Le 17/12/2017 à 12:37, Taher Alkhateeb a écrit :

Hi Jacques, I still don't understand how you determined that it is
_not_ a buildbot scripting issue? I need that information in order to
isolate the cause of these annoying error messages. I find it unlikely
to be a genuine bug in buildbot and more likely a bug in our scripts.
So perhaps you can share what you found so that I focus my efforts in
the right place?

On Wed, Dec 13, 2017 at 9:07 PM, Jacques Le Roux
 wrote:

Taher,

Look at
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins?numbuilds=150

 From time to time, when I find weird that a build fails on Buildbot but not
locally, I force a build on Buildbot manually (ie redo an existing commit)
and then it passes
Eg:
Dec 05 06:47

 1817154 success #797

forced: by IRC user  (privmsg): forces manual build after tests
errors Build successful
Dec 05 04:161817151 failure #796

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
this build Failed shell_4


Dec 08 19:40

 1817550 success #805

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
this build Build successful
Dec 08 10:141817479 success #804

forced: by IRC user  (privmsg): forces manual build after BuilBot
signaling a failure (OK locally) Build successful


Of course you can check there are no OFBiz commits between these forcings.
Remember we share SVN and Buildbot with other TLPs...

At contratrio, this one was a real issue I wanted to be sure about, see it
fails 2 times...
Dec 13 10:23

 1817994 failure #869

forced: by IRC user  (privmsg): forces manual build to check we
have a real error with testPerformFind Failed shell_4
Dec 13 09:231817989 failure #868

The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
this build Failed shell_4


You can find the same on
https://ci.apache.org/builders/ofbiz-trunk-framework?numbuilds=150

BTW this was a good question and I'll add this info in the infra request.

I tend to forgot about how I do things. I'm really the kind of intuitive
people. But I can help myself when I need to help others :)

Jacques


Le 13/12/2017 à 17:12, Taher Alkhateeb a écrit :

How did you determine it's not the buildbot script?

On Wed, Dec 13, 2017 at 7:05 PM, Jacques Le Roux
 wrote:

I fear it's not part of our BuildBot config, so I asked help from infra.
Maybe this can help

https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394

Jacques



Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM,   wrote:

The Buildbot has detected a new failure on builder
ofbiz-trunk-framework-plugins while building . Full details are
available
at:

https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
-The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Taher Alkhateeb]

Hi Jacques, I still don't understand how you determined that it is
_not_ a buildbot scripting issue? I need that information in order to
isolate the cause of these annoying error messages. I find it unlikely
to be a genuine bug in buildbot and more likely a bug in our scripts.
So perhaps you can share what you found so that I focus my efforts in
the right place?

On Wed, Dec 13, 2017 at 9:07 PM, Jacques Le Roux
 wrote:
> Taher,
>
> Look at
> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins?numbuilds=150
>
> From time to time, when I find weird that a build fails on Buildbot but not
> locally, I force a build on Buildbot manually (ie redo an existing commit)
> and then it passes
> Eg:
> Dec 05 06:47
>
> 1817154 success #797
> 
> forced: by IRC user  (privmsg): forces manual build after tests
> errors Build successful
> Dec 05 04:161817151 failure #796
> 
> The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
> this build Failed shell_4
>
>
> Dec 08 19:40
>
> 1817550 success #805
> 
> The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
> this build Build successful
> Dec 08 10:141817479 success #804
> 
> forced: by IRC user  (privmsg): forces manual build after BuilBot
> signaling a failure (OK locally) Build successful
>
>
> Of course you can check there are no OFBiz commits between these forcings.
> Remember we share SVN and Buildbot with other TLPs...
>
> At contratrio, this one was a real issue I wanted to be sure about, see it
> fails 2 times...
> Dec 13 10:23
>
> 1817994 failure #869
> 
> forced: by IRC user  (privmsg): forces manual build to check we
> have a real error with testPerformFind Failed shell_4
> Dec 13 09:231817989 failure #868
> 
> The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered
> this build Failed shell_4
>
>
> You can find the same on
> https://ci.apache.org/builders/ofbiz-trunk-framework?numbuilds=150
>
> BTW this was a good question and I'll add this info in the infra request.
>
> I tend to forgot about how I do things. I'm really the kind of intuitive
> people. But I can help myself when I need to help others :)
>
> Jacques
>
>
> Le 13/12/2017 à 17:12, Taher Alkhateeb a écrit :
>>
>> How did you determine it's not the buildbot script?
>>
>> On Wed, Dec 13, 2017 at 7:05 PM, Jacques Le Roux
>>  wrote:
>>>
>>> I fear it's not part of our BuildBot config, so I asked help from infra.
>>> Maybe this can help
>>>
>>> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394
>>>
>>> Jacques
>>>
>>>
>>>
>>> Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

 These error messages are becoming excessive and indicating a faulty
 buildbot implementation. I would like to work on it. Is anyone
 interested in helping me or has background information that might
 help?

 On Wed, Dec 13, 2017 at 5:36 PM,   wrote:
>
> The Buildbot has detected a new failure on builder
> ofbiz-trunk-framework-plugins while building . Full details are
> available
> at:
>
> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named
> 'on-ofbiz-framework-commit' triggered this build
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
> Blamelist: jleroux
>
> BUILD FAILED: failed shell_4
>
> Sincerely,
>-The Buildbot
>
>
>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

I think we miss is a bit of documentation on Buildbot. I'll do that soon...

Jacques


Le 13/12/2017 à 19:07, Jacques Le Roux a écrit :

Taher,

Look at 
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins?numbuilds=150

From time to time, when I find weird that a build fails on Buildbot but not locally, I force a build on Buildbot manually (ie redo an existing 
commit) and then it passes

Eg:
Dec 05 06:47

1817154 success #797  forced: by IRC user  (privmsg): 
forces manual build after tests errors Build successful
Dec 05 04:16 1817151 failure #796  The AnyBranchScheduler 
scheduler named 'on-ofbiz-framework-commit' triggered this build Failed shell_4



Dec 08 19:40

1817550 success #805  The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build Build successful
Dec 08 10:14 1817479 success #804  forced: by IRC user 
 (privmsg): forces manual build after BuilBot signaling a failure (OK locally) Build successful



Of course you can check there are no OFBiz commits between these forcings. 
Remember we share SVN and Buildbot with other TLPs...

At contratrio, this one was a real issue I wanted to be sure about, see it 
fails 2 times...
Dec 13 10:23

1817994 failure #869  forced: by IRC user  (privmsg): 
forces manual build to check we have a real error with testPerformFind Failed shell_4
Dec 13 09:23 1817989 failure #868  The AnyBranchScheduler 
scheduler named 'on-ofbiz-framework-commit' triggered this build Failed shell_4



You can find the same on 
https://ci.apache.org/builders/ofbiz-trunk-framework?numbuilds=150

BTW this was a good question and I'll add this info in the infra request.

I tend to forgot about how I do things. I'm really the kind of intuitive 
people. But I can help myself when I need to help others :)

Jacques

Le 13/12/2017 à 17:12, Taher Alkhateeb a écrit :

How did you determine it's not the buildbot script?

On Wed, Dec 13, 2017 at 7:05 PM, Jacques Le Roux
 wrote:

I fear it's not part of our BuildBot config, so I asked help from infra.
Maybe this can help

https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394

Jacques



Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM,  wrote:

The Buildbot has detected a new failure on builder
ofbiz-trunk-framework-plugins while building . Full details are available
at:

https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
   -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

Taher,

Look at 
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins?numbuilds=150

From time to time, when I find weird that a build fails on Buildbot but not locally, I force a build on Buildbot manually (ie redo an existing 
commit) and then it passes

Eg:
Dec 05 06:47

	1817154 	success 	#797  	forced: by IRC user  (privmsg): forces 
manual build after tests errors 	Build successful
Dec 05 04:16 	1817151 	failure 	#796  	The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build 	Failed shell_4



Dec 08 19:40

	1817550 	success 	#805  	The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build 	Build successful
Dec 08 10:14 	1817479 	success 	#804  	forced: by IRC user  
(privmsg): forces manual build after BuilBot signaling a failure (OK locally) 	Build successful



Of course you can check there are no OFBiz commits between these forcings. 
Remember we share SVN and Buildbot with other TLPs...

At contratrio, this one was a real issue I wanted to be sure about, see it 
fails 2 times...
Dec 13 10:23

	1817994 	failure 	#869  	forced: by IRC user  (privmsg): forces 
manual build to check we have a real error with testPerformFind 	Failed shell_4
Dec 13 09:23 	1817989 	failure 	#868  	The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build 	Failed shell_4



You can find the same on 
https://ci.apache.org/builders/ofbiz-trunk-framework?numbuilds=150

BTW this was a good question and I'll add this info in the infra request.

I tend to forgot about how I do things. I'm really the kind of intuitive 
people. But I can help myself when I need to help others :)

Jacques

Le 13/12/2017 à 17:12, Taher Alkhateeb a écrit :

How did you determine it's not the buildbot script?

On Wed, Dec 13, 2017 at 7:05 PM, Jacques Le Roux
 wrote:

I fear it's not part of our BuildBot config, so I asked help from infra.
Maybe this can help

https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394

Jacques



Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM,   wrote:

The Buildbot has detected a new failure on builder
ofbiz-trunk-framework-plugins while building . Full details are available
at:

https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
   -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Taher Alkhateeb]

How did you determine it's not the buildbot script?

On Wed, Dec 13, 2017 at 7:05 PM, Jacques Le Roux
 wrote:
> I fear it's not part of our BuildBot config, so I asked help from infra.
> Maybe this can help
>
> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394
>
> Jacques
>
>
>
> Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :
>>
>> These error messages are becoming excessive and indicating a faulty
>> buildbot implementation. I would like to work on it. Is anyone
>> interested in helping me or has background information that might
>> help?
>>
>> On Wed, Dec 13, 2017 at 5:36 PM,   wrote:
>>>
>>> The Buildbot has detected a new failure on builder
>>> ofbiz-trunk-framework-plugins while building . Full details are available
>>> at:
>>>
>>> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877
>>>
>>> Buildbot URL: https://ci.apache.org/
>>>
>>> Buildslave for this Build: silvanus_ubuntu
>>>
>>> Build Reason: The AnyBranchScheduler scheduler named
>>> 'on-ofbiz-framework-commit' triggered this build
>>> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
>>> Blamelist: jleroux
>>>
>>> BUILD FAILED: failed shell_4
>>>
>>> Sincerely,
>>>   -The Buildbot
>>>
>>>
>>>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

I fear it's not part of our BuildBot config, so I asked help from infra. Maybe 
this can help

https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394

Jacques


Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit :

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM,   wrote:

The Buildbot has detected a new failure on builder 
ofbiz-trunk-framework-plugins while building . Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Taher Alkhateeb]

These error messages are becoming excessive and indicating a faulty
buildbot implementation. I would like to work on it. Is anyone
interested in helping me or has background information that might
help?

On Wed, Dec 13, 2017 at 5:36 PM,   wrote:
> The Buildbot has detected a new failure on builder 
> ofbiz-trunk-framework-plugins while building . Full details are available at:
> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named 
> 'on-ofbiz-framework-commit' triggered this build
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020
> Blamelist: jleroux
>
> BUILD FAILED: failed shell_4
>
> Sincerely,
>  -The Buildbot
>
>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Deepak Dixit]

Thanks Jacques, this has been fixed,


Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Wed, Dec 13, 2017 at 5:18 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Thanks Deepak,
>
> It's indeed a very small things
>
> Jacques
>
>
>
> Le 13/12/2017 à 11:43, Deepak Dixit a écrit :
>
>> Hi Jacques,
>>
>> Reverted for now , its working locally, will check more and then commit
>> agin.
>>
>>
>> Thanks & Regards
>> --
>> Deepak Dixit
>> www.hotwaxsystems.com
>> www.hotwax.co
>>
>> On Wed, Dec 13, 2017 at 4:03 PM, Deepak Dixit <
>> deepak.di...@hotwaxsystems.com> wrote:
>>
>> Let me check Jacques.
>>>
>>> Thanks & Regards
>>> --
>>> Deepak Dixit
>>> www.hotwaxsystems.com
>>> www.hotwax.co
>>>
>>> On Wed, Dec 13, 2017 at 3:45 PM, Jacques Le Roux <
>>> jacques.le.r...@les7arts.com> wrote:
>>>
>>> Hi Deepak,

 This is a real problem, I reproduce (almost) the same locally, please
 fix
 or revert

 I'd prefer that other committers wait before committing anything else
 before this is resolved

 Thanks

 Jacques



 Le 13/12/2017 à 10:32, build...@apache.org a écrit :

 The Buildbot has detected a new failure on builder
> ofbiz-trunk-framework-plugins while building . Full details are
> available
> at:
>   https://ci.apache.org/builders/ofbiz-trunk-framework-plugin
> s/builds/868
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named
> 'on-ofbiz-framework-commit' triggered this build
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1817989
> Blamelist: deepak
>
> BUILD FAILED: failed shell_4
>
> Sincerely,
>-The Buildbot
>
>
>
>
>
>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

Thanks Deepak,

It's indeed a very small things

Jacques


Le 13/12/2017 à 11:43, Deepak Dixit a écrit :

Hi Jacques,

Reverted for now , its working locally, will check more and then commit
agin.


Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Wed, Dec 13, 2017 at 4:03 PM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:


Let me check Jacques.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Wed, Dec 13, 2017 at 3:45 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi Deepak,

This is a real problem, I reproduce (almost) the same locally, please fix
or revert

I'd prefer that other committers wait before committing anything else
before this is resolved

Thanks

Jacques



Le 13/12/2017 à 10:32, build...@apache.org a écrit :


The Buildbot has detected a new failure on builder
ofbiz-trunk-framework-plugins while building . Full details are available
at:
  https://ci.apache.org/builders/ofbiz-trunk-framework-plugin
s/builds/868

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1817989
Blamelist: deepak

BUILD FAILED: failed shell_4

Sincerely,
   -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Deepak Dixit]

Hi Jacques,

Reverted for now , its working locally, will check more and then commit
agin.


Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Wed, Dec 13, 2017 at 4:03 PM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:

> Let me check Jacques.
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
> www.hotwax.co
>
> On Wed, Dec 13, 2017 at 3:45 PM, Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
>> Hi Deepak,
>>
>> This is a real problem, I reproduce (almost) the same locally, please fix
>> or revert
>>
>> I'd prefer that other committers wait before committing anything else
>> before this is resolved
>>
>> Thanks
>>
>> Jacques
>>
>>
>>
>> Le 13/12/2017 à 10:32, build...@apache.org a écrit :
>>
>>> The Buildbot has detected a new failure on builder
>>> ofbiz-trunk-framework-plugins while building . Full details are available
>>> at:
>>>  https://ci.apache.org/builders/ofbiz-trunk-framework-plugin
>>> s/builds/868
>>>
>>> Buildbot URL: https://ci.apache.org/
>>>
>>> Buildslave for this Build: silvanus_ubuntu
>>>
>>> Build Reason: The AnyBranchScheduler scheduler named
>>> 'on-ofbiz-framework-commit' triggered this build
>>> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1817989
>>> Blamelist: deepak
>>>
>>> BUILD FAILED: failed shell_4
>>>
>>> Sincerely,
>>>   -The Buildbot
>>>
>>>
>>>
>>>
>>>
>>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Deepak Dixit]

Let me check Jacques.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Wed, Dec 13, 2017 at 3:45 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi Deepak,
>
> This is a real problem, I reproduce (almost) the same locally, please fix
> or revert
>
> I'd prefer that other committers wait before committing anything else
> before this is resolved
>
> Thanks
>
> Jacques
>
>
>
> Le 13/12/2017 à 10:32, build...@apache.org a écrit :
>
>> The Buildbot has detected a new failure on builder
>> ofbiz-trunk-framework-plugins while building . Full details are available
>> at:
>>  https://ci.apache.org/builders/ofbiz-trunk-framework-
>> plugins/builds/868
>>
>> Buildbot URL: https://ci.apache.org/
>>
>> Buildslave for this Build: silvanus_ubuntu
>>
>> Build Reason: The AnyBranchScheduler scheduler named
>> 'on-ofbiz-framework-commit' triggered this build
>> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1817989
>> Blamelist: deepak
>>
>> BUILD FAILED: failed shell_4
>>
>> Sincerely,
>>   -The Buildbot
>>
>>
>>
>>
>>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

Hi Deepak,

This is a real problem, I reproduce (almost) the same locally, please fix or 
revert

I'd prefer that other committers wait before committing anything else before 
this is resolved

Thanks

Jacques


Le 13/12/2017 à 10:32, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder 
ofbiz-trunk-framework-plugins while building . Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/868

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1817989
Blamelist: deepak

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Rishi Solanki]

Thanks Jacques!


Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co

On Tue, Dec 5, 2017 at 12:34 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi Rishi,
>
> It's OK here too, I relaunch Buildbot to (hopefully) clean that
>
> Jacques
>
>
> Le 05/12/2017 à 06:51, Rishi Solanki a écrit :
>
>> I ran the cleanAll loadAll testIntegration and got build success with no
>> issues.
>>
>> I think we are good.
>>
>> Best Regards,
>> --
>>
>> Rishi Solanki
>> Sr Manager, Enterprise Software Development
>> HotWax Systems Pvt. Ltd.
>> Direct: +91-9893287847
>> http://www.hotwaxsystems.com
>> www.hotwax.co
>>
>> On Tue, Dec 5, 2017 at 10:00 AM, Rishi Solanki 
>> wrote:
>>
>> I'm checking with this one.
>>>
>>> Thanks!
>>>
>>> Rishi Solanki
>>> Sr Manager, Enterprise Software Development
>>> HotWax Systems Pvt. Ltd.
>>> Direct: +91-9893287847
>>> http://www.hotwaxsystems.com
>>> www.hotwax.co
>>>
>>> On Tue, Dec 5, 2017 at 9:55 AM,  wrote:
>>>
>>> The Buildbot has detected a new failure on builder
 ofbiz-trunk-framework-plugins while building . Full details are
 available
 at:
  https://ci.apache.org/builders/ofbiz-trunk-framework-
 plugins/builds/796

 Buildbot URL: https://ci.apache.org/

 Buildslave for this Build: silvanus_ubuntu

 Build Reason: The AnyBranchScheduler scheduler named
 'on-ofbiz-framework-commit' triggered this build
 Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1817151
 Blamelist: rishi

 BUILD FAILED: failed shell_4

 Sincerely,
   -The Buildbot





>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

Hi Rishi,

It's OK here too, I relaunch Buildbot to (hopefully) clean that

Jacques

Le 05/12/2017 à 06:51, Rishi Solanki a écrit :

I ran the cleanAll loadAll testIntegration and got build success with no
issues.

I think we are good.

Best Regards,
--

Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co

On Tue, Dec 5, 2017 at 10:00 AM, Rishi Solanki 
wrote:


I'm checking with this one.

Thanks!

Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co

On Tue, Dec 5, 2017 at 9:55 AM,  wrote:


The Buildbot has detected a new failure on builder
ofbiz-trunk-framework-plugins while building . Full details are available
at:
 https://ci.apache.org/builders/ofbiz-trunk-framework-
plugins/builds/796

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1817151
Blamelist: rishi

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Rishi Solanki]

I ran the cleanAll loadAll testIntegration and got build success with no
issues.

I think we are good.

Best Regards,
--

Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co

On Tue, Dec 5, 2017 at 10:00 AM, Rishi Solanki 
wrote:

> I'm checking with this one.
>
> Thanks!
>
> Rishi Solanki
> Sr Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
> www.hotwax.co
>
> On Tue, Dec 5, 2017 at 9:55 AM,  wrote:
>
>> The Buildbot has detected a new failure on builder
>> ofbiz-trunk-framework-plugins while building . Full details are available
>> at:
>> https://ci.apache.org/builders/ofbiz-trunk-framework-
>> plugins/builds/796
>>
>> Buildbot URL: https://ci.apache.org/
>>
>> Buildslave for this Build: silvanus_ubuntu
>>
>> Build Reason: The AnyBranchScheduler scheduler named
>> 'on-ofbiz-framework-commit' triggered this build
>> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1817151
>> Blamelist: rishi
>>
>> BUILD FAILED: failed shell_4
>>
>> Sincerely,
>>  -The Buildbot
>>
>>
>>
>>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Rishi Solanki]

I'm checking with this one.

Thanks!

Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co

On Tue, Dec 5, 2017 at 9:55 AM,  wrote:

> The Buildbot has detected a new failure on builder
> ofbiz-trunk-framework-plugins while building . Full details are available
> at:
> https://ci.apache.org/builders/ofbiz-trunk-
> framework-plugins/builds/796
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named
> 'on-ofbiz-framework-commit' triggered this build
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1817151
> Blamelist: rishi
>
> BUILD FAILED: failed shell_4
>
> Sincerely,
>  -The Buildbot
>
>
>
>

Re: buildbot failure in on ofbiz-trunk-framework

[Rishi Solanki]

I have already fixed this in my next commit.

Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co

On Mon, Oct 30, 2017 at 11:34 AM,  wrote:

> The Buildbot has detected a new failure on builder ofbiz-trunk-framework
> while building . Full details are available at:
> https://ci.apache.org/builders/ofbiz-trunk-framework/builds/638
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: lares_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named
> 'on-ofbiz-framework-commit' triggered this build
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1813724
> Blamelist: rishi
>
> BUILD FAILED: failed shell_2
>
> Sincerely,
>  -The Buildbot
>
>
>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Taher Alkhateeb]

This is a classic "hidden dependency" because of some sort of "global
state". I'm glad we're facing this problem because it shows the value
of separating the project into two repos.

I checked the logs and I think it would take a while to see exactly
where that null reference is coming from. So I think the best thing to
do here is run the debugger for these tests and go line by line
unfortunately.

I faced this problem so many times, I change something in one place
and something breaks on the other end of the world! Heck maybe it's a
combo of a few commits that lead to this bug.

On Tue, Jul 4, 2017 at 7:31 PM, Jacques Le Roux
 wrote:
> I also tried to locally revert your commit and then all the tests (plugins
> included pass), it's a weird one for sure.
>
> Jacques
>
>
>
> Le 04/07/2017 à 18:05, Michael Brohl a écrit :
>>
>> I can reproduce it when I run all integration tests with the plugins.
>>
>> It's strange that it comes up now, the last commits to plugins are a few
>> days ago...
>>
>>
>> Am 04.07.17 um 17:59 schrieb Jacques Le Roux:
>>>
>>> You are right
>>> https://ci.apache.org/builders/ofbiz-trunk-framework/builds/248
>>>
>>> It's still an issue, a weird one I'd say. Because only one of the tests
>>> which fail is in lucene plugin, the 3 others are in accounting and order. So
>>> we need to investigate that, I hope it's a data location issue...
>>>
>>> Jacques
>>>
>>>
>>> Le 04/07/2017 à 17:20, Michael Brohl a écrit :

 Hi Jacques,

 I cannot reproduce this with a clean framework (no plugins). The last
 change was only in the framework/content manager.

 Regards,

 Michael


 Am 04.07.17 um 16:57 schrieb Jacques Le Roux:
>
> Hi Michael,
>
> I reproduce locally so it's not a Buildbot issue, could you please
> check on you end?
>
> Thanks
>
> Jacques
>
>
> Le 04/07/2017 à 15:33, build...@apache.org a écrit :
>>
>> The Buildbot has detected a new failure on builder
>> ofbiz-trunk-framework-plugins while building . Full details are available
>> at:
>>
>> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/202
>>
>> Buildbot URL: https://ci.apache.org/
>>
>> Buildslave for this Build: lares_ubuntu
>>
>> Build Reason: The AnyBranchScheduler scheduler named
>> 'on-ofbiz-framework-commit' triggered this build
>> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1800780
>> Blamelist: mbrohl
>>
>> BUILD FAILED: failed shell_4
>>
>> Sincerely,
>>   -The Buildbot
>>
>>
>>
>>
>


>>>
>>
>>
>

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

I also tried to locally revert your commit and then all the tests (plugins 
included pass), it's a weird one for sure.

Jacques


Le 04/07/2017 à 18:05, Michael Brohl a écrit :

I can reproduce it when I run all integration tests with the plugins.

It's strange that it comes up now, the last commits to plugins are a few days 
ago...


Am 04.07.17 um 17:59 schrieb Jacques Le Roux:

You are right https://ci.apache.org/builders/ofbiz-trunk-framework/builds/248

It's still an issue, a weird one I'd say. Because only one of the tests which fail is in lucene plugin, the 3 others are in accounting and order. 
So we need to investigate that, I hope it's a data location issue...


Jacques


Le 04/07/2017 à 17:20, Michael Brohl a écrit :

Hi Jacques,

I cannot reproduce this with a clean framework (no plugins). The last change 
was only in the framework/content manager.

Regards,

Michael


Am 04.07.17 um 16:57 schrieb Jacques Le Roux:

Hi Michael,

I reproduce locally so it's not a Buildbot issue, could you please check on you 
end?

Thanks

Jacques


Le 04/07/2017 à 15:33, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder 
ofbiz-trunk-framework-plugins while building . Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/202

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1800780
Blamelist: mbrohl

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Michael Brohl]

Locally, I get only 3 failures in framework, lucene tests are fine:

invoicetests 
invoice-per-shipment-tests.testInvoicePerShipmentSetOrderFalse 
FailureError running the simple-method: 
java.lang.reflect.InvocationTargetException (null) Method = 
testInvoicePerShipmentSetOrderFalse, File = 
file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/applications/accounting/minilang/test/InvoicePerShipmentTests.xml, 
Element = , Line 334null


junit.framework.AssertionFailedError: Error running the simple-method: 
java.lang.reflect.InvocationTargetException (null) Method = 
testInvoicePerShipmentSetOrderFalse, File = 
file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/applications/accountiing/minilang/test/InvoicePerShipmentTests.xml, 
Element = , Line 334null

at org.apache.ofbiz.testtools.SimpleMethodTest.run(SimpleMethodTest.java:91)
at 
org.apache.ofbiz.testtools.TestRunContaineer.start(TestRunContainer.java:152)
at 
org.apache.ofbiz.base.container.ContainerLoader.startLoadedContainers(ContainerLoader.java:148)
at 
org.apache.ofbiz.base.container.ContainerLoader.load(ContainerLoader.java:73)
at 
org.apache.ofbiz.base.start..StartupControlPanel.loadStartupLoaders(StartupControlPanel.java:222)
at 
org.apache.ofbiz.base.start.StartupControlPanel.start(StartupControlPanel.java:72)

at org.apache.ofbiz.base.staart.Start.main(Start.java:84)
0.259
invoicetests 
invoice-per-shipment-tests.testInvoicePerShipmentSetOrderTrue Failure
Error running the simple-method: 
java.lang.reflect.InvocationTargetException (null) Method = 
testInvoicePerShipmentSetOrderTrue, File = 
file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/applications/accounting/minilang/test/InvoicePerShipmentTests.xml, 
Element = , Line 459null


junit.framework.AssertionFailedError: Error running the simple-method: 
java.lang.reflect.InvocationTargetException (null) Method = 
testInvoicePerShipmentSetOrderTrue, File = 
file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/applications/accountiing/minilang/test/InvoicePerShipmentTests.xml, 
Element = , Line 459null

at org.apache.ofbiz.testtools.SimpleMethodTest.run(SimpleMethodTest.java:91)
at 
org.apache.ofbiz.testtools.TestRunContainer.start(TestRunContainer.java:152)
at 
org.apache.ofbiz.base.container.ContainerLoader.startLoadedContainers(ContainerLoader.java:148)
at 
org.apache.ofbiz.base.container.ContainerLoader.load(ContainerLoader.java:73)
at 
org.apache.ofbiz.base.start..StartupControlPanel.loadStartupLoaders(StartupControlPanel.java:222)
at 
org.apache.ofbiz.base.start.StartupControlPanel.start(StartupControlPanel.java:72)

at org.apache.ofbiz.base.staart.Start.main(Start.java:84)
0.337
shoppingcarttestsconfigurableServiceOrder-testFailure Error 
running the simple-method: java.lang.reflect.InvocationTargetException 
(null) Method = testCreateOrderConfigurableServiceProduct, File = 
file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/applications/order/minilang/test/ShoppingCartTests.xml, 
Element = , Line 651null


junit.framework.AssertionFailedError: Error running the simple-method: 
java.lang.reflect.InvocationTargetException (null) Method = 
testCreateOrderConfigurableServiceProduct, File = 
file:/Users/mbrohl/Projects/apache-ofbiz/trunk/ofbiz/applicationss/order/minilang/test/ShoppingCartTests.xml, 
Element = , Line 651null

at org.apache.ofbiz.testtools.SimpleMethodTest.run(SimpleMethodTest.java:91)
at 
org.apache.ofbiz.testtools.TestRunContainer.start(TestRunContainer.java:152)
at 
org.apache.ofbiz.base.container.ContainerLoader.startLoadedContainers(ContainerLoader.java:148)
at 
org.apache.ofbiz.base.container.ContainerLoader.load(ContainerLoader.java:73)
at 
org.apache.ofbiz.base.start..StartupControlPanel.loadStartupLoaders(StartupControlPanel.java:222)
at 
org.apache.ofbiz.base.start.StartupControlPanel.start(StartupControlPanel.java:72)

at org.apache.ofbiz.base.staart.Start.main(Start.java:84)
0.145

Regards,

Michael

Am 04.07.17 um 18:05 schrieb Michael Brohl:

I can reproduce it when I run all integration tests with the plugins.

It's strange that it comes up now, the last commits to plugins are a 
few days ago...



Am 04.07.17 um 17:59 schrieb Jacques Le Roux:
You are right 
https://ci.apache.org/builders/ofbiz-trunk-framework/builds/248


It's still an issue, a weird one I'd say. Because only one of the 
tests which fail is in lucene plugin, the 3 others are in accounting 
and order. So we need to investigate that, I hope it's a data 
location issue...


Jacques


Le 04/07/2017 à 17:20, Michael Brohl a écrit :

Hi Jacques,

I cannot reproduce this with a clean framework (no plugins). The 
last change was only in the framework/content manager.


Regards,

Michael


Am 04.07.17 um 16:57 schrieb Jacques Le Roux:

Hi Michael,

I reproduce locally so it's not a Buildbot issue, could you please 
check on you end?


Thanks

Jacques


Le 04/07/2017 à 15:33, build...@apache.org a écrit :
The Buildbot has detected a new failure on builder 

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Michael Brohl]

I can reproduce it when I run all integration tests with the plugins.

It's strange that it comes up now, the last commits to plugins are a few 
days ago...



Am 04.07.17 um 17:59 schrieb Jacques Le Roux:
You are right 
https://ci.apache.org/builders/ofbiz-trunk-framework/builds/248


It's still an issue, a weird one I'd say. Because only one of the 
tests which fail is in lucene plugin, the 3 others are in accounting 
and order. So we need to investigate that, I hope it's a data location 
issue...


Jacques


Le 04/07/2017 à 17:20, Michael Brohl a écrit :

Hi Jacques,

I cannot reproduce this with a clean framework (no plugins). The last 
change was only in the framework/content manager.


Regards,

Michael


Am 04.07.17 um 16:57 schrieb Jacques Le Roux:

Hi Michael,

I reproduce locally so it's not a Buildbot issue, could you please 
check on you end?


Thanks

Jacques


Le 04/07/2017 à 15:33, build...@apache.org a écrit :
The Buildbot has detected a new failure on builder 
ofbiz-trunk-framework-plugins while building . Full details are 
available at:
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/202 



Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build

Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1800780
Blamelist: mbrohl

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot
















smime.p7s
Description: S/MIME Cryptographic Signature

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

You are right https://ci.apache.org/builders/ofbiz-trunk-framework/builds/248

It's still an issue, a weird one I'd say. Because only one of the tests which fail is in lucene plugin, the 3 others are in accounting and order. So 
we need to investigate that, I hope it's a data location issue...


Jacques


Le 04/07/2017 à 17:20, Michael Brohl a écrit :

Hi Jacques,

I cannot reproduce this with a clean framework (no plugins). The last change 
was only in the framework/content manager.

Regards,

Michael


Am 04.07.17 um 16:57 schrieb Jacques Le Roux:

Hi Michael,

I reproduce locally so it's not a Buildbot issue, could you please check on you 
end?

Thanks

Jacques


Le 04/07/2017 à 15:33, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder 
ofbiz-trunk-framework-plugins while building . Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/202

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1800780
Blamelist: mbrohl

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Michael Brohl]

Hi Jacques,

I cannot reproduce this with a clean framework (no plugins). The last 
change was only in the framework/content manager.


Regards,

Michael


Am 04.07.17 um 16:57 schrieb Jacques Le Roux:

Hi Michael,

I reproduce locally so it's not a Buildbot issue, could you please 
check on you end?


Thanks

Jacques


Le 04/07/2017 à 15:33, build...@apache.org a écrit :
The Buildbot has detected a new failure on builder 
ofbiz-trunk-framework-plugins while building . Full details are 
available at:

https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/202

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build

Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1800780
Blamelist: mbrohl

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot











smime.p7s
Description: S/MIME Cryptographic Signature

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Jacques Le Roux]

Hi Michael,

I reproduce locally so it's not a Buildbot issue, could you please check on you 
end?

Thanks

Jacques


Le 04/07/2017 à 15:33, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder 
ofbiz-trunk-framework-plugins while building . Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/202

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1800780
Blamelist: mbrohl

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework-plugins

[Taher Alkhateeb]

I suspect we did something wrong in the buildbot scripts lately and that is
why we're having these weird consistent crashes. We need to review these
files.

On Sat, Jun 24, 2017 at 11:30 PM,  wrote:

> The Buildbot has detected a new failure on builder
> ofbiz-trunk-framework-plugins while building . Full details are available
> at:
> https://ci.apache.org/builders/ofbiz-trunk-
> framework-plugins/builds/184
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named
> 'on-ofbiz-framework-commit' triggered this build
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1799779
> Blamelist: taher
>
> BUILD FAILED: failed shell_4
>
> Sincerely,
>  -The Buildbot
>
>
>
>

Re: buildbot failure in on ofbiz-trunk-framework

[Taher Alkhateeb]

I don't want to sound like a broken record, but at a minimum I would
suggest to apply "svn up" followed by "./gradlew cleanAll loadDefault
testIntegration" before committing. Depending on buildbot to catch errors
is not an ideal solution because it slows down other committers who are
trying to commit code.

I am now facing this issue multiple times. You commit broken code and I
have to wait for you to fix it before I commit my code because I'm not sure
what is the source of error.

On Sat, Jun 10, 2017 at 10:44 PM,  wrote:

> The Buildbot has detected a new failure on builder ofbiz-trunk-framework
> while building . Full details are available at:
> https://ci.apache.org/builders/ofbiz-trunk-framework/builds/186
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: orcus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named
> 'on-ofbiz-framework-commit' triggered this build
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1798335
> Blamelist: jleroux
>
> BUILD FAILED: failed shell
>
> Sincerely,
>  -The Buildbot
>
>
>
>

Re: buildbot failure in on ofbiz-trunk-framework

[Jacques Le Roux]

Hi,

On every branches (lately R14 and trunk) , we randomly get false tests failures 
and errors always and only related to SOAP and XML-RPC

We can neglect them but this is annoying because we have to check the status uselessly. I have not yet for sure identified the reason even if I still 
suspect a 8080 port random pre-emption


Before bothering Infra, I'll try to have another look when I'll get a chance, 
help appreciated...

Jacques


Le 12/03/2017 à 13:45, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbiz-trunk-framework while 
building . Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk-framework/builds/15

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 
'on-ofbiz-framework-commit' triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1786568
Blamelist: jleroux

BUILD FAILED: failed shell_2

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk-framework

[Jacques Le Roux]

Le 03/03/2017 à 09:01, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbiz-trunk-framework while 
building . Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk-framework/builds/5

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: forced: by IRC user  (privmsg): forces manual build. I 
need to check svn update in Buildbot
Build Source Stamp: HEAD
Blamelist:

BUILD FAILED: failed shell_2

Sincerely,
  -The Buildbot





This is only due to pending INFRA-13573

Jacques

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

I created https://issues.apache.org/jira/browse/OFBIZ-9196 for that ("Regression: 
the testIntegration Gradle taks shoud not use/block the ports")

Jacques


Le 30/01/2017 à 11:15, Jacques Le Roux a écrit :

Thanks Scott,

Inline...


Le 30/01/2017 à 10:03, Scott Gray a écrit :

Try and be patient Jacques, I'm also having trouble understanding what you
are saying.

Here's what I've been able to understand so far:
- Pre-gradle OFBiz tests run fine on buildbot
- Gradle OFBiz fails on buildbot with a complaint that the default ports
are in use
- The test framework in OFBiz has never supported port offset
- Jacques thinks that maybe using a port offset for tests will fix the
problem but he's unsure why

Is that mostly correct Jacques?
Almost, It's not that I'm unsure, actually I tried this weekend to use portoffset in Gradle versions. From the documentation, it's theoretically 
possible but does not work OOTB (I agree it's a complicated matter)
So I  committed r1780660  and locally hardcoded 8080 port changes to 8081 in XML files serviceengine.xml, services_test.xml and axis2.xml w/o 
success when running tests.


Then I thought more at the problem and I see now 2 options:
1) Infra does not need to have always Tomcat using the 8080 port on Buildbot hosts, problem resolved. I asked a question in the related infra: 
https://issues.apache.org/jira/browse/INFRA-13402
2) Infra needs to have always Tomcat using the 8080 port on Buildbot hosts. Then, it's maybe possible, as Taher suggested, to get back to the 
previous behaviour were tests were not using/blocking the 8080 port. Taher suggested to have a look into config.xml...


I first wait an answer to 1), then I'll consider 2)

Note though that it would be nice to not use/block ports during tests, as it was before Gradle. Then you can use another OFBiz instance while 
running tests, and vice-versa. I don't know if it's me, but it seems that I'm rehearsing the same things :/



Is there a possibility that buildbot isn't correctly shutting down OFBiz
from the previous test run and the ports are being left open? Just a
guess, I don't know much about buildbot but that's the usual cause of the
default ports being unavailable in my experience.


Infra said in INFRA-13402 that it's due to Tomcat being puppetized, please read 
INFRA-13402

Jacques


Regards
Scott

On 30 January 2017 at 21:08, Jacques Le Roux 
wrote:


Come on Taher,

As I said below (my last message) BuildBot is only revealing a symptom.

I already explained in this thread http://markmail.org/message/h4
i7cn4i2btugdwn:

>

I suggest that you test by yourself to be convinced.

I also wrote in this same email <>

I did, now waiting their answer... and focusing on other matters in the
meantime...

Jacques


Le 29/01/2017 à 14:27, Taher Alkhateeb a écrit :


What does gradle have to do with blocking these ports? This is stuff
related to Tomcat. There is nothing in both ant and gradle that has
anything to do with these ports afaik.

On Jan 29, 2017 4:16 PM, "Jacques Le Roux" 
wrote:

Taher,

I did not say that "ant run-tests" can use portoffset. Indeed it's not,
and I was overzealous when, long ago and yesterday in r1780660, I changed
the Java code of tests for that (related with portoffset). Because I did
not change how the tests are running in pre Gradle versions. Actually I
was
then unsure and preferred to cover all cases. So, I repeat: we never
use/block ports (at least 8080 and I guess 8443) when running tests in
pre
Gradle versions.

For instance if you look for

f_ofb_15.addStep(Compile(command=["ant" , "load-demo"],
and
f_ofb_15.addStep(Compile(command=["ant" , "run-tests"],

in https://svn.apache.org/repos/infra/infrastructure/buildbot/a
egis/buildmaster/master1/projects/ofbiz.conf (for committers only)

You will see that we don't use portoffset in Buildbot and it works well:

https://ci.apache.org/projects/ofbiz/logs/15.12/html/ (ran yesterday)

But since Gradle migration something has surely changed. As Buildbot
shows
(it's a side effect here, but it's also Buildbot role to track
regressions), the ports are used(?)/blocked when running tests in post
Gradle versions.
I believe the best for us is to remove that, if it's possible. I'll have
a
look in Config.java. I'll not feel offended if someone beats me on it...

Thanks

Jacques


Le 29/01/2017 à 11:12, Taher Alkhateeb a écrit :

Okay, thank you for the efforts Jacques.

The only thing that I suspect is related might be in Config.java where
the
portoffset is evaluated. I don't think I've changed the logic, and so I
suspect that it is not related to Gradle. If the tests do not run on a
portoffset, then I suspect perhaps they don't do the same on ant either.

On Sun, Jan 29, 2017 at 12:57 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

Hi Taher,


Prior to Gradle migration we were not using the 8080 port during tests.
For instance we could have an 

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Thanks Scott,

Inline...


Le 30/01/2017 à 10:03, Scott Gray a écrit :

Try and be patient Jacques, I'm also having trouble understanding what you
are saying.

Here's what I've been able to understand so far:
- Pre-gradle OFBiz tests run fine on buildbot
- Gradle OFBiz fails on buildbot with a complaint that the default ports
are in use
- The test framework in OFBiz has never supported port offset
- Jacques thinks that maybe using a port offset for tests will fix the
problem but he's unsure why

Is that mostly correct Jacques?
Almost, It's not that I'm unsure, actually I tried this weekend to use portoffset in Gradle versions. From the documentation, it's theoretically 
possible but does not work OOTB (I agree it's a complicated matter)
So I  committed r1780660  and locally hardcoded 8080 port changes to 8081 in XML files serviceengine.xml, services_test.xml and axis2.xml w/o success 
when running tests.


Then I thought more at the problem and I see now 2 options:
1) Infra does not need to have always Tomcat using the 8080 port on Buildbot hosts, problem resolved. I asked a question in the related infra: 
https://issues.apache.org/jira/browse/INFRA-13402
2) Infra needs to have always Tomcat using the 8080 port on Buildbot hosts. Then, it's maybe possible, as Taher suggested, to get back to the previous 
behaviour were tests were not using/blocking the 8080 port. Taher suggested to have a look into config.xml...


I first wait an answer to 1), then I'll consider 2)

Note though that it would be nice to not use/block ports during tests, as it was before Gradle. Then you can use another OFBiz instance while running 
tests, and vice-versa. I don't know if it's me, but it seems that I'm rehearsing the same things :/



Is there a possibility that buildbot isn't correctly shutting down OFBiz
from the previous test run and the ports are being left open?  Just a
guess, I don't know much about buildbot but that's the usual cause of the
default ports being unavailable in my experience.


Infra said in INFRA-13402 that it's due to Tomcat being puppetized, please read 
INFRA-13402

Jacques


Regards
Scott

On 30 January 2017 at 21:08, Jacques Le Roux 
wrote:


Come on Taher,

As I said below (my last message) BuildBot is only revealing a symptom.

I already explained in this thread http://markmail.org/message/h4
i7cn4i2btugdwn:

>

I suggest that you test by yourself to be convinced.

I also wrote in this same email <>

I did, now waiting their answer... and focusing on other matters in the
meantime...

Jacques


Le 29/01/2017 à 14:27, Taher Alkhateeb a écrit :


What does gradle have to do with blocking these ports? This is stuff
related to Tomcat. There is nothing in both ant and gradle that has
anything to do with these ports afaik.

On Jan 29, 2017 4:16 PM, "Jacques Le Roux" 
wrote:

Taher,

I did not say that "ant run-tests" can use portoffset. Indeed it's not,
and I was overzealous when, long ago and yesterday in r1780660, I changed
the Java code of tests for that (related with portoffset). Because I did
not change how the tests are running in pre Gradle versions. Actually I
was
then unsure and preferred to cover all cases. So, I repeat: we never
use/block ports (at least 8080 and I guess 8443) when running tests in
pre
Gradle versions.

For instance if you look for

f_ofb_15.addStep(Compile(command=["ant" , "load-demo"],
and
f_ofb_15.addStep(Compile(command=["ant" , "run-tests"],

in https://svn.apache.org/repos/infra/infrastructure/buildbot/a
egis/buildmaster/master1/projects/ofbiz.conf (for committers only)

You will see that we don't use portoffset in Buildbot and it works well:

https://ci.apache.org/projects/ofbiz/logs/15.12/html/ (ran yesterday)

But since Gradle migration something has surely changed. As Buildbot
shows
(it's a side effect here, but it's also Buildbot role to track
regressions), the ports are used(?)/blocked when running tests in post
Gradle versions.
I believe the best for us is to remove that, if it's possible. I'll have
a
look in Config.java. I'll not feel offended if someone beats me on it...

Thanks

Jacques


Le 29/01/2017 à 11:12, Taher Alkhateeb a écrit :

Okay, thank you for the efforts Jacques.

The only thing that I suspect is related might be in Config.java where
the
portoffset is evaluated. I don't think I've changed the logic, and so I
suspect that it is not related to Gradle. If the tests do not run on a
portoffset, then I suspect perhaps they don't do the same on ant either.

On Sun, Jan 29, 2017 at 12:57 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

Hi Taher,


Prior to Gradle migration we were not using the 8080 port during tests.
For instance we could have an OFBiz instance running, playing with its
UI
and then run tests on another instance or vice-versa.

This is no longer possible because now the port 8080 (and others) are
kept
open while running tests. So far it 

Re: buildbot failure in on ofbiz-trunk

[Scott Gray]

Try and be patient Jacques, I'm also having trouble understanding what you
are saying.

Here's what I've been able to understand so far:
- Pre-gradle OFBiz tests run fine on buildbot
- Gradle OFBiz fails on buildbot with a complaint that the default ports
are in use
- The test framework in OFBiz has never supported port offset
- Jacques thinks that maybe using a port offset for tests will fix the
problem but he's unsure why

Is that mostly correct Jacques?
Is there a possibility that buildbot isn't correctly shutting down OFBiz
from the previous test run and the ports are being left open?  Just a
guess, I don't know much about buildbot but that's the usual cause of the
default ports being unavailable in my experience.

Regards
Scott

On 30 January 2017 at 21:08, Jacques Le Roux 
wrote:

> Come on Taher,
>
> As I said below (my last message) BuildBot is only revealing a symptom.
>
> I already explained in this thread http://markmail.org/message/h4
> i7cn4i2btugdwn:
>
> < For instance we could have an OFBiz instance running, playing with its UI
> and then run tests on another instance or vice-versa.
> This is no longer possible because now the port 8080 (and others) are kept
> open while running tests. So far it was only a "small" annoyance, but it's
> now blocking BuildBot because infra puppetized the BuildBot slaves
> https://s.apache.org/pWQD.>>
>
> I suggest that you test by yourself to be convinced.
>
> I also wrote in this same email < infra why Tomcat is always running on these hosts...>>
>
> I did, now waiting their answer... and focusing on other matters in the
> meantime...
>
> Jacques
>
>
> Le 29/01/2017 à 14:27, Taher Alkhateeb a écrit :
>
>> What does gradle have to do with blocking these ports? This is stuff
>> related to Tomcat. There is nothing in both ant and gradle that has
>> anything to do with these ports afaik.
>>
>> On Jan 29, 2017 4:16 PM, "Jacques Le Roux" 
>> wrote:
>>
>> Taher,
>>>
>>> I did not say that "ant run-tests" can use portoffset. Indeed it's not,
>>> and I was overzealous when, long ago and yesterday in r1780660, I changed
>>> the Java code of tests for that (related with portoffset). Because I did
>>> not change how the tests are running in pre Gradle versions. Actually I
>>> was
>>> then unsure and preferred to cover all cases. So, I repeat: we never
>>> use/block ports (at least 8080 and I guess 8443) when running tests in
>>> pre
>>> Gradle versions.
>>>
>>> For instance if you look for
>>>
>>> f_ofb_15.addStep(Compile(command=["ant" , "load-demo"],
>>> and
>>> f_ofb_15.addStep(Compile(command=["ant" , "run-tests"],
>>>
>>> in https://svn.apache.org/repos/infra/infrastructure/buildbot/a
>>> egis/buildmaster/master1/projects/ofbiz.conf (for committers only)
>>>
>>> You will see that we don't use portoffset in Buildbot and it works well:
>>>
>>> https://ci.apache.org/projects/ofbiz/logs/15.12/html/ (ran yesterday)
>>>
>>> But since Gradle migration something has surely changed. As Buildbot
>>> shows
>>> (it's a side effect here, but it's also Buildbot role to track
>>> regressions), the ports are used(?)/blocked when running tests in post
>>> Gradle versions.
>>> I believe the best for us is to remove that, if it's possible. I'll have
>>> a
>>> look in Config.java. I'll not feel offended if someone beats me on it...
>>>
>>> Thanks
>>>
>>> Jacques
>>>
>>>
>>> Le 29/01/2017 à 11:12, Taher Alkhateeb a écrit :
>>>
>>> Okay, thank you for the efforts Jacques.

 The only thing that I suspect is related might be in Config.java where
 the
 portoffset is evaluated. I don't think I've changed the logic, and so I
 suspect that it is not related to Gradle. If the tests do not run on a
 portoffset, then I suspect perhaps they don't do the same on ant either.

 On Sun, Jan 29, 2017 at 12:57 PM, Jacques Le Roux <
 jacques.le.r...@les7arts.com> wrote:

 Hi Taher,

> Prior to Gradle migration we were not using the 8080 port during tests.
> For instance we could have an OFBiz instance running, playing with its
> UI
> and then run tests on another instance or vice-versa.
>
> This is no longer possible because now the port 8080 (and others) are
> kept
> open while running tests. So far it was only a "small" annoyance, but
> it's
> now blocking BuildBot because infra puppetized the BuildBot slaves
> https://s.apache.org/pWQD.
>
> And, I don't know why and this could be a question to infra, for a
> reason
> there is always a Tomcat instance running on port 8080 these hosts
> https://s.apache.org/iSaN
>
> I thought we could bypass this issue by using portoffset with
> testIntegration task since it's now required. But I just tested locally
> and
> it seems to not work. I'm not quite sure and will try a last thing
> directly
> "on" Buildbot. If it does not work we have to think about removing this

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Come on Taher,

As I said below (my last message) BuildBot is only revealing a symptom.

I already explained in this thread http://markmail.org/message/h4i7cn4i2btugdwn:

>


I suggest that you test by yourself to be convinced.

I also wrote in this same email <>

I did, now waiting their answer... and focusing on other matters in the 
meantime...

Jacques

Le 29/01/2017 à 14:27, Taher Alkhateeb a écrit :

What does gradle have to do with blocking these ports? This is stuff
related to Tomcat. There is nothing in both ant and gradle that has
anything to do with these ports afaik.

On Jan 29, 2017 4:16 PM, "Jacques Le Roux" 
wrote:


Taher,

I did not say that "ant run-tests" can use portoffset. Indeed it's not,
and I was overzealous when, long ago and yesterday in r1780660, I changed
the Java code of tests for that (related with portoffset). Because I did
not change how the tests are running in pre Gradle versions. Actually I was
then unsure and preferred to cover all cases. So, I repeat: we never
use/block ports (at least 8080 and I guess 8443) when running tests in pre
Gradle versions.

For instance if you look for

f_ofb_15.addStep(Compile(command=["ant" , "load-demo"],
and
f_ofb_15.addStep(Compile(command=["ant" , "run-tests"],

in https://svn.apache.org/repos/infra/infrastructure/buildbot/a
egis/buildmaster/master1/projects/ofbiz.conf (for committers only)

You will see that we don't use portoffset in Buildbot and it works well:

https://ci.apache.org/projects/ofbiz/logs/15.12/html/ (ran yesterday)

But since Gradle migration something has surely changed. As Buildbot shows
(it's a side effect here, but it's also Buildbot role to track
regressions), the ports are used(?)/blocked when running tests in post
Gradle versions.
I believe the best for us is to remove that, if it's possible. I'll have a
look in Config.java. I'll not feel offended if someone beats me on it...

Thanks

Jacques


Le 29/01/2017 à 11:12, Taher Alkhateeb a écrit :


Okay, thank you for the efforts Jacques.

The only thing that I suspect is related might be in Config.java where the
portoffset is evaluated. I don't think I've changed the logic, and so I
suspect that it is not related to Gradle. If the tests do not run on a
portoffset, then I suspect perhaps they don't do the same on ant either.

On Sun, Jan 29, 2017 at 12:57 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

Hi Taher,

Prior to Gradle migration we were not using the 8080 port during tests.
For instance we could have an OFBiz instance running, playing with its UI
and then run tests on another instance or vice-versa.

This is no longer possible because now the port 8080 (and others) are
kept
open while running tests. So far it was only a "small" annoyance, but
it's
now blocking BuildBot because infra puppetized the BuildBot slaves
https://s.apache.org/pWQD.

And, I don't know why and this could be a question to infra, for a reason
there is always a Tomcat instance running on port 8080 these hosts
https://s.apache.org/iSaN

I thought we could bypass this issue by using portoffset with
testIntegration task since it's now required. But I just tested locally
and
it seems to not work. I'm not quite sure and will try a last thing
directly
"on" Buildbot. If it does not work we have to think about removing this
need of open ports while running tests, IOW to remove this regression
introduced with Gradle.

Before anything else, I will though ask infra why Tomcat is always
running
on these hosts...

Jacques


Le 27/01/2017 à 18:15, Taher Alkhateeb a écrit :

Why do we need to run the tests on portoffset?

On Fri, Jan 27, 2017 at 7:48 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

Ah, I forgot to say, that I have dropped BuildBot support for R12 and
R13.


Also that the pre-Gradle versions don't need portoffset



Le 27/01/2017 à 05:29, Jacques Le Roux a écrit :

Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :


But in the case of running integration tests with a portoffset we have


an issue which is blocking BuildBot now for trunk and

R16


Jacques

Re: buildbot failure in on ofbiz-trunk

[Taher Alkhateeb]

What does gradle have to do with blocking these ports? This is stuff
related to Tomcat. There is nothing in both ant and gradle that has
anything to do with these ports afaik.

On Jan 29, 2017 4:16 PM, "Jacques Le Roux" 
wrote:

> Taher,
>
> I did not say that "ant run-tests" can use portoffset. Indeed it's not,
> and I was overzealous when, long ago and yesterday in r1780660, I changed
> the Java code of tests for that (related with portoffset). Because I did
> not change how the tests are running in pre Gradle versions. Actually I was
> then unsure and preferred to cover all cases. So, I repeat: we never
> use/block ports (at least 8080 and I guess 8443) when running tests in pre
> Gradle versions.
>
> For instance if you look for
>
> f_ofb_15.addStep(Compile(command=["ant" , "load-demo"],
> and
> f_ofb_15.addStep(Compile(command=["ant" , "run-tests"],
>
> in https://svn.apache.org/repos/infra/infrastructure/buildbot/a
> egis/buildmaster/master1/projects/ofbiz.conf (for committers only)
>
> You will see that we don't use portoffset in Buildbot and it works well:
>
> https://ci.apache.org/projects/ofbiz/logs/15.12/html/ (ran yesterday)
>
> But since Gradle migration something has surely changed. As Buildbot shows
> (it's a side effect here, but it's also Buildbot role to track
> regressions), the ports are used(?)/blocked when running tests in post
> Gradle versions.
> I believe the best for us is to remove that, if it's possible. I'll have a
> look in Config.java. I'll not feel offended if someone beats me on it...
>
> Thanks
>
> Jacques
>
>
> Le 29/01/2017 à 11:12, Taher Alkhateeb a écrit :
>
>> Okay, thank you for the efforts Jacques.
>>
>> The only thing that I suspect is related might be in Config.java where the
>> portoffset is evaluated. I don't think I've changed the logic, and so I
>> suspect that it is not related to Gradle. If the tests do not run on a
>> portoffset, then I suspect perhaps they don't do the same on ant either.
>>
>> On Sun, Jan 29, 2017 at 12:57 PM, Jacques Le Roux <
>> jacques.le.r...@les7arts.com> wrote:
>>
>> Hi Taher,
>>>
>>> Prior to Gradle migration we were not using the 8080 port during tests.
>>> For instance we could have an OFBiz instance running, playing with its UI
>>> and then run tests on another instance or vice-versa.
>>>
>>> This is no longer possible because now the port 8080 (and others) are
>>> kept
>>> open while running tests. So far it was only a "small" annoyance, but
>>> it's
>>> now blocking BuildBot because infra puppetized the BuildBot slaves
>>> https://s.apache.org/pWQD.
>>>
>>> And, I don't know why and this could be a question to infra, for a reason
>>> there is always a Tomcat instance running on port 8080 these hosts
>>> https://s.apache.org/iSaN
>>>
>>> I thought we could bypass this issue by using portoffset with
>>> testIntegration task since it's now required. But I just tested locally
>>> and
>>> it seems to not work. I'm not quite sure and will try a last thing
>>> directly
>>> "on" Buildbot. If it does not work we have to think about removing this
>>> need of open ports while running tests, IOW to remove this regression
>>> introduced with Gradle.
>>>
>>> Before anything else, I will though ask infra why Tomcat is always
>>> running
>>> on these hosts...
>>>
>>> Jacques
>>>
>>>
>>> Le 27/01/2017 à 18:15, Taher Alkhateeb a écrit :
>>>
>>> Why do we need to run the tests on portoffset?

 On Fri, Jan 27, 2017 at 7:48 AM, Jacques Le Roux <
 jacques.le.r...@les7arts.com> wrote:

 Ah, I forgot to say, that I have dropped BuildBot support for R12 and
 R13.

> Also that the pre-Gradle versions don't need portoffset
>
>
>
> Le 27/01/2017 à 05:29, Jacques Le Roux a écrit :
>
> Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :
>
>> But in the case of running integration tests with a portoffset we have
>>
>>> an issue which is blocking BuildBot now for trunk and
>>>
>>> R16
>>>
>> Jacques
>>
>>
>>
>>
>>
>>
>

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Taher,

I did not say that "ant run-tests" can use portoffset. Indeed it's not, and I was overzealous when, long ago and yesterday in r1780660, I changed the 
Java code of tests for that (related with portoffset). Because I did not change how the tests are running in pre Gradle versions. Actually I was then 
unsure and preferred to cover all cases. So, I repeat: we never use/block ports (at least 8080 and I guess 8443) when running tests in pre Gradle 
versions.


For instance if you look for

f_ofb_15.addStep(Compile(command=["ant" , "load-demo"],
and
f_ofb_15.addStep(Compile(command=["ant" , "run-tests"],

in 
https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/ofbiz.conf
 (for committers only)

You will see that we don't use portoffset in Buildbot and it works well:

https://ci.apache.org/projects/ofbiz/logs/15.12/html/ (ran yesterday)

But since Gradle migration something has surely changed. As Buildbot shows (it's a side effect here, but it's also Buildbot role to track 
regressions), the ports are used(?)/blocked when running tests in post Gradle versions.

I believe the best for us is to remove that, if it's possible. I'll have a look 
in Config.java. I'll not feel offended if someone beats me on it...

Thanks

Jacques


Le 29/01/2017 à 11:12, Taher Alkhateeb a écrit :

Okay, thank you for the efforts Jacques.

The only thing that I suspect is related might be in Config.java where the
portoffset is evaluated. I don't think I've changed the logic, and so I
suspect that it is not related to Gradle. If the tests do not run on a
portoffset, then I suspect perhaps they don't do the same on ant either.

On Sun, Jan 29, 2017 at 12:57 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi Taher,

Prior to Gradle migration we were not using the 8080 port during tests.
For instance we could have an OFBiz instance running, playing with its UI
and then run tests on another instance or vice-versa.

This is no longer possible because now the port 8080 (and others) are kept
open while running tests. So far it was only a "small" annoyance, but it's
now blocking BuildBot because infra puppetized the BuildBot slaves
https://s.apache.org/pWQD.

And, I don't know why and this could be a question to infra, for a reason
there is always a Tomcat instance running on port 8080 these hosts
https://s.apache.org/iSaN

I thought we could bypass this issue by using portoffset with
testIntegration task since it's now required. But I just tested locally and
it seems to not work. I'm not quite sure and will try a last thing directly
"on" Buildbot. If it does not work we have to think about removing this
need of open ports while running tests, IOW to remove this regression
introduced with Gradle.

Before anything else, I will though ask infra why Tomcat is always running
on these hosts...

Jacques


Le 27/01/2017 à 18:15, Taher Alkhateeb a écrit :


Why do we need to run the tests on portoffset?

On Fri, Jan 27, 2017 at 7:48 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

Ah, I forgot to say, that I have dropped BuildBot support for R12 and R13.

Also that the pre-Gradle versions don't need portoffset



Le 27/01/2017 à 05:29, Jacques Le Roux a écrit :

Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :

But in the case of running integration tests with a portoffset we have

an issue which is blocking BuildBot now for trunk and

R16

Jacques

Re: buildbot failure in on ofbiz-trunk

[Taher Alkhateeb]

Okay, thank you for the efforts Jacques.

The only thing that I suspect is related might be in Config.java where the
portoffset is evaluated. I don't think I've changed the logic, and so I
suspect that it is not related to Gradle. If the tests do not run on a
portoffset, then I suspect perhaps they don't do the same on ant either.

On Sun, Jan 29, 2017 at 12:57 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi Taher,
>
> Prior to Gradle migration we were not using the 8080 port during tests.
> For instance we could have an OFBiz instance running, playing with its UI
> and then run tests on another instance or vice-versa.
>
> This is no longer possible because now the port 8080 (and others) are kept
> open while running tests. So far it was only a "small" annoyance, but it's
> now blocking BuildBot because infra puppetized the BuildBot slaves
> https://s.apache.org/pWQD.
>
> And, I don't know why and this could be a question to infra, for a reason
> there is always a Tomcat instance running on port 8080 these hosts
> https://s.apache.org/iSaN
>
> I thought we could bypass this issue by using portoffset with
> testIntegration task since it's now required. But I just tested locally and
> it seems to not work. I'm not quite sure and will try a last thing directly
> "on" Buildbot. If it does not work we have to think about removing this
> need of open ports while running tests, IOW to remove this regression
> introduced with Gradle.
>
> Before anything else, I will though ask infra why Tomcat is always running
> on these hosts...
>
> Jacques
>
>
> Le 27/01/2017 à 18:15, Taher Alkhateeb a écrit :
>
>> Why do we need to run the tests on portoffset?
>>
>> On Fri, Jan 27, 2017 at 7:48 AM, Jacques Le Roux <
>> jacques.le.r...@les7arts.com> wrote:
>>
>> Ah, I forgot to say, that I have dropped BuildBot support for R12 and R13.
>>>
>>> Also that the pre-Gradle versions don't need portoffset
>>>
>>>
>>>
>>> Le 27/01/2017 à 05:29, Jacques Le Roux a écrit :
>>>
>>> Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :

 But in the case of running integration tests with a portoffset we have
> an issue which is blocking BuildBot now for trunk and
>
> R16

 Jacques




>

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Hi Taher,

Prior to Gradle migration we were not using the 8080 port during tests. For instance we could have an OFBiz instance running, playing with its UI and 
then run tests on another instance or vice-versa.


This is no longer possible because now the port 8080 (and others) are kept open while running tests. So far it was only a "small" annoyance, but it's 
now blocking BuildBot because infra puppetized the BuildBot slaves https://s.apache.org/pWQD.


And, I don't know why and this could be a question to infra, for a reason there is always a Tomcat instance running on port 8080 these hosts 
https://s.apache.org/iSaN


I thought we could bypass this issue by using portoffset with testIntegration task since it's now required. But I just tested locally and it seems to 
not work. I'm not quite sure and will try a last thing directly "on" Buildbot. If it does not work we have to think about removing this need of open 
ports while running tests, IOW to remove this regression introduced with Gradle.


Before anything else, I will though ask infra why Tomcat is always running on 
these hosts...

Jacques


Le 27/01/2017 à 18:15, Taher Alkhateeb a écrit :

Why do we need to run the tests on portoffset?

On Fri, Jan 27, 2017 at 7:48 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Ah, I forgot to say, that I have dropped BuildBot support for R12 and R13.

Also that the pre-Gradle versions don't need portoffset



Le 27/01/2017 à 05:29, Jacques Le Roux a écrit :


Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :


But in the case of running integration tests with a portoffset we have
an issue which is blocking BuildBot now for trunk and


R16

Jacques

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

OK I thought about this. It seems we have 2 issues:

1) when using portoffset with testIntegration (on Builbot or locally), on error OFBiz does not report to runtime\logs\test-results\html eg: 
https://ci.apache.org/projects/ofbiz/logs/trunk/


2) We need a patch or another mechanism to test with portoffset. Because of XMLRPC and SOAP tests, see port 8080 harcoded in XmlRpcTests class, 
serviceengine.xml and testRemoteSoap service definition


To be continued later...

Jacques

Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :

I don't know why my last message did not reach the ML.

Anyway, I have fixed the issue, and made some cleaning, in the Buildbot config 
script.

But we have an issue "with Gradle" when running test

java -jar build/libs/ofbiz.jar -t --portoffset 1

while loading data is OK

java -jar build/libs/ofbiz.jar -l --portoffset 1

These is one of the 2 regressions I experienced so far. The other being unable 
to run OFBiz inside Eclipse (in Debug mode or not).

We already spoke about Eclipse. And if I regret a bit to no longer being able to run a build in Eclipse with 1 click and then, also with 1 click, 
run OFBiz in Debug mode or not, other good aspects largely overweight this small drawbacks (sorry I could not resist to this rant)


But in the case of running integration tests with a portoffset we have an issue 
which is blocking BuildBot now for trunk and

I'll try to have a look today, but of course I'd be very glad if someone (hint 
Taher ;)) beats me on it

Thanks

Jacques


Le 26/01/2017 à 06:58, Jacques Le Roux a écrit :

https://issues.apache.org/jira/browse/INFRA-13402

Jacques


Le 25/01/2017 à 10:13, Jacques Le Roux a écrit :

Tests pass on Ubuntu locally. Buildbot runs also on Ubuntu (though newer 
version).

So I'm now pretty sure it's a setting in Buildbot which has changed. I'll see 
with infra. Please devs until it's fixed refer to your local builds

Jacques


Le 25/01/2017 à 09:06, Jacques Le Roux a écrit :

Mmm, there is definitely an embarrassment with Buildbot after r1780133 
https://ci.apache.org/builders/ofbiz-trunk

I though don't see how it could be related with your changes and as it works 
perfectly locally (even on Win7!) I guess it's rather on Buildbot.

I'll check and see with infra if I can't find it by myself...

Jacques


Le 25/01/2017 à 07:55, Jacques Le Roux a écrit :

Hi Jinghai,

You are welcome, I'll have a look ASAP (not right now, I must move)

Cheers

Jacques

PS: No worries, it works here (locally on Win7) so it's a Builbot hiccup, I'll 
check that



Le 25/01/2017 à 04:59, Shi Jinghai a écrit :

Hmm, I read the log and found some errors. I don't know how to resolve these 
problems.

This error is the first one and I guess it causes other errors:
Jan 25, 2017 3:14:06 AM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler 
["http-nio-8080"]
java.net.BindException: Address already in use

I need Jacques's help ... HELP ...

-邮件原件-
发件人: build...@apache.org [mailto:build...@apache.org]
发送时间: 2017年1月25日 11:18
收件人: dev@ofbiz.apache.org
主题: buildbot failure in on ofbiz-trunk

The Buildbot has detected a new failure on builder ofbiz-trunk while building . 
Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk/builds/1861

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build Build Source Stamp: [branch ofbiz/trunk] 1780133
Blamelist: shijh

BUILD FAILED: failed shell_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

I explained in this thread at http://markmail.org/message/63ik3ofjuztdjrcf

Jacques


Le 27/01/2017 à 18:15, Taher Alkhateeb a écrit :

Why do we need to run the tests on portoffset?

On Fri, Jan 27, 2017 at 7:48 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Ah, I forgot to say, that I have dropped BuildBot support for R12 and R13.

Also that the pre-Gradle versions don't need portoffset



Le 27/01/2017 à 05:29, Jacques Le Roux a écrit :


Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :


But in the case of running integration tests with a portoffset we have
an issue which is blocking BuildBot now for trunk and


R16

Jacques

Re: buildbot failure in on ofbiz-trunk

[Taher Alkhateeb]

Why do we need to run the tests on portoffset?

On Fri, Jan 27, 2017 at 7:48 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Ah, I forgot to say, that I have dropped BuildBot support for R12 and R13.
>
> Also that the pre-Gradle versions don't need portoffset
>
>
>
> Le 27/01/2017 à 05:29, Jacques Le Roux a écrit :
>
>> Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :
>>
>>> But in the case of running integration tests with a portoffset we have
>>> an issue which is blocking BuildBot now for trunk and
>>>
>> R16
>>
>> Jacques
>>
>>
>>
>

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Ah, I forgot to say, that I have dropped BuildBot support for R12 and R13.

Also that the pre-Gradle versions don't need portoffset


Le 27/01/2017 à 05:29, Jacques Le Roux a écrit :

Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :
But in the case of running integration tests with a portoffset we have an issue which is blocking BuildBot now for trunk and 

R16

Jacques

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :
But in the case of running integration tests with a portoffset we have an issue which is blocking BuildBot now for trunk and 

R16

Jacques

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

I don't know why my last message did not reach the ML.

Anyway, I have fixed the issue, and made some cleaning, in the Buildbot config 
script.

But we have an issue "with Gradle" when running test

java -jar build/libs/ofbiz.jar -t --portoffset 1

while loading data is OK

java -jar build/libs/ofbiz.jar -l --portoffset 1

These is one of the 2 regressions I experienced so far. The other being unable 
to run OFBiz inside Eclipse (in Debug mode or not).

We already spoke about Eclipse. And if I regret a bit to no longer being able to run a build in Eclipse with 1 click and then, also with 1 click, run 
OFBiz in Debug mode or not, other good aspects largely overweight this small drawbacks (sorry I could not resist to this rant)


But in the case of running integration tests with a portoffset we have an issue 
which is blocking BuildBot now for trunk and

I'll try to have a look today, but of course I'd be very glad if someone (hint 
Taher ;)) beats me on it

Thanks

Jacques


Le 26/01/2017 à 06:58, Jacques Le Roux a écrit :

https://issues.apache.org/jira/browse/INFRA-13402

Jacques


Le 25/01/2017 à 10:13, Jacques Le Roux a écrit :

Tests pass on Ubuntu locally. Buildbot runs also on Ubuntu (though newer 
version).

So I'm now pretty sure it's a setting in Buildbot which has changed. I'll see 
with infra. Please devs until it's fixed refer to your local builds

Jacques


Le 25/01/2017 à 09:06, Jacques Le Roux a écrit :

Mmm, there is definitely an embarrassment with Buildbot after r1780133 
https://ci.apache.org/builders/ofbiz-trunk

I though don't see how it could be related with your changes and as it works 
perfectly locally (even on Win7!) I guess it's rather on Buildbot.

I'll check and see with infra if I can't find it by myself...

Jacques


Le 25/01/2017 à 07:55, Jacques Le Roux a écrit :

Hi Jinghai,

You are welcome, I'll have a look ASAP (not right now, I must move)

Cheers

Jacques

PS: No worries, it works here (locally on Win7) so it's a Builbot hiccup, I'll 
check that



Le 25/01/2017 à 04:59, Shi Jinghai a écrit :

Hmm, I read the log and found some errors. I don't know how to resolve these 
problems.

This error is the first one and I guess it causes other errors:
Jan 25, 2017 3:14:06 AM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler 
["http-nio-8080"]
java.net.BindException: Address already in use

I need Jacques's help ... HELP ...

-邮件原件-
发件人: build...@apache.org [mailto:build...@apache.org]
发送时间: 2017年1月25日 11:18
收件人: dev@ofbiz.apache.org
主题: buildbot failure in on ofbiz-trunk

The Buildbot has detected a new failure on builder ofbiz-trunk while building . 
Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk/builds/1861

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build Build Source Stamp: [branch ofbiz/trunk] 1780133
Blamelist: shijh

BUILD FAILED: failed shell_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

https://issues.apache.org/jira/browse/INFRA-13402

Jacques


Le 25/01/2017 à 10:13, Jacques Le Roux a écrit :

Tests pass on Ubuntu locally. Buildbot runs also on Ubuntu (though newer 
version).

So I'm now pretty sure it's a setting in Buildbot which has changed. I'll see 
with infra. Please devs until it's fixed refer to your local builds

Jacques


Le 25/01/2017 à 09:06, Jacques Le Roux a écrit :

Mmm, there is definitely an embarrassment with Buildbot after r1780133 
https://ci.apache.org/builders/ofbiz-trunk

I though don't see how it could be related with your changes and as it works 
perfectly locally (even on Win7!) I guess it's rather on Buildbot.

I'll check and see with infra if I can't find it by myself...

Jacques


Le 25/01/2017 à 07:55, Jacques Le Roux a écrit :

Hi Jinghai,

You are welcome, I'll have a look ASAP (not right now, I must move)

Cheers

Jacques

PS: No worries, it works here (locally on Win7) so it's a Builbot hiccup, I'll 
check that



Le 25/01/2017 à 04:59, Shi Jinghai a écrit :

Hmm, I read the log and found some errors. I don't know how to resolve these 
problems.

This error is the first one and I guess it causes other errors:
Jan 25, 2017 3:14:06 AM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler 
["http-nio-8080"]
java.net.BindException: Address already in use

I need Jacques's help ... HELP ...

-邮件原件-
发件人: build...@apache.org [mailto:build...@apache.org]
发送时间: 2017年1月25日 11:18
收件人: dev@ofbiz.apache.org
主题: buildbot failure in on ofbiz-trunk

The Buildbot has detected a new failure on builder ofbiz-trunk while building . 
Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk/builds/1861

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build Build Source Stamp: [branch ofbiz/trunk] 1780133
Blamelist: shijh

BUILD FAILED: failed shell_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Tests pass on Ubuntu locally. Buildbot runs also on Ubuntu (though newer 
version).

So I'm now pretty sure it's a setting in Buildbot which has changed. I'll see 
with infra. Please devs until it's fixed refer to your local builds

Jacques


Le 25/01/2017 à 09:06, Jacques Le Roux a écrit :

Mmm, there is definitely an embarrassment with Buildbot after r1780133 
https://ci.apache.org/builders/ofbiz-trunk

I though don't see how it could be related with your changes and as it works 
perfectly locally (even on Win7!) I guess it's rather on Buildbot.

I'll check and see with infra if I can't find it by myself...

Jacques


Le 25/01/2017 à 07:55, Jacques Le Roux a écrit :

Hi Jinghai,

You are welcome, I'll have a look ASAP (not right now, I must move)

Cheers

Jacques

PS: No worries, it works here (locally on Win7) so it's a Builbot hiccup, I'll 
check that



Le 25/01/2017 à 04:59, Shi Jinghai a écrit :

Hmm, I read the log and found some errors. I don't know how to resolve these 
problems.

This error is the first one and I guess it causes other errors:
Jan 25, 2017 3:14:06 AM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler 
["http-nio-8080"]
java.net.BindException: Address already in use

I need Jacques's help ... HELP ...

-邮件原件-
发件人: build...@apache.org [mailto:build...@apache.org]
发送时间: 2017年1月25日 11:18
收件人: dev@ofbiz.apache.org
主题: buildbot failure in on ofbiz-trunk

The Buildbot has detected a new failure on builder ofbiz-trunk while building . 
Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk/builds/1861

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build Build Source Stamp: [branch ofbiz/trunk] 1780133
Blamelist: shijh

BUILD FAILED: failed shell_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Mmm, there is definitely an embarrassment with Buildbot after r1780133 
https://ci.apache.org/builders/ofbiz-trunk

I though don't see how it could be related with your changes and as it works 
perfectly locally (even on Win7!) I guess it's rather on Buildbot.

I'll check and see with infra if I can't find it by myself...

Jacques


Le 25/01/2017 à 07:55, Jacques Le Roux a écrit :

Hi Jinghai,

You are welcome, I'll have a look ASAP (not right now, I must move)

Cheers

Jacques

PS: No worries, it works here (locally on Win7) so it's a Builbot hiccup, I'll 
check that



Le 25/01/2017 à 04:59, Shi Jinghai a écrit :

Hmm, I read the log and found some errors. I don't know how to resolve these 
problems.

This error is the first one and I guess it causes other errors:
Jan 25, 2017 3:14:06 AM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler 
["http-nio-8080"]
java.net.BindException: Address already in use

I need Jacques's help ... HELP ...

-邮件原件-
发件人: build...@apache.org [mailto:build...@apache.org]
发送时间: 2017年1月25日 11:18
收件人: dev@ofbiz.apache.org
主题: buildbot failure in on ofbiz-trunk

The Buildbot has detected a new failure on builder ofbiz-trunk while building . 
Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk/builds/1861

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build Build Source Stamp: [branch ofbiz/trunk] 1780133
Blamelist: shijh

BUILD FAILED: failed shell_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Hi Jinghai,

You are welcome, I'll have a look ASAP (not right now, I must move)

Cheers

Jacques

PS: No worries, it works here (locally on Win7) so it's a Builbot hiccup, I'll 
check that



Le 25/01/2017 à 04:59, Shi Jinghai a écrit :

Hmm, I read the log and found some errors. I don't know how to resolve these 
problems.

This error is the first one and I guess it causes other errors:
Jan 25, 2017 3:14:06 AM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler 
["http-nio-8080"]
java.net.BindException: Address already in use

I need Jacques's help ... HELP ...

-邮件原件-
发件人: build...@apache.org [mailto:build...@apache.org]
发送时间: 2017年1月25日 11:18
收件人: dev@ofbiz.apache.org
主题: buildbot failure in on ofbiz-trunk

The Buildbot has detected a new failure on builder ofbiz-trunk while building . 
Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk/builds/1861

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build Build Source Stamp: [branch ofbiz/trunk] 1780133
Blamelist: shijh

BUILD FAILED: failed shell_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Shi Jinghai]

Hmm, I read the log and found some errors. I don't know how to resolve these 
problems.

This error is the first one and I guess it causes other errors:
Jan 25, 2017 3:14:06 AM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler 
["http-nio-8080"]
java.net.BindException: Address already in use

I need Jacques's help ... HELP ...

-邮件原件-
发件人: build...@apache.org [mailto:build...@apache.org] 
发送时间: 2017年1月25日 11:18
收件人: dev@ofbiz.apache.org
主题: buildbot failure in on ofbiz-trunk

The Buildbot has detected a new failure on builder ofbiz-trunk while building . 
Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk/builds/1861

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' 
triggered this build Build Source Stamp: [branch ofbiz/trunk] 1780133
Blamelist: shijh

BUILD FAILED: failed shell_1

Sincerely,
 -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Taher Alkhateeb]

Okay, I'm not sure if this is a passing fluke, but all tests pass locally.

On Tue, Dec 6, 2016 at 3:49 PM,  wrote:

> The Buildbot has detected a new failure on builder ofbiz-trunk while
> building . Full details are available at:
> https://ci.apache.org/builders/ofbiz-trunk/builds/1775
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit'
> triggered this build
> Build Source Stamp: [branch ofbiz/trunk] 1772879
> Blamelist: taher
>
> BUILD FAILED: failed shell_4
>
> Sincerely,
>  -The Buildbot
>
>
>
>

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Yes I also checked tests locally just after the commit, I confirm and Builbot 
continued OK later

Thanks to care Deepak

Jacques


Le 30/11/2016 à 08:50, Deepak Dixit a écrit :

I think its an false report, as  testIntegration return success on local
box.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Tue, Nov 29, 2016 at 11:47 PM,  wrote:


The Buildbot has detected a new failure on builder ofbiz-trunk while
building . Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk/builds/1765

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit'
triggered this build
Build Source Stamp: [branch ofbiz/trunk] 1771935
Blamelist: deepak

BUILD FAILED: failed shell_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Deepak Dixit]

I think its an false report, as  testIntegration return success on local
box.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Tue, Nov 29, 2016 at 11:47 PM,  wrote:

> The Buildbot has detected a new failure on builder ofbiz-trunk while
> building . Full details are available at:
> https://ci.apache.org/builders/ofbiz-trunk/builds/1765
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit'
> triggered this build
> Build Source Stamp: [branch ofbiz/trunk] 1771935
> Blamelist: deepak
>
> BUILD FAILED: failed shell_1
>
> Sincerely,
>  -The Buildbot
>
>
>
>

Re: buildbot failure in on ofbiz-trunk

[Deepak Dixit]

yes may be, not sure :)

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sun, Jun 12, 2016 at 2:10 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Ah, maybe fixed with r1747963?
>
> Jacques
>
>
>
> Le 12/06/2016 à 10:39, Jacques Le Roux a écrit :
>
>> We don't have history on HTML test results. So it's hard to tell now ,
>> because you have successfully committed since (would need to browse
>> https://ci.apache.org/builders/ofbiz-trunk/builds/826/steps/compile_1/logs/stdio
>> ).
>> Anyway it works now so just forget it ;)
>>
>> Jacques
>>
>> Le 12/06/2016 à 09:38, Deepak Dixit a écrit :
>>
>>> I don't know why buildbot send failure notification for r#1747956, In
>>> this
>>> commit changes only done for  PartyServices.java and all the party
>>> related
>>> test passed successfully.
>>>
>>> {quote}
>>>
>>>   [java] 2016-06-12 07:12:56,826 |main
>>> |GenericDelegator  |I| Rolling back 42 entity operations
>>>   [java] 2016-06-12 07:12:57,359 |main
>>> |TestRunContainer  |I| [JUNIT] Results for test suite:
>>> partytests
>>>   [java] 2016-06-12 07:12:57,359 |main
>>> |TestRunContainer  |I| [JUNIT] Pass: true | # Tests: 16 |
>>> # Failed: 0 # Errors: 0
>>>
>>> {quote}
>>>
>>> Thanks & Regards
>>> --
>>> Deepak Dixit
>>> www.hotwaxsystems.com
>>>
>>> On Sun, Jun 12, 2016 at 12:44 PM,  wrote:
>>>
>>> The Buildbot has detected a new failure on builder ofbiz-trunk while
 building . Full details are available at:
  https://ci.apache.org/builders/ofbiz-trunk/builds/826

 Buildbot URL: https://ci.apache.org/

 Buildslave for this Build: silvanus_ubuntu

 Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit'
 triggered this build
 Build Source Stamp: [branch ofbiz/trunk] 1747956
 Blamelist: deepak

 BUILD FAILED: failed compile_1

 Sincerely,
   -The Buildbot





>>
>

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

Ah, maybe fixed with r1747963?

Jacques


Le 12/06/2016 à 10:39, Jacques Le Roux a écrit :
We don't have history on HTML test results. So it's hard to tell now , because you have successfully committed since (would need to browse 
https://ci.apache.org/builders/ofbiz-trunk/builds/826/steps/compile_1/logs/stdio).

Anyway it works now so just forget it ;)

Jacques

Le 12/06/2016 à 09:38, Deepak Dixit a écrit :

I don't know why buildbot send failure notification for r#1747956, In this
commit changes only done for  PartyServices.java and all the party related
test passed successfully.

{quote}

  [java] 2016-06-12 07:12:56,826 |main
|GenericDelegator  |I| Rolling back 42 entity operations
  [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Results for test suite:
partytests
  [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Pass: true | # Tests: 16 |
# Failed: 0 # Errors: 0

{quote}

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sun, Jun 12, 2016 at 12:44 PM,  wrote:


The Buildbot has detected a new failure on builder ofbiz-trunk while
building . Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk/builds/826

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit'
triggered this build
Build Source Stamp: [branch ofbiz/trunk] 1747956
Blamelist: deepak

BUILD FAILED: failed compile_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Jacques Le Roux]

We don't have history on HTML test results. So it's hard to tell now , because you have successfully committed since (would need to browse 
https://ci.apache.org/builders/ofbiz-trunk/builds/826/steps/compile_1/logs/stdio).

Anyway it works now so just forget it ;)

Jacques

Le 12/06/2016 à 09:38, Deepak Dixit a écrit :

I don't know why buildbot send failure notification for r#1747956, In this
commit changes only done for  PartyServices.java and all the party related
test passed successfully.

{quote}

  [java] 2016-06-12 07:12:56,826 |main
|GenericDelegator  |I| Rolling back 42 entity operations
  [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Results for test suite:
partytests
  [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Pass: true | # Tests: 16 |
# Failed: 0 # Errors: 0

{quote}

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sun, Jun 12, 2016 at 12:44 PM,  wrote:


The Buildbot has detected a new failure on builder ofbiz-trunk while
building . Full details are available at:
 https://ci.apache.org/builders/ofbiz-trunk/builds/826

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit'
triggered this build
Build Source Stamp: [branch ofbiz/trunk] 1747956
Blamelist: deepak

BUILD FAILED: failed compile_1

Sincerely,
  -The Buildbot

Re: buildbot failure in on ofbiz-trunk

[Deepak Dixit]

I don't know why buildbot send failure notification for r#1747956, In this
commit changes only done for  PartyServices.java and all the party related
test passed successfully.

{quote}

 [java] 2016-06-12 07:12:56,826 |main
|GenericDelegator  |I| Rolling back 42 entity operations
 [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Results for test suite:
partytests
 [java] 2016-06-12 07:12:57,359 |main
|TestRunContainer  |I| [JUNIT] Pass: true | # Tests: 16 |
# Failed: 0 # Errors: 0

{quote}

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sun, Jun 12, 2016 at 12:44 PM,  wrote:

> The Buildbot has detected a new failure on builder ofbiz-trunk while
> building . Full details are available at:
> https://ci.apache.org/builders/ofbiz-trunk/builds/826
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit'
> triggered this build
> Build Source Stamp: [branch ofbiz/trunk] 1747956
> Blamelist: deepak
>
> BUILD FAILED: failed compile_1
>
> Sincerely,
>  -The Buildbot
>
>
>
>

Re: buildbot failure in on ofbiz-trunk

[Taher Alkhateeb]

Gd

Ok so this means ofbiz is working correctly after fixing a regression which
freezes the system.

Now whoever commited something that breaks the system please fix it (has to
do with invoices).

Cheers,

Taher Allhateeb
On Jun 3, 2016 7:39 PM,  wrote:

> The Buildbot has detected a new failure on builder ofbiz-trunk while
> building . Full details are available at:
> https://ci.apache.org/builders/ofbiz-trunk/builds/771
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: orcus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit'
> triggered this build
> Build Source Stamp: [branch ofbiz/trunk] 1746737
> Blamelist: taher
>
> BUILD FAILED: failed compile_1
>
> Sincerely,
>  -The Buildbot
>
>
>
>