On 2016-11-30 23:59:32, Guido Günther wrote:
> Hi Antoine,
> On Wed, Nov 30, 2016 at 11:03:39PM -0500, Antoine Beaupré wrote:
>> On 2016-11-30 16:46:17, Ola Lundqvist wrote:
>> > Hi
>> > There were no test suite before the update so I could not tell if it was a
>> > regression or not.
>> I just figured out how to hook up the test suite, and it fails:
> (Posting this here again since I'm not sure everybody working on nss in
> LTS is aware of it):
> We have patches to enable it during the build here:
Sigh... I missed that in my research. I ended up with a similar patch
> There's also more stuff like some minimal autopkgtests here:
>> Tests summary:
>> Passed: 8282
>> Failed: 17
>> Failed with core: 0
>> ASan failures: 0
>> Unknown status: 0
>> It takes a looong time to run here. I thought it was in a loop for a
>> while there.
>> I am not sure what to do next here - maybe I could test against the pre
>> 3.26 version from wheezy and see if the tests fail similarly...
> Do we really intend to track nss upstream from now on:
> I remember the nss testsuite to run cleanly last time I checked a couple
> of months ago so we should IMHO investigate.
Okay. One problem with the test suite is that it generates so much
output that it's basically impossible to see what the failure *was* -
I'll need to log all this and run the test suite again...
Twenty years from now you will be more disappointed by the things that
you didn't do than by the ones you did do. So throw off the bowlines.
Sail away from the safe harbor. Catch the trade winds in your sails.
Explore. Dream. Discover. - Mark Twain