Le 29 janv. 2010 à 21:15, Jon Schneider a écrit :
> I did volunteer to do the release and got sidetracked. I've been thinking
> of it this week, and will be starting on it this weekend. I think it would
> be a valuable chance to gain some experience with it. Thanks for bringing
> it up again.
Being curious about this random fail and success build, I just noted that every
failing build was done on the ubuntu slaves, and the successful on the master.
I don't understand at all why it makes some copy of file fail, but I took the
initiative to tied the build to the master node as the JDK
Thanks Nicolas,
the root cause of this error was probably an exotic file system error
happening on the ubuntu slaves.
I read somewhere that this "Invalid Argument" error comes from the OS
which does not like some type of file system.
Regards,
Antoine
Nicolas Lalevée wrote:
Being curiou
As regular user, I've been using the 1.8 RC since it came out, haven't
noticed any problems
so +1 on Release as Apache Ant 1.8.0
(tought might be nice to have some feedback from community)
Keep up the good work!
Regards
On 30/01/2010 1:51, Antoine Levy Lambert wrote:
Hi,
a candidate for a
In Revision 793462, a BufferedWriter was added to
JUnitTestRunner.filterStack(String). However, the BufferedWriter was not
flushed before returning the underlying StringWriter's contents. This may
exclude all or part of the filtered stack trace from the returned String.
Attached is a patch cl
--- On Sat, 1/30/10, N C wrote:
> Attached is a patch closing the BufferedWriter.
I'm not sure the attachment went through...
--- JUnitTestRunner.java.orig 2010-01-30 16:22:58.0 -0500
+++ JUnitTestRunner.java2010-01-30 16:23:12.0 -0500
@@ -896,6 +896,7 @@
