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/49
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: silvanus_ubuntu
Build Reason: forced: by
Either way, I have committed a fix in r1787627 that should take care of the
admin server blocking the port. Now it only starts for the "start" ofbiz
server command as opposed to test and load-data as well.
I think this permanently fixes the issue.
On Sun, Mar 19, 2017 at 4:15 PM, Taher Alkhateeb
Okay great!
Now the next question. Does buildbot fail on simultaneous commits to the
same branch or for different branches only? Meaning if we commit at the
same time to trunk it's okay but if we commit to trunk and 16.11 then it
fails?. I am asking because I assume only one build for one branch
Yes, that should do it
Jacques
Le 19/03/2017 à 13:01, Taher Alkhateeb a écrit :
Okay, so, to be absolutely exact, the repeat behavior is the following:
- checkout ofbiz r1744041
- ant clean-all load-demo
- ant start
- open a new terminal
- ant run-tests
- observe tests run successfully
And
Okay, so, to be absolutely exact, the repeat behavior is the following:
- checkout ofbiz r1744041
- ant clean-all load-demo
- ant start
- open a new terminal
- ant run-tests
- observe tests run successfully
And then
- checkout ofbiz r1744107
- ant clean-all load-demo
- ant start
- open a new
yep, you got it. But you also need an OFBiz instance running (previously) to
reproduce, of course!
Jacques
Le 19/03/2017 à 12:37, Taher Alkhateeb a écrit :
Sorry, I'm still lost, trying to explain it again:
Before the commit: "ant clean-all load-demo run-tests" works
after the commit: "ant
Le 19/03/2017 à 12:32, Jacques Le Roux a écrit :
It's quite simple, I repeat.
It's not specifically related with Buildbot despite the title. It was 1st
identified there.
If you run an OFBiz instance (I ran one at the "beforeGradle" tag, but we know
any commit version fits since it's
Sorry, I'm still lost, trying to explain it again:
Before the commit: "ant clean-all load-demo run-tests" works
after the commit: "ant clean-all load-demo run-tests" does not work with
the socket error message?
Is this now what you mean?
On Sun, Mar 19, 2017 at 2:32 PM, Jacques Le Roux <
It's quite simple, I repeat.
It's not specifically related with Buildbot despite the title. It was 1st
identified there.
If you run an OFBiz instance (I ran one at the "beforeGradle" tag, but we know
any commit version fits since it's currently reproducible on Buildbot)
Before your commit
The commit in question is not important because there are too many changes.
What we need is a "repeat" behavior. So my questions from this thread
remain to be answered before we can investigate.
On Sun, Mar 19, 2017 at 1:53 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Here it is
Here it is
--
git.exe bisect good
298c831a3aa1cea45b4aab66acebd9617f6615e0 is the first bad commit
commit 298c831a3aa1cea45b4aab66acebd9617f6615e0
Hi Jacques,
Sorry I still don't understand, let me try to capture this.
Scenario 1 - Using ant
- Start OFBiz using: ant start
- Run tests in another OFBiz using: ant run-tests
- OFBiz fails with an error message
Scenario 2 - Using gradle
- Start OFBiz using: ./gradlew ofbiz
- Run tests in
The Buildbot has detected a build exception on builder ofbiz-trunk-framework
while building . Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk-framework/builds/47
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: silvanus_ubuntu
Build Reason: forced:
Hi Taher,
Le 19/03/2017 à 04:18, Taher Alkhateeb a écrit :
Hi Jacques,
Okay just to try and understand your point, what are the circumstances in
which you are witnessing failure in post gradle but not pre-gradle?
Fortunately it's now simple.
You run an OFBiz instance with "ant start"
You run
14 matches
Mail list logo
