Re: [OE-core] [PATCH 2/3] yocto-compat-layer: limit report of signature changes

2017-04-07 Thread Patrick Ohly
On Fri, 2017-04-07 at 08:38 +1200, Paul Eggleton wrote: > On Thursday, 6 April 2017 1:36:05 AM NZST you wrote: > >AssertionError: False is not true : Layer meta- changed 120 > > signatures, initial differences (first hash without, second with layer): > > BTW, rather than

Re: [OE-core] [PATCH 2/3] yocto-compat-layer: limit report of signature changes

2017-04-06 Thread Paul Eggleton
On Thursday, 6 April 2017 1:36:05 AM NZST you wrote: >AssertionError: False is not true : Layer meta- changed 120 > signatures, initial differences (first hash without, second with layer): BTW, rather than self.assertTrue(False, ... ) you can just use self.fail(...) and then you avoid

[OE-core] [PATCH 2/3] yocto-compat-layer: limit report of signature changes

2017-04-05 Thread Patrick Ohly
Typically a single change cascades through the entire task dependency chain. Developers had to figure that out themselves, based on hard to read and interpret output (not sorted, no indention, no explanations): $ yocto-compat-layer.py -n meta- ... AssertionError: True is not false :