Re: [platform-releng-dev] 4.3.0 N-Build: N20130406-1500 - BUILD FAILED

[David M Williams <david_williams@xxxxxxxxxx>]

No, we do use -fae, (--fail-at-end) thanks
to the tip from Jan Sievers in the bug I mentioned (Bug 404634)
and it is this that at least allows us to continue compiling other bundles,
... instead of stopping on the first compile error. 

But, without a true "failOnError=false"
supported, there is no jar produced, so even if I specify --fail-never
we do not get very much further, since there is no jar, many repositories,
etc., are not created and serious failures occur later. 

Keep in mind, one reason (of many) that I like "stopping
on errors", is that shortly after we started using Maven/Tycho there
were some builds that were producing "junk" ... sure, they'd
produce output, and yes, there were error messages in the megabytes of
logs produced, but without a clear idea of what can go wrong, and what
to look for, I find it preferable just to stop when an obvious error occurs,
rather then produce output which is not accurate. 

We are going to fail tonight's nightly build, unless a
JDT committer is around that can fix/revert the latest commit for Bug 385154.
Its even smaller than a "compile error", but "fail-never"
did not allow us to get much further ... in my local tests. 




From:      
 Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx>
To:      
 "Eclipse platform
release engineering list." <platform-releng-dev@xxxxxxxxxxx>,

Date:      
 04/08/2013 10:23 AM
Subject:    
   Re: [platform-releng-dev]
4.3.0 N-Build: N20130406-1500        -  
     BUILD        FAILED
Sent by:    
   platform-releng-dev-bounces@xxxxxxxxxxx

---

Probably because the –fae
option is not being specified on the command line.
 
 
From: platform-releng-dev-bounces@xxxxxxxxxxx
[mailto:platform-releng-dev-bounces@xxxxxxxxxxx]
On Behalf Of Daniel Megert
Sent: April-08-13 4:40 AM
To: Eclipse platform release engineering list.
Subject: Re: [platform-releng-dev] 4.3.0 N-Build: N20130406-1500 -
BUILD FAILED
 
Why does a compile error in one of the test
bundles cause the whole build to stop? I don't think this was the case
with the PDE build. 

Dani

From:	David M Williams <david_williams@xxxxxxxxxx>
To:	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>,
Date:	06.04.2013 23:26
Subject:	Re: [platform-releng-dev] 4.3.0 N-Build: N20130406-1500 - BUILD        FAILED

---

Some work to do to get compile errors "easy to see", but, besides
the huge log, I do grep them into a smaller file ... they are in 
org.eclipse.equinox.p2.tests.verifier
See 
http://download.eclipse.org/eclipse/downloads/drops4/N20130406-1500/buildFailed-run-maven-build





From:        e4Builder@xxxxxxxxxxx
To:        platform-releng-dev@xxxxxxxxxxx,
Date:        04/06/2013
05:11 PM 
Subject:        [platform-releng-dev]
4.3.0 N-Build: N20130406-1500 - BUILD FAILED
Sent by:        platform-releng-dev-bounces@xxxxxxxxxxx

---

Eclipse downloads: http://download.eclipse.org/eclipse/downloads/drops4/N20130406-1500/_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev