You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Luciano Resende <lr...@apache.org> on 2008/07/24 21:16:55 UTC
Continuum build notifications
I have recently changed the Tuscany continuum build schedules to once
a day instead of multiple times as it was originally set, and there
was also some changes on the build error notification e-mails, that
now contains only a summary of the errors and a link to the full log
as on the notification example below.
I was wondering that if we should get the build notifications back to
the dev-list, as this would help us to get and continue with a stable
trunk/build.
Thoughts ?
---------- Forwarded message ----------
From: Continuum@vmbuild.apache.org <co...@apache.org>
Date: Thu, Jul 3, 2008 at 3:18 AM
Subject: [continuum] BUILD FAILURE: Tuscany - Apache Tuscany SCA
Implementation Project - Build Def:
To: lresende@apache.org
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=99875&projectId=277
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 3 Jul 2008 03:15:26 -0700
Finished at: Thu 3 Jul 2008 03:17:35 -0700
Total time: 2m 9s
Build Trigger: Schedule
Build Number: 195
Exit code: 1
Building machine hostname: vmbuild.apache.org
Operating system : Linux(unknown)
Java Home version : java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)
Builder version :
Maven version: 2.0.8
Java version: 1.5.0_12
OS name: "linux" version: "2.6.20-16-server" arch: "i386" Family: "unix"
****************************************************************************
SCM Changes:
****************************************************************************
No files changed
****************************************************************************
Dependencies Changes:
****************************************************************************
No dependencies changed
****************************************************************************
Build Defintion:
****************************************************************************
POM filename: pom.xml
Goals: -Pdistribution clean install Arguments: --batch-mode
Build Fresh: true
Always Build: false
Default Build Definition: true
Schedule: DEFAULT_SCHEDULE
Profile Name: Java 5, Large Memory
Description:
****************************************************************************
Test Summary:
****************************************************************************
Tests: 108
Failures: 1
Total time: 8.749001
****************************************************************************
Test Failures:
****************************************************************************
DefaultCorbaHostTestCase
test_registerServant :
junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.fail(Assert.java:53)
at org.apache.tuscany.sca.host.corba.testing.DefaultCorbaHostTestCase.test_registerServant(DefaultCorbaHostTestCase.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Continuum build notifications
Posted by Simon Laws <si...@googlemail.com>.
On Mon, Aug 4, 2008 at 9:47 PM, Luciano Resende <lu...@gmail.com>wrote:
> I've made the following changes :
>
> - Changed build schedule to once a day at 2 AM
> - Changed build to use maven -fae in order to report all erros at once
> - Enabled notifications to be sent to dev list
>
> I also forced a build, in order to test the notifications being sent
> to the dev list.
>
> Please let me know if there are any issues.
>
> On Mon, Aug 4, 2008 at 6:05 AM, Giorgio Zoppi <gi...@gmail.com>
> wrote:
> > 2008/7/25 Raymond Feng <en...@gmail.com>:
> >> +1 to resume the notifications. We should try to fix build breaks as the
> 1st
> >> priority. Ensuring a good build is the basic confidence for the project.
> >
> >
> > I agree with you and what it doens't build should be commented in
> > order to be fixed.
> >
> > Cheers,
> > Giorgio.
> >
> > --
> > "I wish I were the first star that you see to shine every night 'cause
> > so you're eyes know that I look at you and that I'm always with
> > you..".. from Favola - Moda.
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>
Hi Luciano
I just made a change to stop the big model printout happening in the tool
build. Should make the results page smaller.
Simon
Re: Continuum build notifications
Posted by Luciano Resende <lu...@gmail.com>.
I've made the following changes :
- Changed build schedule to once a day at 2 AM
- Changed build to use maven -fae in order to report all erros at once
- Enabled notifications to be sent to dev list
I also forced a build, in order to test the notifications being sent
to the dev list.
Please let me know if there are any issues.
On Mon, Aug 4, 2008 at 6:05 AM, Giorgio Zoppi <gi...@gmail.com> wrote:
> 2008/7/25 Raymond Feng <en...@gmail.com>:
>> +1 to resume the notifications. We should try to fix build breaks as the 1st
>> priority. Ensuring a good build is the basic confidence for the project.
>
>
> I agree with you and what it doens't build should be commented in
> order to be fixed.
>
> Cheers,
> Giorgio.
>
> --
> "I wish I were the first star that you see to shine every night 'cause
> so you're eyes know that I look at you and that I'm always with
> you..".. from Favola - Moda.
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Continuum build notifications
Posted by Giorgio Zoppi <gi...@gmail.com>.
2008/7/25 Raymond Feng <en...@gmail.com>:
> +1 to resume the notifications. We should try to fix build breaks as the 1st
> priority. Ensuring a good build is the basic confidence for the project.
I agree with you and what it doens't build should be commented in
order to be fixed.
Cheers,
Giorgio.
--
"I wish I were the first star that you see to shine every night 'cause
so you're eyes know that I look at you and that I'm always with
you..".. from Favola - Moda.
Re: Continuum build notifications
Posted by Simon Laws <si...@googlemail.com>.
On Mon, Jul 28, 2008 at 1:58 PM, Dan Becker <da...@gmail.com> wrote:
> Luciano Resende wrote:
>
>> Ok, I'll resume build notifications early next week, this should give
>> EVERYBODY enough time to get things working smoothly. As a reminder,
>> build status and full logs can be seen in [1].
>>
>> [1]
>> http://vmbuild.apache.org/continuum/buildResults.action;jsessionid=2827ic4k5ujba?projectGroupId=19&projectId=277
>>
>>
> Thanks for the link. Definitely one for the bookmarks.
>
> --
> Thanks, Dan Becker
>
Hi Luciano
Did this happen? I don't see notifications and there are still build
failures.
Simon
Re: Continuum build notifications
Posted by Dan Becker <da...@gmail.com>.
Luciano Resende wrote:
> Ok, I'll resume build notifications early next week, this should give
> EVERYBODY enough time to get things working smoothly. As a reminder,
> build status and full logs can be seen in [1].
>
> [1] http://vmbuild.apache.org/continuum/buildResults.action;jsessionid=2827ic4k5ujba?projectGroupId=19&projectId=277
>
Thanks for the link. Definitely one for the bookmarks.
--
Thanks, Dan Becker
Re: Continuum build notifications
Posted by Luciano Resende <lu...@gmail.com>.
Ok, I'll resume build notifications early next week, this should give
EVERYBODY enough time to get things working smoothly. As a reminder,
build status and full logs can be seen in [1].
[1] http://vmbuild.apache.org/continuum/buildResults.action;jsessionid=2827ic4k5ujba?projectGroupId=19&projectId=277
On Fri, Jul 25, 2008 at 11:14 AM, Dan Becker <da...@gmail.com> wrote:
>> I was wondering that if we should get the build notifications back
>> to
>> the dev-list, as this would help us to get and continue with a
>> stable
>> trunk/build.
>>
>
> +1 from me
> --
> Thanks, Dan Becker
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Continuum build notifications
Posted by Dan Becker <da...@gmail.com>.
> I was wondering that if we should get the build notifications back to
> the dev-list, as this would help us to get and continue with a stable
> trunk/build.
>
+1 from me
--
Thanks, Dan Becker
Re: Continuum build notifications
Posted by Raymond Feng <en...@gmail.com>.
+1 to resume the notifications. We should try to fix build breaks as the 1st priority. Ensuring a good build is the basic confidence for the project.
Thanks,
Raymond
From: Simon Laws
Sent: Friday, July 25, 2008 12:28 AM
To: dev@tuscany.apache.org
Subject: Re: Continuum build notifications
On Thu, Jul 24, 2008 at 9:47 PM, Simon Nash <na...@apache.org> wrote:
ant elder wrote:
Big +1 from me, i'd probably prefer the messages go to the commit list but either would be an improvement.
We have clear evidence from the last few weeks that without these
timely public reminders of the status of the build, the trunk is in
a broken state far more often than it can be built cleanly. Looking
back at the continuum history, there have been no successful SCA Java
builds since the start of recorded history on May 7, 2008. So +++1
for restoring these notifications to the ML.
I think these notifications are useful to people other than the
committers, so I would prefer to have them on the dev list.
Simon
...ant
On Thu, Jul 24, 2008 at 8:16 PM, Luciano Resende <lresende@apache.org <ma...@apache.org>> wrote:
I have recently changed the Tuscany continuum build schedules to once
a day instead of multiple times as it was originally set, and there
was also some changes on the build error notification e-mails, that
now contains only a summary of the errors and a link to the full log
as on the notification example below.
I was wondering that if we should get the build notifications back to
the dev-list, as this would help us to get and continue with a stable
trunk/build.
Thoughts ?
---------- Forwarded message ----------
From: Continuum@vmbuild.apache.org
<ma...@vmbuild.apache.org> <continuum@apache.org
<ma...@apache.org>>
Date: Thu, Jul 3, 2008 at 3:18 AM
Subject: [continuum] BUILD FAILURE: Tuscany - Apache Tuscany SCA
Implementation Project - Build Def:
To: lresende@apache.org <ma...@apache.org>
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=99875&projectId=277
<http://vmbuild.apache.org/continuum/buildResult.action?buildId=99875&projectId=277>
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 3 Jul 2008 03:15:26 -0700
Finished at: Thu 3 Jul 2008 03:17:35 -0700
Total time: 2m 9s
Build Trigger: Schedule
Build Number: 195
Exit code: 1
Building machine hostname: vmbuild.apache.org
<http://vmbuild.apache.org>
Operating system : Linux(unknown)
Java Home version : java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode,
sharing)
Builder version :
Maven version: 2.0.8
Java version: 1.5.0_12
OS name: "linux" version: "2.6.20-16-server" arch: "i386"
Family: "unix"
****************************************************************************
SCM Changes:
****************************************************************************
No files changed
****************************************************************************
Dependencies Changes:
****************************************************************************
No dependencies changed
****************************************************************************
Build Defintion:
****************************************************************************
POM filename: pom.xml
Goals: -Pdistribution clean install Arguments: --batch-mode
Build Fresh: true
Always Build: false
Default Build Definition: true
Schedule: DEFAULT_SCHEDULE
Profile Name: Java 5, Large Memory
Description:
****************************************************************************
Test Summary:
****************************************************************************
Tests: 108
Failures: 1
Total time: 8.749001
****************************************************************************
Test Failures:
****************************************************************************
DefaultCorbaHostTestCase
test_registerServant :
junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.fail(Assert.java:53)
at
org.apache.tuscany.sca.host.corba.testing.DefaultCorbaHostTestCase.test_registerServant(DefaultCorbaHostTestCase.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
at
org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
at
org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at
org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
at
org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
at
org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
at
org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
at
org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
at
org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at
org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
<http://people.apache.org/%7Elresende>
http://lresende.blogspot.com/
+1 from me. We're working in the dark a little without them.
Simon
Re: Continuum build notifications
Posted by Simon Laws <si...@googlemail.com>.
On Thu, Jul 24, 2008 at 9:47 PM, Simon Nash <na...@apache.org> wrote:
> ant elder wrote:
>
>> Big +1 from me, i'd probably prefer the messages go to the commit list but
>> either would be an improvement.
>>
>> We have clear evidence from the last few weeks that without these
> timely public reminders of the status of the build, the trunk is in
> a broken state far more often than it can be built cleanly. Looking
> back at the continuum history, there have been no successful SCA Java
> builds since the start of recorded history on May 7, 2008. So +++1
> for restoring these notifications to the ML.
>
> I think these notifications are useful to people other than the
> committers, so I would prefer to have them on the dev list.
>
> Simon
>
> ...ant
>>
>> On Thu, Jul 24, 2008 at 8:16 PM, Luciano Resende <lresende@apache.org<mailto:
>> lresende@apache.org>> wrote:
>>
>> I have recently changed the Tuscany continuum build schedules to once
>> a day instead of multiple times as it was originally set, and there
>> was also some changes on the build error notification e-mails, that
>> now contains only a summary of the errors and a link to the full log
>> as on the notification example below.
>>
>> I was wondering that if we should get the build notifications back to
>> the dev-list, as this would help us to get and continue with a stable
>> trunk/build.
>>
>> Thoughts ?
>>
>>
>> ---------- Forwarded message ----------
>> From: Continuum@vmbuild.apache.org
>> <ma...@vmbuild.apache.org> <continuum@apache.org
>> <ma...@apache.org>>
>> Date: Thu, Jul 3, 2008 at 3:18 AM
>> Subject: [continuum] BUILD FAILURE: Tuscany - Apache Tuscany SCA
>> Implementation Project - Build Def:
>> To: lresende@apache.org <ma...@apache.org>
>>
>>
>> Online report :
>>
>> http://vmbuild.apache.org/continuum/buildResult.action?buildId=99875&projectId=277
>> <
>> http://vmbuild.apache.org/continuum/buildResult.action?buildId=99875&projectId=277
>> >
>>
>> Build statistics:
>> State: Failed
>> Previous State: Failed
>> Started at: Thu 3 Jul 2008 03:15:26 -0700
>> Finished at: Thu 3 Jul 2008 03:17:35 -0700
>> Total time: 2m 9s
>> Build Trigger: Schedule
>> Build Number: 195
>> Exit code: 1
>> Building machine hostname: vmbuild.apache.org
>> <http://vmbuild.apache.org>
>>
>> Operating system : Linux(unknown)
>> Java Home version : java version "1.5.0_12"
>> Java(TM) 2 Runtime Environment, Standard Edition (build
>> 1.5.0_12-b04)
>> Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode,
>> sharing)
>> Builder version :
>> Maven version: 2.0.8
>> Java version: 1.5.0_12
>> OS name: "linux" version: "2.6.20-16-server" arch: "i386"
>> Family: "unix"
>>
>> ****************************************************************************
>> SCM Changes:
>>
>> ****************************************************************************
>> No files changed
>>
>>
>> ****************************************************************************
>> Dependencies Changes:
>>
>> ****************************************************************************
>> No dependencies changed
>>
>>
>>
>> ****************************************************************************
>> Build Defintion:
>>
>> ****************************************************************************
>> POM filename: pom.xml
>> Goals: -Pdistribution clean install Arguments: --batch-mode
>> Build Fresh: true
>> Always Build: false
>> Default Build Definition: true
>> Schedule: DEFAULT_SCHEDULE
>> Profile Name: Java 5, Large Memory
>> Description:
>>
>> ****************************************************************************
>> Test Summary:
>>
>> ****************************************************************************
>> Tests: 108
>> Failures: 1
>> Total time: 8.749001
>>
>>
>> ****************************************************************************
>> Test Failures:
>>
>> ****************************************************************************
>>
>> DefaultCorbaHostTestCase
>> test_registerServant :
>> junit.framework.AssertionFailedError
>> junit.framework.AssertionFailedError: null
>> at junit.framework.Assert.fail(Assert.java:47)
>> at junit.framework.Assert.fail(Assert.java:53)
>> at
>>
>> org.apache.tuscany.sca.host.corba.testing.DefaultCorbaHostTestCase.test_registerServant(DefaultCorbaHostTestCase.java:94)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>>
>> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>> at
>>
>> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>> at
>>
>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>> at
>>
>> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>> at
>>
>> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>> at
>>
>> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>> at
>>
>> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>> at
>>
>> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>> at
>>
>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>> at
>> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>> at
>>
>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>> at
>>
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>> at
>>
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>>
>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>> at
>>
>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>>
>>
>>
>>
>>
>>
>> --
>> Luciano Resende
>> Apache Tuscany Committer
>> http://people.apache.org/~lresende<http://people.apache.org/%7Elresende>
>> <http://people.apache.org/%7Elresende>
>> http://lresende.blogspot.com/
>>
>>
>>
> +1 from me. We're working in the dark a little without them.
Simon
Re: Continuum build notifications
Posted by Simon Nash <na...@apache.org>.
ant elder wrote:
> Big +1 from me, i'd probably prefer the messages go to the commit list
> but either would be an improvement.
>
We have clear evidence from the last few weeks that without these
timely public reminders of the status of the build, the trunk is in
a broken state far more often than it can be built cleanly. Looking
back at the continuum history, there have been no successful SCA Java
builds since the start of recorded history on May 7, 2008. So +++1
for restoring these notifications to the ML.
I think these notifications are useful to people other than the
committers, so I would prefer to have them on the dev list.
Simon
> ...ant
>
> On Thu, Jul 24, 2008 at 8:16 PM, Luciano Resende <lresende@apache.org
> <ma...@apache.org>> wrote:
>
> I have recently changed the Tuscany continuum build schedules to once
> a day instead of multiple times as it was originally set, and there
> was also some changes on the build error notification e-mails, that
> now contains only a summary of the errors and a link to the full log
> as on the notification example below.
>
> I was wondering that if we should get the build notifications back to
> the dev-list, as this would help us to get and continue with a stable
> trunk/build.
>
> Thoughts ?
>
>
> ---------- Forwarded message ----------
> From: Continuum@vmbuild.apache.org
> <ma...@vmbuild.apache.org> <continuum@apache.org
> <ma...@apache.org>>
> Date: Thu, Jul 3, 2008 at 3:18 AM
> Subject: [continuum] BUILD FAILURE: Tuscany - Apache Tuscany SCA
> Implementation Project - Build Def:
> To: lresende@apache.org <ma...@apache.org>
>
>
> Online report :
> http://vmbuild.apache.org/continuum/buildResult.action?buildId=99875&projectId=277
> <http://vmbuild.apache.org/continuum/buildResult.action?buildId=99875&projectId=277>
>
> Build statistics:
> State: Failed
> Previous State: Failed
> Started at: Thu 3 Jul 2008 03:15:26 -0700
> Finished at: Thu 3 Jul 2008 03:17:35 -0700
> Total time: 2m 9s
> Build Trigger: Schedule
> Build Number: 195
> Exit code: 1
> Building machine hostname: vmbuild.apache.org
> <http://vmbuild.apache.org>
> Operating system : Linux(unknown)
> Java Home version : java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> 1.5.0_12-b04)
> Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode,
> sharing)
> Builder version :
> Maven version: 2.0.8
> Java version: 1.5.0_12
> OS name: "linux" version: "2.6.20-16-server" arch: "i386"
> Family: "unix"
> ****************************************************************************
> SCM Changes:
> ****************************************************************************
> No files changed
>
> ****************************************************************************
> Dependencies Changes:
> ****************************************************************************
> No dependencies changed
>
>
> ****************************************************************************
> Build Defintion:
> ****************************************************************************
> POM filename: pom.xml
> Goals: -Pdistribution clean install Arguments: --batch-mode
> Build Fresh: true
> Always Build: false
> Default Build Definition: true
> Schedule: DEFAULT_SCHEDULE
> Profile Name: Java 5, Large Memory
> Description:
> ****************************************************************************
> Test Summary:
> ****************************************************************************
> Tests: 108
> Failures: 1
> Total time: 8.749001
>
> ****************************************************************************
> Test Failures:
> ****************************************************************************
>
> DefaultCorbaHostTestCase
> test_registerServant :
> junit.framework.AssertionFailedError
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.fail(Assert.java:53)
> at
> org.apache.tuscany.sca.host.corba.testing.DefaultCorbaHostTestCase.test_registerServant(DefaultCorbaHostTestCase.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
> at
> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
> at
> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> at
> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
> at
> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
> at
> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
> at
> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
> at
> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
> at
> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> at
> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
> at
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>
>
>
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>
>
Re: Continuum build notifications
Posted by ant elder <an...@gmail.com>.
Big +1 from me, i'd probably prefer the messages go to the commit list but
either would be an improvement.
...ant
On Thu, Jul 24, 2008 at 8:16 PM, Luciano Resende <lr...@apache.org>
wrote:
> I have recently changed the Tuscany continuum build schedules to once
> a day instead of multiple times as it was originally set, and there
> was also some changes on the build error notification e-mails, that
> now contains only a summary of the errors and a link to the full log
> as on the notification example below.
>
> I was wondering that if we should get the build notifications back to
> the dev-list, as this would help us to get and continue with a stable
> trunk/build.
>
> Thoughts ?
>
>
> ---------- Forwarded message ----------
> From: Continuum@vmbuild.apache.org <co...@apache.org>
> Date: Thu, Jul 3, 2008 at 3:18 AM
> Subject: [continuum] BUILD FAILURE: Tuscany - Apache Tuscany SCA
> Implementation Project - Build Def:
> To: lresende@apache.org
>
>
> Online report :
>
> http://vmbuild.apache.org/continuum/buildResult.action?buildId=99875&projectId=277
>
> Build statistics:
> State: Failed
> Previous State: Failed
> Started at: Thu 3 Jul 2008 03:15:26 -0700
> Finished at: Thu 3 Jul 2008 03:17:35 -0700
> Total time: 2m 9s
> Build Trigger: Schedule
> Build Number: 195
> Exit code: 1
> Building machine hostname: vmbuild.apache.org
> Operating system : Linux(unknown)
> Java Home version : java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> 1.5.0_12-b04)
> Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)
> Builder version :
> Maven version: 2.0.8
> Java version: 1.5.0_12
> OS name: "linux" version: "2.6.20-16-server" arch: "i386" Family:
> "unix"
>
> ****************************************************************************
> SCM Changes:
>
> ****************************************************************************
> No files changed
>
>
> ****************************************************************************
> Dependencies Changes:
>
> ****************************************************************************
> No dependencies changed
>
>
>
> ****************************************************************************
> Build Defintion:
>
> ****************************************************************************
> POM filename: pom.xml
> Goals: -Pdistribution clean install Arguments: --batch-mode
> Build Fresh: true
> Always Build: false
> Default Build Definition: true
> Schedule: DEFAULT_SCHEDULE
> Profile Name: Java 5, Large Memory
> Description:
>
> ****************************************************************************
> Test Summary:
>
> ****************************************************************************
> Tests: 108
> Failures: 1
> Total time: 8.749001
>
>
> ****************************************************************************
> Test Failures:
>
> ****************************************************************************
>
> DefaultCorbaHostTestCase
> test_registerServant :
> junit.framework.AssertionFailedError
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.fail(Assert.java:53)
> at
> org.apache.tuscany.sca.host.corba.testing.DefaultCorbaHostTestCase.test_registerServant(DefaultCorbaHostTestCase.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
> at
> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
> at
> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> at
> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
> at
> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
> at
> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
> at
> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
> at
> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
> at
> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> at
> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
> at
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>
>
>
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>