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?
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484991 Title: Too hard to find results in the log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1484991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
