[Bug 1484991] Re: Too hard to find results in the log files
Printing the summary at the end of logs indeed does sound like a good improvement, especially if a package has several tests and not the last one failed. I usually search for - - results in logs to jump between the test results, but this might be more obvious with a final summary. Moving summary from artifacts.tar.gz to result.tar seems okay, but not sure if that's still needed once log.gz gets the summary too? ** Changed in: autopkgtest (Ubuntu) Importance: Undecided = Wishlist ** Changed in: autopkgtest (Ubuntu) Status: New = Triaged ** Summary changed: - Too hard to find results in the log files + show summary at end of log file ** Changed in: autopkgtest (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- 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: show summary at end of log file 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
Re: [Bug 1484991] Re: Too hard to find results in the log files
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 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
[Bug 1484991] Re: Too hard to find results in the log files
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
