To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
Adam R. B. Jack wrote:
The usual test failed: dotnet.xml
So the question: should we the DotnetTest to the patternset
id=teststhatfail (line 330)?
After that Gump go ahead and other projects too.
We know that there is an error inside ...
Interesting, so you can allow a specific test to fail w/o
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
The usual test failed: dotnet.xml
So the question: should we the DotnetTest to the patternset
id=teststhatfail (line 330)?
After that Gump go ahead and other projects too.
We know that there is an error inside ...
Interesting, so you can allow a specific test to fail w/o halting? Neat.
I'd say
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
The usual test failed: dotnet.xml
So the question: should we the DotnetTest to the patternset
id=teststhatfail (line 330)?
After that Gump go ahead and other projects too.
We know that there is an error inside ...
Jan
Testcase:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
On Wed, 11 Aug 2004, Steve Loughran [EMAIL PROTECTED] wrote:
More likely we are passing something in on the command line it
doesnt like -or the source or path is unsupported.
Absolutely not:
testCSC-Mono:
[csc] working from source directory
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
Rmic passed. DotNet failed.
Jan
Testcase: testCSC(org.apache.tools.ant.taskdefs.optional.DotnetTest):
Caused an ERROR
csc returned: 129
/usr/local/gump/public/workspace/ant/src/etc/testcases/taskdefs/optional/dot
net.xml:157: csc returned: 129
at
[csc] ** ERROR **: file critical-sections.c: line 89
(DeleteCriticalSection): assertion failed: (ret == 0)
[csc] aborting...
BUILD FAILED
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155:
csc returned: 129
at
On Wed, 11 Aug 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote:
Wild-arsed guess, but I wonder if Brutus' two CPUs have something to
do with this.
Possible, I vaguely recall that brutus was running a non-standard
kernel as well.
Is there a simpler test we can run?
This is really just invoking
Wild-arsed guess, but I wonder if Brutus' two CPUs have something to
do with this.
Possible, I vaguely recall that brutus was running a non-standard
kernel as well.
BTW: Leo just updated Mono from 1.0-3 to 1.0-4 on Brutus. I think the
kernel is 'testing', but I don't think it is any more
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
On Tue, 10 Aug 2004, Stefan Bodewig [EMAIL PROTECTED] wrote:
ant -f src/etc/testcases/taskdefs/optional/dotnet.xml testCSC -v
probe_for_apps:
Property ${env.Path} has not been set
[available] Found: ilasm in /usr/bin
[echo] ilasm.found=true
Property ${env.Path} has not been set
Stefan Bodewig wrote:
On Mon, 9 Aug 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote:
So, how do we get more details so we can debug this?
Run the Ant targets the test would run in verbose or debug mode
directly. I.e.
ant -f src/etc/testcases/taskdefs/optional/dotnet.xml testCSC -v
or something
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
http://brutus.apache.org/gump/public/ant/test-ant/gump_work/build_ant_test-a
nt.txt
Testcase: testCompilerAttribute(org.apache.tools.ant.taskdefs.RmicTest):
FAILED
default value
junit.framework.AssertionFailedError: default value
at junit.framework.Assert.fail(Assert.java:47)
at
Gump Integration Build wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community
On Mon, 9 Aug 2004, Steve Loughran wrote:
we are back to CSC failing:
[junit] Testcase:
testCSC(org.apache.tools.ant.taskdefs.optional.DotnetTest): Caused an
ERROR
[junit] csc returned: 129
[junit]
/usr/local/gump/public/workspace/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
On Wed, 4 Aug 2004, Stefan Bodewig wrote:
These are the .NET tasks failing (brutus now has Mono installed).
Since I'm unsure whether this is a glitch with the Mono install, let's
wait for the next Gump run before we proceed.
So Ant is using a summary print for tests, not fully reports? If it were
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
[junit] Testcase:
testCSC(org.apache.tools.ant.taskdefs.optional.DotnetTest): Caused an
ERROR
[junit] csc returned: 129
[junit]
/usr/local/gump/public/workspace/ant/src/etc/testcases/taskdefs/optional/dot
net.xml:155: csc returned: 129
[junit] at
These are the .NET tasks failing (brutus now has Mono installed).
Since I'm unsure whether this is a glitch with the Mono install, let's
wait for the next Gump run before we proceed.
Stefan
-
To unsubscribe, e-mail: [EMAIL
Gump Integration Build wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
[junit] Testcase:
testIllegalCustomAlgorithm(org.apache.tools.ant.types.selectors.ModifiedSele
ctorTest): FAILED
[junit] Wrong exception message. expected:Specified class
(javax.swing.JFrame) is not an Algorithm. but
was:java.awt.HeadlessException
I´ll have a look at that.
Jan
Ok, API-Doc sais
Thrown when code that is dependent on a keyboard, display, or mouse is
called in an environment that does not support a keyboard, display, or
mouse.
I´ll change the used class from javax.swing.JFrame to a non-gui class.
Should solve that :)
Jan
-Ursprüngliche
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
This issue affects 1
I can´t see anything ... besides the last message build success ...
Can anybody else find the error?
Jan
-Original Message-
From: Gump Integration Build [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 27, 2004 9:42 PM
To: [EMAIL PROTECTED]
Subject: [EMAIL PROTECTED]: ant/test-ant
On Fri, 28 May 2004, Jan Materne [EMAIL PROTECTED] wrote:
I can´t see anything ...
Neither can I.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project test-ant has an issue affecting its community integration.
Project State : 'Failed',
41 matches
Mail list logo