Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] BUILD STATUS:: trunk nightly build failed! 
Hi James,

The nightly build is composed of two parts, build and test on MySQL. I agree that test failures on MySQL should not fail a build, i.e., should not prevent the bits from uploading to the download site. Eric talked to me couple of days ago that he was working on a change on this.

The QA nightly testing now depends on the nightly build. If there are no new builds available on the download site, no tests will be run. Certainly, in this case, we can temporarily change to build locally and run the tests anyway, we didn't do that because we couldn't predict how long the situation was going to last. 

The Continuous Build was designed to help developers to detect issues promptly. It is responsible for breaking the no-build/no-test cycle. Unfortunately, in this case, the CB doesn't work for the same reason. 

The QA nightly testing is more responsible for the bits what customers can get, like nightly builds, milestones, release candidates on the download site. And the scope of the testing is much wider, like database/jdk/server certification and so on.

Thanks,
Edwin

-----Original Message-----
From: James Sutherland 
Sent: September 28, 2010 10:04 AM
To: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] BUILD STATUS:: trunk nightly build failed!

The dependency is on the jar not on the tests running successfully at Eclipse.  Just because a test failed on MySQL seems odd we would abort the entire nightly run.
Also a compile failure in utils or one component will not affect other components and still allow tests to run, even when the build fails.

If the Eclipse build fails and there is no updated jar, can we not just build locally just in that case?

Having the Oracle QA nightly test run would allow developers to figure out why the Eclipse test run is failing, and make getting the Eclipse build up and running again much easier.
Getting into the cycle of no build => no tests => more checkins causing more failures because they don't see the test failures => continued no-build/no-test cycle.

>> in rare cases like this time
Doesn't seem too rare...


-----Original Message-----
From: Edwin Tang 
Sent: Tuesday, September 28, 2010 9:40 AM
To: Dev mailing list for Eclipse Persistence Services
Cc: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] BUILD STATUS:: trunk nightly build failed!

Hi James,

We used to build everything and run the tests as long as there are any chech-ins. It is quite a while that we have changed to test the bits from the download site, which are generated by the nightly build. The advantage is obvious, we are testing what customers can grab. The disadvantage is the dependency, in rare cases like this time, no build then no test.

Thanks,
Edwin


On 2010-09-28, at 9:03 AM, James Sutherland <JAMES.SUTHERLAND@xxxxxxxxxx> wrote:

> The nightly Oracle QA runs have not occurred since the 22nd either, shouldn't these continue to run?
> They should not have any dependencies on the Eclipse nightly build or test run.
>
>
> -----Original Message-----
> From: Edwin Tang
> Sent: Monday, September 27, 2010 10:10 AM
> To: Dev mailing list for Eclipse Persistence Services; ejgwin@xxxxxxxxx
> Subject: Re: [eclipselink-dev] BUILD STATUS:: trunk nightly build failed!
>
> Hi Eric,
>
> We haven't had success nightly builds for trunk since 2010-09-22, for 2.1 branch since 2010-09-23. Do we figure out the cause yet?
>
> Thanks,
> Edwin
>
> -----Original Message-----
> From: Eric Gwin
> Sent: September 25, 2010 8:29 AM
> To: ejgwin@xxxxxxxxx; eclipselink-dev@xxxxxxxxxxx
> Subject: [eclipselink-dev] BUILD STATUS:: trunk nightly build failed!
>
> Build summary for 2.2.0.v20100925-r8242
> -----------------------------------
> Non-critical compilation issues (if any) reported in
> the format [BUILDLOG_LINE#: NUMBER_OF_ERRORS]:
> -----------------------------------
> Build log: (/shared/rt/eclipselink/logs/bsb-trunk_nightly_100925-0005.log)
> Build logs can be found on the download server at:
>    http://www.eclipse.org/eclipselink/downloads/build-failures.php
> -----------------------------------
>
> SVN Changes since Last Build:
> ------------------------------------------------------------------------
> r8242 | ailitchev | 2010-09-24 16:55:51 -0400 (Fri, 24 Sep 2010)
> Changed paths:
>   M /trunk/foundation/org.eclipse.persistence.core/src/org/eclipse/persistence/mappings/AggregateCollectionMapping.java
>   M /trunk/jpa/eclipselink.jpa.test/src/org/eclipse/persistence/testing/models/jpa/inherited/InheritedTableManager.java
>   M /trunk/jpa/eclipselink.jpa.test/src/org/eclipse/persistence/testing/models/jpa/inherited/RatedBeerConsumer.java
>   M /trunk/jpa/eclipselink.jpa.test/src/org/eclipse/persistence/testing/tests/jpa/inherited/InheritedModelJunitTest.java
> ------------------------------------------------------------------------
> r8241 | mobrien | 2010-09-24 12:01:58 -0400 (Fri, 24 Sep 2010)
> Changed paths:
>   M /trunk/jpa/eclipselink.jpa.test/src/org/eclipse/persistence/testing/models/jpa/metamodel/GalacticPosition.java
>   M /trunk/jpa/eclipselink.jpa.test/src/org/eclipse/persistence/testing/tests/jpa/advanced/concurrency/LifecycleJUnitTest.java
> ------------------------------------------------------------------------
> r8238 | agoerler | 2010-09-24 11:18:02 -0400 (Fri, 24 Sep 2010)
> Changed paths:
>   M /trunk/jpa/eclipselink.jpa.wdf.test/src/org/eclipse/persistence/testing/tests/wdf/jpa1/entitymanager/TestCascadeFlush.java
>   M /trunk/jpa/eclipselink.jpa.wdf.test/src/org/eclipse/persistence/testing/tests/wdf/jpa1/entitymanager/TestCascadePersist.java
> ------------------------------------------------------------------------
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev

Back to the top