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
