2:08 p.m.
The current build fails on smoke tests for me. Tried 2 times now.
See attached files.
Yesterday evening everything was working.
So some of the late commits from yesterday or those from today broke the
testsuite.
2:17 p.m.
Are you doing a "./build.sh clean install"?
If not, try it.
On 07/12/2012 03:08 PM, Frank Langelage wrote:
The current build fails on smoke tests for me. Tried 2 times now.
See attached files.
Yesterday evening everything was working.
So some of the late commits from yesterday or those from today broke the
testsuite.
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4:09 p.m.
Yes, but in 2 steps
build.sh clean
then the git pull
and then build.sh
without install but that's the default if nothing is given.
After third or fourth try the build including the smoke tests was
successful now.
Some and then a smoke test fails for me.
I thought it's something to do with the workload on the machine when
doing the build and tests. It's a quite old machine (1,2 GHz CPUs).
The default deployment-timeout of 60 seconds is not sufficient when
starting the JBoss instance with more than 1 ear deployed.
So I increased it to 300 sec. for my needs.
6:20 p.m.
I'm seeing the same failure on lightning now
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/313...
On 07/12/2012 05:09 PM, Frank Langelage wrote:
Yes, but in 2 steps
build.sh clean
then the git pull
and then build.sh
without install but that's the default if nothing is given.
After third or fourth try the build including the smoke tests was
successful now.
Some and then a smoke test fails for me.
I thought it's something to do with the workload on the machine when
doing the build and tests. It's a quite old machine (1,2 GHz CPUs).
The default deployment-timeout of 60 seconds is not sufficient when
starting the JBoss instance with more than 1 ear deployed.
So I increased it to 300 sec. for my needs.
6:26 p.m.
I have an idea what is causing this, I will try and sort it out today.
Stuart
On 13/07/2012, at 9:20 AM, Scott Marlow wrote:
I'm seeing the same failure on lightning now
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/313...
On 07/12/2012 05:09 PM, Frank Langelage wrote:
> Yes, but in 2 steps
> build.sh clean
> then the git pull
> and then build.sh
> without install but that's the default if nothing is given.
>
> After third or fourth try the build including the smoke tests was
> successful now.
>
> Some and then a smoke test fails for me.
> I thought it's something to do with the workload on the machine when
> doing the build and tests. It's a quite old machine (1,2 GHz CPUs).
>
> The default deployment-timeout of 60 seconds is not sufficient when
> starting the JBoss instance with more than 1 ear deployed.
> So I increased it to 300 sec. for my needs.
>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
9:25 p.m.
I think this is an OSGI issue, I have emailed Thomas with details on what I believe is
causing it.
Stuart
On 13/07/2012, at 9:20 AM, Scott Marlow wrote:
I'm seeing the same failure on lightning now
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/313...
On 07/12/2012 05:09 PM, Frank Langelage wrote:
> Yes, but in 2 steps
> build.sh clean
> then the git pull
> and then build.sh
> without install but that's the default if nothing is given.
>
> After third or fourth try the build including the smoke tests was
> successful now.
>
> Some and then a smoke test fails for me.
> I thought it's something to do with the workload on the machine when
> doing the build and tests. It's a quite old machine (1,2 GHz CPUs).
>
> The default deployment-timeout of 60 seconds is not sufficient when
> starting the JBoss instance with more than 1 ear deployed.
> So I increased it to 300 sec. for my needs.
>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
2:20 a.m.
Yes, its a race and here is the PR that takes care of that
https://github.com/jbossas/jboss-as/pull/2669
(Unfortunately) we only had successful runs before it made it into master.
cheers
-thomas
On 07/12/2012 09:08 PM, Frank Langelage wrote:
The current build fails on smoke tests for me. Tried 2 times now.
See attached files.
Yesterday evening everything was working.
So some of the late commits from yesterday or those from today broke
the testsuite.
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
4331
days inactive
4332
days old
6 comments
4 participants
participants (4)
-
Frank Langelage -
Scott Marlow -
Stuart Douglas -
Thomas Diesler