The system variable has nothing to do with it. The output from tests is passed to report plugins and the default one printing to console simply discards whatever goes to sysout/syserr if a test passed (and within its suite's boundary). There is another report plugin that saves full output to disk so you have a few choices:
1) enable full sysout/syserr logging by passing tests.showSuccess=true to jenkins (or committing it in to the repo), 2) going to a particular jenkins plan, accessing the workspace and fetching build output for that test. For example: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/ws/lucene/build/core/test/tests-report.txt (this file may not be there if a build hasn't reached it yet). 3) ask Uwe or whoever is the jenkins admin to preserve **/tests-report.txt as a build artefact; this way you'd have some history to look at. These files are *big* though, especially for Solr which emits tons of logs. Dawid On Mon, Mar 4, 2013 at 9:47 PM, Erick Erickson <[email protected]> wrote: > I wasn't very clear. Since I can't get the tests to fail in my local > environment, I was trying for the verbose output for this particular test > _whenever_ the test was run. Is it reasonable to set the system var for > tests.showSuccess=true in my @BeforeClass? > > Thanks, > Erick > > > On Mon, Mar 4, 2013 at 9:52 AM, Dawid Weiss <[email protected]> > wrote: >> >> By default the output from tests that passed is not dumped to the >> console (you wouldn't be able to track which JVM dumped what anyway >> when running on multicore). If you need a full log then: >> >> > ant test-help >> ... >> [echo] # Include additional information like what is printed to >> [echo] # sysout/syserr, even if the test passes. >> [echo] # Enabled automatically when running for a single test case. >> [echo] ant -Dtests.showSuccess=true test >> >> Should do the job. If you'd like to see the output from jenkins or any >> other build server then, unless it fails, it won't be on the console. >> >> Dawid >> >> On Mon, Mar 4, 2013 at 3:48 PM, Erick Erickson <[email protected]> >> wrote: >> > I tried turning on verbose in the OpenCloseCoreStressTests by setting >> > System.setProperty("tests.verbose", "true"); >> > in @BeforeClass and, of course, it works on my machine. But the failed >> > test >> > logs don't have verbose output, is there some magic here? For the nonce, >> > I'm >> > just doing a bit of hard logging. >> > >> > I also found another place where I screwed up the a Stream by not >> > closing >> > it, ZkCLI of all places. I've checked that in. >> > >> > Of course all tests pass on my machine. Scant comfort that. >> > >> > I also had yet another assumption proved wrong so I didn't get any >> > useful >> > info from last night's failure, trying to add some more logging again >> > today. >> > Don't panic that the checking has my initials init, that's so I'm >> > absolutely >> > sure to know to take it out. >> > >> > Thanks, >> > Erick >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
