On Wed, Mar 12 2014, John Dennis wrote:
> On 03/12/2014 01:22 PM, Zane Bitter wrote:
>> On 10/03/14 20:29, Robert Collins wrote:
>>> Which bits look raw? It should only show text/* attachments, non-text
>>> should be named but not dumped.
>>
>> I was thinking of the:
>>
>> pythonlogging:'': {{{
On 03/12/2014 01:22 PM, Zane Bitter wrote:
> On 10/03/14 20:29, Robert Collins wrote:
>> Which bits look raw? It should only show text/* attachments, non-text
>> should be named but not dumped.
>
> I was thinking of the:
>
> pythonlogging:'': {{{
>
> part.
Yes, this is the primary culprit, it's
On 10/03/14 20:29, Robert Collins wrote:
Which bits look raw? It should only show text/* attachments, non-text
should be named but not dumped.
I was thinking of the:
pythonlogging:'': {{{
part.
- ZB
___
OpenStack-dev mailing list
OpenStack-dev@lis
On Mon, Mar 10, 2014 at 7:20 PM, Zane Bitter wrote:
> On 10/03/14 16:04, Clark Boylan wrote:
>
>> On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter wrote:
>>
>>> Thanks Clark for this great write-up. However, I think the solution to
>>> the
>>> problem in question is richer commands and better outpu
On 11 March 2014 12:20, Zane Bitter wrote:
>> Except nose can make them all the same file descriptor and let
>> everything multiplex together. Nose isn't demuxing arbitrary numbers
>> of file descriptors from arbitrary numbers of processes.
>
>
> Can't each subunit process do the same thing?
Rou
On Mon, Mar 10, 2014 at 4:20 PM, Zane Bitter wrote:
> On 10/03/14 16:04, Clark Boylan wrote:
>>
>> On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter wrote:
>>>
>>> Thanks Clark for this great write-up. However, I think the solution to
>>> the
>>> problem in question is richer commands and better outp
On 10/03/14 16:04, Clark Boylan wrote:
On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter wrote:
Thanks Clark for this great write-up. However, I think the solution to the
problem in question is richer commands and better output formatting, not
discarding information.
On 07/03/14 16:30, Clark Boyl
On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter wrote:
> Thanks Clark for this great write-up. However, I think the solution to the
> problem in question is richer commands and better output formatting, not
> discarding information.
>
>
> On 07/03/14 16:30, Clark Boylan wrote:
>>
>> But running test
On Mon, Mar 10, 2014 at 12:21 PM, John Dennis wrote:
> On 03/10/2014 02:31 PM, Zane Bitter wrote:
>> Fewer logs is hardly ever what you want when debugging a unit test.
>>
>> I think what John is looking for is a report at the end of each test run
>> that just lists the tests that failed instead o
On 03/10/2014 02:31 PM, Zane Bitter wrote:
> Fewer logs is hardly ever what you want when debugging a unit test.
>
> I think what John is looking for is a report at the end of each test run
> that just lists the tests that failed instead of all the details (like
> `testr failing --list`), or per
Thanks Clark for this great write-up. However, I think the solution to
the problem in question is richer commands and better output formatting,
not discarding information.
On 07/03/14 16:30, Clark Boylan wrote:
But running tests in parallel introduces some fun problems. Like where
do you send
On 03/07/2014 04:30 PM, Clark Boylan wrote:
> Now onto indirectly answering some of the questions you have. If a
> single unittest is producing thousands of lines of log output that is
> probably a bug. The test scope is too large or the logging is too
> verbose or both. To work around this we pro
On 03/07/2014 04:33 PM, Steve Kowalik wrote:
> On 07/03/14 12:56, John Dennis wrote:
>> Question: How do you list just the failing tests? I don't want to see
>> the contents of the logging data stored under the pythonlogging: key.
>> Ideally I'd like to see the name of the test, what the failure wa
On 07/03/14 12:56, John Dennis wrote:
Question: How do you list just the failing tests? I don't want to see
the contents of the logging data stored under the pythonlogging: key.
Ideally I'd like to see the name of the test, what the failure was, and
possibly the associated stacktrace. Should be s
On Fri, Mar 7, 2014 at 12:56 PM, John Dennis wrote:
> I've read the following documents as well as the doc for subunit and
> testtools but I'm still missing some big picture usage.
>
> https://wiki.openstack.org/wiki/Testr
> https://testrepository.readthedocs.org/en/latest/index.html
>
> The bigge
I've read the following documents as well as the doc for subunit and
testtools but I'm still missing some big picture usage.
https://wiki.openstack.org/wiki/Testr
https://testrepository.readthedocs.org/en/latest/index.html
The biggest problem seems to be whenever tests are listed I get
thousands
16 matches
Mail list logo
