On 01/04/15 11:47, John Meinel wrote:
I've been noticing lately that everytime a test fails it ends up
having a *lot* of lines about failing to find simplestreams headers.
(this last test failure had about 200 long lines of that, and only 6
lines of actual failure message that was useful).
make them trace
On Wed, Apr 1, 2015 at 6:47 AM, John Meinel j...@arbash-meinel.com wrote:
I've been noticing lately that everytime a test fails it ends up having a
*lot* of lines about failing to find simplestreams headers. (this last test
failure had about 200 long lines of that, and only 6
+1000
On Wed, Apr 1, 2015 at 11:47 AM, John Meinel j...@arbash-meinel.com wrote:
I've been noticing lately that everytime a test fails it ends up having a
*lot* of lines about failing to find simplestreams headers. (this last test
failure had about 200 long lines of that, and only 6 lines of
Any idea why the test would be doing 9 lookups?
John
=:-
On Wed, Apr 1, 2015 at 3:14 PM, Ian Booth ian.bo...@canonical.com wrote:
TL;DR:
A lot of the spam is necessary to diagnose when simplestreams look up
fails, or
you get the wrong tools. In such cases, it's extremely useful to see
TL;DR:
A lot of the spam is necessary to diagnose when simplestreams look up fails, or
you get the wrong tools. In such cases, it's extremely useful to see where the
search path has looked. This was especially the case in the early days when
published tools and associated metadata sometimes were
