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
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:'': {{{
part.
Yes,
On Mon, Mar 10, 2014 at 7:20 PM, Zane Bitter zbit...@redhat.com wrote:
On 10/03/14 16:04, Clark Boylan wrote:
On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter zbit...@redhat.com wrote:
Thanks Clark for this great write-up. However, I think the solution to
the
problem in question is richer
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/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 perhaps
On Mon, Mar 10, 2014 at 12:21 PM, John Dennis jden...@redhat.com 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
On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter zbit...@redhat.com 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
On 10/03/14 16:04, Clark Boylan wrote:
On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter zbit...@redhat.com 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
On Mon, Mar 10, 2014 at 4:20 PM, Zane Bitter zbit...@redhat.com wrote:
On 10/03/14 16:04, Clark Boylan wrote:
On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter zbit...@redhat.com wrote:
Thanks Clark for this great write-up. However, I think the solution to
the
problem in question is richer
On 11 March 2014 12:20, Zane Bitter zbit...@redhat.com 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
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
On Fri, Mar 7, 2014 at 12:56 PM, John Dennis jden...@redhat.com 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
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
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 was, and
14 matches
Mail list logo
