Le 18 mars 2012 à 07:40, Stefan Bodewig a écrit :
> On 2012-03-16, Nicolas Lalevée wrote:
>
>> Le 16 mars 2012 à 06:02, Stefan Bodewig a écrit :
>
>>> On 2012-03-09, Nicolas Lalevée wrote:
>
As a quick fix I guess we can add in the command line launched by
Jenkins a -Djava.io.tmpdir=
On 2012-03-16, Nicolas Lalevée wrote:
> Le 16 mars 2012 à 06:02, Stefan Bodewig a écrit :
>> On 2012-03-09, Nicolas Lalevée wrote:
>>> As a quick fix I guess we can add in the command line launched by
>>> Jenkins a -Djava.io.tmpdir=$WORKSPACE/tmpdir
>> Have you changed the configuration to cont
Le 16 mars 2012 à 06:02, Stefan Bodewig a écrit :
> On 2012-03-09, Nicolas Lalevée wrote:
>
>> As a quick fix I guess we can add in the command line launched by
>> Jenkins a -Djava.io.tmpdir=$WORKSPACE/tmpdir
>
> Have you changed the configuration to contain that? If so, it doesn't
> look to h
On 2012-03-09, Nicolas Lalevée wrote:
> As a quick fix I guess we can add in the command line launched by
> Jenkins a -Djava.io.tmpdir=$WORKSPACE/tmpdir
Have you changed the configuration to contain that? If so, it doesn't
look to have had any effect.
Stefan
---
On 03/09/2012 04:16 AM, Nicolas Lalevée wrote:
As a quick fix I guess we can add in the command line launched by Jenkins a
-Djava.io.tmpdir=$WORKSPACE/tmpdir
I guess that would work for the AntUnit tests, so try that. For JUnit tests it
would probably have no effect since these run in a forke
As a quick fix I guess we can add in the command line launched by Jenkins a
-Djava.io.tmpdir=$WORKSPACE/tmpdir
Should I do that or we want to get rid of java.io.tmpdir ?
Nicolas
Le 9 mars 2012 à 05:57, Stefan Bodewig a écrit :
> On 2012-03-09, Jesse Glick wrote:
>
>> On 03/08/2012 12:04 AM, S
On 2012-03-09, Jesse Glick wrote:
> On 03/08/2012 12:04 AM, Stefan Bodewig wrote:
>> do we have to do anything special to provide the Jenkins build with a
>> ${java.to.tmpdir} that it actually is allowed to write to?
> Using ${java.io.tmpdir} from tests is a bit dangerous anyway; the
> files may
On 03/08/2012 12:04 AM, Stefan Bodewig wrote:
do we have to do anything special to provide the Jenkins build with a
${java.to.tmpdir} that it actually is allowed to write to?
Using ${java.io.tmpdir} from tests is a bit dangerous anyway; the files may rarely or never get cleaned up, you need to
On 2012-03-07, Jesse Glick wrote:
> On 03/06/2012 12:53 PM, Nicolas Lalevée wrote:
>> [AntUnit] results were not aggregated by Jenkins. I have fixed it.
> Confirmed; #462 shows tons of AntUnit failures. Whoever wrote these
> tests and is still around, consider reviewing them.
I had a quick look,
On 03/06/2012 06:21 PM, Jesse Glick wrote:
#462 shows tons of AntUnit failures
BTW I disabled email notifications as it looks like we are a long way from
fixing all of these tests.
-
To unsubscribe, e-mail: dev-unsubscr...@
On 03/06/2012 12:53 PM, Nicolas Lalevée wrote:
[AntUnit] results were not aggregated by Jenkins. I have fixed it.
Confirmed; #462 shows tons of AntUnit failures. Whoever wrote these tests and is still around, consider reviewing them. (I do not think it is safe to do much of anything
in trunk u
Le 6 mars 2012 à 15:38, Jesse Glick a écrit :
> On 03/05/2012 01:33 PM, Jesse Glick wrote:
>> I am looking into some of the test failures.
>
> I think I have fixed most of the failures, though there are still some things
> that seem to fail at random, especially on Windows.
great job !
> Two
On 03/05/2012 01:33 PM, Jesse Glick wrote:
I am looking into some of the test failures.
I think I have fixed most of the failures, though there are still some things
that seem to fail at random, especially on Windows.
Two points of confusion:
1. All the JDK 1.5 and 1.6 history - including te
On 03/03/2012 12:51 PM, Nicolas Lalevée wrote:
So we would have Ant_Nightly which builds the distrib of Ant and gather
findbugs warnings, java warnings and TODO/FIXMEs, and we would have the tests
run by Ant-Build-Matrix.
Looks like an improvement - thanks for setting this up. I am looking in
On 2012-03-03, Nicolas Lalevée wrote:
> Le 3 mars 2012 à 06:15, Stefan Bodewig a écrit :
>> Hi all,
>> before we can start using Java5 stuff in trunk, we need to disable the
>> JDK 1.4 build in Jenkins and replace it with a Java5 build (if there
>> isn't one already). It may be worthwhile to ha
Le 3 mars 2012 à 06:15, Stefan Bodewig a écrit :
> Hi all,
>
> before we can start using Java5 stuff in trunk, we need to disable the
> JDK 1.4 build in Jenkins and replace it with a Java5 build (if there
> isn't one already). It may be worthwhile to have a 1.4 build for the
> 1.8.x branch if w
Hi all,
before we can start using Java5 stuff in trunk, we need to disable the
JDK 1.4 build in Jenkins and replace it with a Java5 build (if there
isn't one already). It may be worthwhile to have a 1.4 build for the
1.8.x branch if we ever intend to create 1.8.4, but this can wait.
Can anybody
17 matches
Mail list logo
