Hi, I've been running the cache loader migration tests via maven and I spotted that only the first test results would print to the standard output. The rest of tests would run, but the output would not appear. Digging a little bit, I found http://jira.codehaus.org/browse/SUREFIRE-315 Basically, at the end of the first test run, whose results appear on the STDOUT (TransformingFileCacheLoaderTest), TestingUtil.recursiveFileRemove(targetLoc) is called which removes some files created during tests. Within TestingUtil.recursiveFileRemove(targetLoc) there's a System.out.println("Deleting file " + file); call which ends up messing test output. Removing it solves the problem. If everyone's happy with it, I would change this System.out.println call to a logger call.

Seriously though, thanks for the heads up on this. It's chasing down this kind of crap that's been consuming days of effort; good to know in advance where the land mines are. Brian Stansberry wrote: > Are you volunteering to replace the hundreds of such calls in the > JBoss Cache codebase. ;) If so, please move on and do JBoss AS when > you're done! > > Galder Zamarreno wrote: >> Hi, >> >> I've been running the cache loader migration tests via maven and I >> spotted that only the first test results would print to the standard >> output. The rest of tests would run, but the output would not appear. >> >> Digging a little bit, I found >> http://jira.codehaus.org/browse/SUREFIRE-315 >> >> Basically, at the end of the first test run, whose results appear on >> the STDOUT (TransformingFileCacheLoaderTest), >> TestingUtil.recursiveFileRemove(targetLoc) is called which removes >> some files created during tests. >> >> Within TestingUtil.recursiveFileRemove(targetLoc) there's a >> System.out.println("Deleting file " + file); call which ends up >> messing test output. Removing it solves the problem. >> >> If everyone's happy with it, I would change this System.out.println >> call to a logger call. >> > >

Refresh and install the support module, that should resolve it. Last week I disabled redirectTestOutputToFile because it causes way to many problems. Galder Zamarreno wrote: > Actually, tried changing System.out for logger and still had the same > issue. Ended up commenting that System.out call. I'll try to reproduce > this outside JBC to understand what circumstances lead to this. > > The only alternative is to grep the test results in the > target/sunfire-reports folder. > > Brian Stansberry wrote: >> Seriously though, thanks for the heads up on this. It's chasing down >> this kind of crap that's been consuming days of effort; good to know >> in advance where the land mines are. >> >> Brian Stansberry wrote: >>> Are you volunteering to replace the hundreds of such calls in the >>> JBoss Cache codebase. ;) If so, please move on and do JBoss AS when >>> you're done! >>> >>> Galder Zamarreno wrote: >>>> Hi, >>>> >>>> I've been running the cache loader migration tests via maven and I >>>> spotted that only the first test results would print to the >>>> standard output. The rest of tests would run, but the output would >>>> not appear. >>>> >>>> Digging a little bit, I found >>>> http://jira.codehaus.org/browse/SUREFIRE-315 >>>> >>>> Basically, at the end of the first test run, whose results appear >>>> on the STDOUT (TransformingFileCacheLoaderTest), >>>> TestingUtil.recursiveFileRemove(targetLoc) is called which removes >>>> some files created during tests. >>>> >>>> Within TestingUtil.recursiveFileRemove(targetLoc) there's a >>>> System.out.println("Deleting file " + file); call which ends up >>>> messing test output. Removing it solves the problem. >>>> >>>> If everyone's happy with it, I would change this System.out.println >>>> call to a logger call. >>>> >>> >>> >> >> >