Hi Chris,
See my mail from yesterday: Clover does not have a problem with the code, it is more that the code nesting in this test is so deep, that the filename generated is too long for the underlying os. Maybe make test simplier with less code nesting (inner-inner-inner classes, too long variable names). The file name seems to be generated by that. ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen <http://www.thetaphi.de/> http://www.thetaphi.de eMail: [email protected] From: Chris Male [mailto:[email protected]] Sent: Thursday, July 05, 2012 7:41 AM To: [email protected] Subject: Re: [JENKINS] Lucene-trunk - Build # 1981 - Still Failing I don't really get what is going on here, apart from that Clover is failing due to this test. The file it is looking for seems crazy, is that expected? Having looked at the test, I haven't come across the @ParametersFactory annotation before but maybe that somehow doesn't work with Clover? On Thu, Jul 5, 2012 at 5:34 PM, Apache Jenkins Server <[email protected]> wrote: Build: https://builds.apache.org/job/Lucene-trunk/1981/ All tests passed Build Log: [...truncated 37937 lines...] [...truncated 37937 lines...] [...truncated 37937 lines...] [...truncated 37937 lines...] [...truncated 37937 lines...] [...truncated 37937 lines...] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] -- Chris Male
