Thanks Jacques, fixed in revision 1806279.
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co
On Sat, Aug 26, 2017 at 2:15 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Actually I jus
Actually I just tested locally and found this error while trying to do "svn up &&
gradlew cleanAll eclipse loadAll testIntegration"
2017-08-26 10:33:41,546 |main |GenericDelegator |E| Failure in create operation for entity [WorkEffortType]:
org.apache.ofbiz.entity.GenericEntityExce
Hi,
Buildbot seems quite busy and is wrong there
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/405/steps/upload_1/logs/err.html
Just let's wait ;)
Jacques
Le 26/08/2017 à 09:53, build...@apache.org a écrit :
The Buildbot has detected a build exception on builder ofbiz-tr
+1
Looking forward
Jacques
Le 20/03/2017 à 11:24, Taher Alkhateeb a écrit :
Okay, given that we have removed the mystery of this whole thing, I suggest
to create a JIRA where we can slowly tackle this issue since most of the
commits go to trunk
On Mon, Mar 20, 2017 at 12:46 PM, Jacques Le Ro
Okay, given that we have removed the mystery of this whole thing, I suggest
to create a JIRA where we can slowly tackle this issue since most of the
commits go to trunk
On Mon, Mar 20, 2017 at 12:46 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Just try locally the same thing you d
Just try locally the same thing you did for trunk with the R16 branch, you will
reproduce
Jacques
Le 20/03/2017 à 10:32, Taher Alkhateeb a écrit :
Looking at the code, I don't see any port blocking for R15 or R16
On Mon, Mar 20, 2017 at 12:13 PM, Jacques Le Roux <
jacques.le.r...@les7arts.co
Looking at the code, I don't see any port blocking for R15 or R16
On Mon, Mar 20, 2017 at 12:13 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Hi Taher,
>
> Thanks for the fix, I have changed the log commit to refer to OFBIZ-9196
>
> About your question below. Actually, the problem
Hi Taher,
Thanks for the fix, I have changed the log commit to refer to OFBIZ-9196
About your question below. Actually, the problem is not related with Buildbot particularly. It's obvious since you were able to reproduce locally
using only a trunk instance.
Now, since it was introduced betwee
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 h
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 t
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 ter
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 cl
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 currentl
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 <
jacque
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 (r
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 anothe
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 t
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?
In other words what is the repeat process, the expected outcome and actual
outcome. I ask because I'm a bit confused not sure if you're referri
OK, I locally kept a version of the trunk just prior the Gradle switch.
When running an OFBiz instance (any one fits, I used the ofbiz-framework+plugin HEAD) you can run tests with R15, but not with this preGradle version.
You get
run-tests:
[java] org.ofbiz.base.start.StartupException: C
Le 18/03/2017 à 17:07, Taher Alkhateeb a écrit :
I think we discussed this in the past, but I will ask again for clarity ...
what does gradle have to do with port blocking?
For now I have no clear evidences. Only that before the Gradle move we had not the ports issues (locally and on Buildbot) I
I think we discussed this in the past, but I will ask again for clarity ...
what does gradle have to do with port blocking?
How can gradle or any build tool be responsible for blocking ports that are
not related to the build system but rather used from OFBiz directly?
On Mar 18, 2017 7:00 PM, "Ja
It's clearly related with OFBIZ-9196 "Regression: the testIntegration Gradle taks
shoud not use/block the ports"
The build in trunk and R16 overlap in time:
https://ci.apache.org/builders/ofbiz-trunk-framework/builds/44/
StartSat Mar 18 09:25:12 2017
EndSat Mar 18 09:26:56 2017
https:/
The problem after a second review of the logs is pretty clear. You have two
instances of OFBiz running and conflicting on ports. Either the first build
did not terminate while the second starts or shutdown is not occurring
cleanly. In other words, if you start ./gradlew "ofbiz load-data" &&
./gradl
Ctrl-C does not kill gradle and gradle does not need time to release
resources
On Mar 18, 2017 4:21 PM, "Jacques Le Roux"
wrote:
> Thanks James,
>
> Yes indeed, it takes a bit for Gradle, and especially its wrapper, to
> disconnect resources. I noticed that too on Windows, thought it was
> speci
Thanks James,
Yes indeed, it takes a bit for Gradle, and especially its wrapper, to disconnect resources. I noticed that too on Windows, thought it was specific to
Windows .
This could be the reason, though we don't use the wrapper in Buildbot. We could try to add a small pause (say 30 seconds
I got this issue too when I pressed CTL-C to exit OFBiz and then ran
"./gradew ofbiz" immediately.
Jacques Le Roux wrote
> Mmm, this is pretty bad
>
> https://ci.apache.org/builders/ofbiz-trunk-framework/builds/44/steps/shell_1/logs/stdio
>
>> Building 84% > :ofbiz --load-dataSet OFBIZ_HOME to
Of course no issues locally, same for R16.11
Maybe linked to pending
https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-13643
Let's see
Jacques
Le 18/03/2017 à 11:17, Jacques Le Roux a écrit :
Mmm, this is pretty bad
https://ci.apache.org/builders/ofbiz-trunk-framework/buil
Mmm, this is pretty bad
https://ci.apache.org/builders/ofbiz-trunk-framework/builds/44/steps/shell_1/logs/stdio
Building 84% > :ofbiz --load-dataSet OFBIZ_HOME to - /home/buildslave32/slave32/ofbiz-trunk-framework/build org.apache.ofbiz.base.start.StartupException: Couldn't create server
socket
31 matches
Mail list logo
