I think that's a short legged deer... or whatever the English idiom is, you
get the picture :) There will always be somebody who needs just N + 1 lines
of output and who will complain about it... Also, they'd still consume a
lot of space on jenkins if you have many builds.

If these logs (again -- for successful runs!) are really needed and used by
people (I doubt) then we could preserve those *.txt files as artefacts and
expire them after a certain number of builds? Or we could turn them on
temporarily for Erick and then disable back again once the problem is
resolved?

Dawid

On Tue, Mar 5, 2013 at 10:04 AM, Uwe Schindler <[email protected]> wrote:

> Maybe, as mentioned before, implement some "tail -####" logic and allow:
> <junit4:report-ant-xml dir="@{junit.output.dir}" outputStreams="8192" />
>
> To include the last 8192 lines only?
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
>
>
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]] On Behalf
> > Of Dawid Weiss
> > Sent: Tuesday, March 05, 2013 9:30 AM
> > To: [email protected]
> > Subject: Re: verbose logging
> >
> > You can enable them again. I've warned you though: it wasn't turned off
> > without a sensible reason; it'll be a problem sooner or later.
> > Those XML files were huge at times.
> >
> > Dawid
> >
> > On Tue, Mar 5, 2013 at 8:54 AM, Uwe Schindler <[email protected]> wrote:
> > > Yeah,
> > >
> > > it would be nice to have those, because with the Jenkins Web GUI you
> > could then inspect stdout from each test, like that one from
> forbiddenAPIs:
> > > http://jenkins.thetaphi.de/job/Forbidden-
> > APIs/119/testReport/src.test.antunit/TestClassDeclaration_xml/testForbidd
> > enExtends/?
> > > Can we maybe limit the amount and only have something like "tail
> -####",
> > so you get at least the recent stdout.
> > > I know that the plain text files are easier to write/manage, but the
> XML
> > files are good for inspection of test output with Jenkins. Currently the
> XML
> > output is only filled when test fail.
> > >
> > > Uwe
> > >
> > > -----
> > > Uwe Schindler
> > > H.-H.-Meier-Allee 63, D-28213 Bremen
> > > http://www.thetaphi.de
> > > eMail: [email protected]
> > >
> > >
> > >> -----Original Message-----
> > >> From: [email protected] [mailto:[email protected]] On
> > Behalf
> > >> Of Dawid Weiss
> > >> Sent: Tuesday, March 05, 2013 8:00 AM
> > >> To: [email protected]
> > >> Subject: Re: verbose logging
> > >>
> > >> common-build.xml:
> > >>
> > >>                 <!-- ANT-compatible XMLs for jenkins records etc. -->
> > >>                 <junit4:report-ant-xml dir="@{junit.output.dir}"
> > >> outputStreams="no" />
> > >>
> > >> Like I said though -- I would *not* bring stdout/stderr back to those
> > >> XML files unless you want to deal with other problems resulting from
> > >> 10+mb XML files. They also take a lot longer to serialize/ save than
> > >> just plain text output.
> > >>
> > >> Dawid
> > >>
> > >>
> > >> On Tue, Mar 5, 2013 at 7:58 AM, Dawid Weiss
> > >> <[email protected]> wrote:
> > >> >> I though the XML report files contain the whole stdout?
> > >> >>
> > >> >> http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/ws/solr/build
> > >> >> /so
> > >> >> lr-core/test/TEST-org.apache.solr.update.TestAtomicUpdateErrorCase
> > >> >> s.x
> > >> >> ml
> > >> >>
> > >> >> But its empty... This would be the most "correct" variant. I know
> > >> >> that by
> > >> default stock JUnit saves the whole stdout/stderr in the XML file,
> > >> but JUnit4 runner does not seem to do this?
> > >> >
> > >> > I used to emit stdout to those XML files but Solr emits so much
> > >> > logging information from certain tests that it got XML parsers/
> > >> > transformers hit OOM a few times on jenkins... I disabled it
> > >> > intentionally. Those plain-text files are still saved and they're
> > >> > more compact than XML output. I kept the XML output so that jenkins
> > >> > has stuff for its own analysis pipeline but standard output is not
> > >> > needed there.
> > >> >
> > >> > Dawid
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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]
> > >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>

Reply via email to