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 her
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 lis
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
throu
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 i
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 bu
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
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 i
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
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 sh
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
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 succe
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
>
>
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
b
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
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, Deepa
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
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
> -
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
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
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 relaun
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 Softwa
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:0
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-fra
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-t
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 t
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 commi
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 =
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
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...
J
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 e
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
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
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 comm
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
suspe
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 t
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
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 com
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 ha
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:
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. In
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
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
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 whil
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
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, tha
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 à 0
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
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
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
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
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,
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 c
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
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
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
>
> Bu
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.hot
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:
>
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
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
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, D
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
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 failur
62 matches
Mail list logo