Oh that figures, every time I have a brilliant idea, someone else has
already had it.  heh

On Fri, Sep 27, 2013 at 3:12 PM, Daniel Manrique
<email address hidden> wrote:
> On 13-09-27 03:03 PM, Jeff Lane wrote:
>> IMO, the correct behaviour should be that passing tests only retrieve
>> stdout while failures capture both stdout and stdin.
>>
>> I'm sure checkbox already caches these somehow, so that it can grab the
>> appropriate one for the results, so should be a matter of maybe either
>> concatenating them for failures, or simply changing the output to look
>> something like this for failed tests:
>>
>>
>> STDOUT:
>> soem stuff here
>> more stuff
>> usual suff
>> lots o output
>>
>> STDERR:
>> error message
>> more error messages
>>
>> The problem there is that it's possible the error messages will appear
>> out of sync with the non-error output.
>>
>> The only way I can think of to solve that would really be to dump them
>> together at the test level and just grab them all, or do something like
>> this:
>>
>> each line of output would become a tuple in an ordered list:
>>
>> 1:(stdout,'something')
>> 2:(stdout,'something more')
>> 3:(stderr,'error message')
>> 4:(stdout,'more output')
>
> ^^ This is *exactly* what plainbox does :) (it even captures timing
> information).
>
> I'll have a look at what checkbox knows about test output and see how we can
> accomodate this.
>
>>
>> then when the result is collected, they can be replayed in order and for
>> failures, grab all, and for pass, ignore anything with stderr in the
>> tuple...
>>
>> though that may be too complex an answer.,..
>>
>
> --
> You received this bug notification because you are a member of Checkbox
> Bug Wranglers, which is subscribed to checkbox.
> https://bugs.launchpad.net/bugs/1232077
>
> Title:
>   cpu stress test output on failure is not helpful
>
> Status in Checkbox System Testing:
>   New
>
> Bug description:
>   for some reason, the cpu stress test failed on a system being
>   certified, however, on looking at the output to try to sort out the
>   issue, I was only presented with this:
>
>   stress: FAIL: [8086] (416) <-- worker 8093 got signal 9
>   stress: WARN: [8086] (418) now reaping child worker processes
>   stress: FAIL: [8086] (422) kill error: No such process
>   stress: FAIL: [8086] (416) <-- worker 8097 got signal 9
>   stress: WARN: [8086] (418) now reaping child worker processes
>   stress: FAIL: [8086] (422) kill error: No such process
>   stress: FAIL: [8086] (416) <-- worker 8100 got signal 9
>   stress: WARN: [8086] (418) now reaping child worker processes
>   stress: FAIL: [8086] (422) kill error: No such process
>   stress: FAIL: [8086] (416) <-- worker 8099 got signal 9
>   stress: WARN: [8086] (418) now reaping child worker processes
>   stress: FAIL: [8086] (422) kill error: No such process
>   stress: FAIL: [8086] (452) failed run completed in 7200s
>
>   apparently, the REST of the output was dumped to stdout, while these
>   few lines appear in stderr, and because checkbox chooses stderr in
>   favor of stdout on failed tests, I only get the last few lines of
>   error output with no context to explain why it failed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/checkbox/+bug/1232077/+subscriptions



-- 
Jeff Lane - Server and Cloud Certification and Tools Development
Ubuntu Ham: W4KDH
Freenode IRC: bladernr or bladernr_
gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417  C466 4ABD 3635 3A14 B2DD