Re: [openstack-dev] per process output from testr parallel?

2014-01-29 Thread Sean Dague
On 01/29/2014 07:27 PM, Robert Collins wrote: > On 30 January 2014 10:29, Sean Dague wrote: > > >>> would (worker-N) be sufficient? Or do you want *'s/x's specifically? >> >> So if we had worker-N we could play with a filter above that layer to do >> UI formatting. >> >> Realistically I had a st

Re: [openstack-dev] per process output from testr parallel?

2014-01-29 Thread Robert Collins
On 30 January 2014 10:29, Sean Dague wrote: >> would (worker-N) be sufficient? Or do you want *'s/x's specifically? > > So if we had worker-N we could play with a filter above that layer to do > UI formatting. > > Realistically I had a stream with enough metadata, and preferably a > solid parsin

Re: [openstack-dev] per process output from testr parallel?

2014-01-29 Thread Sean Dague
On 01/29/2014 04:19 PM, Robert Collins wrote: > On 26 January 2014 02:25, Sean Dague wrote: >> Something that's currently just far to manual to figure out is how testr >> is functioning in the parallel case, which tests are running on which >> process, and when does one of the pipelines run out of

Re: [openstack-dev] per process output from testr parallel?

2014-01-29 Thread Robert Collins
On 26 January 2014 02:25, Sean Dague wrote: > Something that's currently just far to manual to figure out is how testr > is functioning in the parallel case, which tests are running on which > process, and when does one of the pipelines run out of tests. The testr > assumption that you don't want

[openstack-dev] per process output from testr parallel?

2014-01-25 Thread Sean Dague
Something that's currently just far to manual to figure out is how testr is functioning in the parallel case, which tests are running on which process, and when does one of the pipelines run out of tests. The testr assumption that you don't want output unless there is a failure is a really bad assu