I meant the output that is (optionally) generated by TSDebug() calls in trafficsever.
On Mon, Feb 4, 2019 at 5:52 PM Jason Kenny <jke...@verizonmedia.com> wrote: > > which debug output? autest or curl? > > On Mon, Feb 4, 2019 at 4:29 PM Pushkar Pradhan > <pprad...@verizonmedia.com.invalid> wrote: >> >> Walt, >> What is your proposal, is it to run all tests with debug output? >> This would require modifying all existing tests. That also brings up >> another question, what sections should be enabled? >> I.e. http, dns, iocore, .... >> >> One potential downfall to turning on debugging is that writing to the debug >> logs is a "synchronous" event which IMO changes the way TS runs during >> autests. >> As a result, Heisenbugs could slip by. A very low possibility and I am sure >> most people have good load testing to catch these anyway? >> >> On Fri, Feb 1, 2019 at 11:57 AM Miles Libbey <mlib...@apache.org> wrote: >> >> > Since we have no data what is taking time to run the suite of tests, >> > isn't it premature to be considering optimizations that may or may not >> > affect the time? >> > >> > miles >> > >> > On Fri, Feb 1, 2019 at 11:36 AM Walt Karas >> > <wka...@verizonmedia.com.invalid> wrote: >> > > >> > > Pushkar pointed out to me the link to get the _sanbox for Au tests run >> > > by CI checks: https://ci.trafficserver.apache.org/autest/ >> > > >> > > The availability of the _sandbox means we can see trace debug output >> > > if the test configures ATS to generate it. But enabling this output >> > > will cause some increase in the time to run all the tests, which is >> > > becoming an issue. What does everyone think, to trace or not to trace >> > > in the merged versions of the Au tests? >> >
