[Bug 1484991] Re: Too hard to find results in the log files

[Barry Warsaw]

On Aug 14, 2015, at 03:19 PM, Martin Pitt wrote:

>Indeed the single "log" often isn't the easiest to consume output. But
>every individual test has its own <testname>-stdout and
><testname>-stderr artifact, which is also available from
>http://autopkgtest.ubuntu.com ("artifacts.tar.gz" link). stderr and exit
>codes are also contained in the "summary" file (also in
>artifacts.tar.gz). Is that more suitable for you? If not, how would you
>propose to do that in a better way?

Ah, good to know!  Maybe instead of putting those only in the artifacts
tarball, they could be unpacked and linked from the autopkgtests.ubuntu.com
page?

>As autopkgtest can't interpret the contents of that there isn't that
>much more that we can do beyond that. I. e. the actual test output is
>just a blob from autopkgtest's view.

But the final PASS/FAIL results and exit codes are available to autopkgtest,
right?  Maybe just a summary at the end could be printed with that
information?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1484991

Title:
  Too hard to find results in the log files

Status in autopkgtest package in Ubuntu:
  New

Bug description:
  Very often, it's quite difficult to find all the results in the log
  files.  If there's a lot of output between runs of separate tests, the
  results can be separated by a lot of output.  Further, there's no
  super great way to search for the results.

  Better would be something like Python's unittest suite where all
  failure results are captured and printed at the end of the run.  At
  least that way, all you'd need to do is scroll to the bottom of the
  log file and see all failures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1484991/+subscriptions