On 23 September 2017 at 17:37, Zev Weiss <zev at bewilderbeest.net> wrote: [....]> And now I'm not able to reproduce the failure at all, with or without that > patch. Not sure what could possibly be different (same git commit, same > terminal session/environment, same 'make' command), but repeated attempts > have been fruitlessYou didn't happen to upgrade OpenSSL since then?> -- now test_kex gets "352 tests ok" every time (after > printing a bunch of ENOENT warnings on /usr/local/etc/moduli).Unfortunately the tests can't work around those warnings but you can copy the moduli file into /usr/local/etc/moduli if they bug you (this problem goes away as soon as you "make install" the first time with those file paths. -- Darren Tucker (dtucker at zip.com.au) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new) Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
On Sun, 24 Sep 2017, Darren Tucker wrote:> On 23 September 2017 at 17:37, Zev Weiss <zev at bewilderbeest.net> wrote: > [....] > > And now I'm not able to reproduce the failure at all, with or without that > > patch. Not sure what could possibly be different (same git commit, same > > terminal session/environment, same 'make' command), but repeated attempts > > have been fruitless > > You didn't happen to upgrade OpenSSL since then?Or, if you were updating an existing tree e.g. using git, forget to "make clean"? -d
On Sun, Sep 24, 2017 at 12:58:20AM CDT, Damien Miller wrote:>On Sun, 24 Sep 2017, Darren Tucker wrote: > >> On 23 September 2017 at 17:37, Zev Weiss <zev at bewilderbeest.net> wrote: >> [....] >> > And now I'm not able to reproduce the failure at all, with or without that >> > patch. Not sure what could possibly be different (same git commit, same >> > terminal session/environment, same 'make' command), but repeated attempts >> > have been fruitless >> >> You didn't happen to upgrade OpenSSL since then? > >Or, if you were updating an existing tree e.g. using git, forget to >"make clean"? >Nope, no OpenSSL/LibreSSL updates, and yes, did a 'make clean' (and a 'git clean -xdf', even); still unable to reproduce it. Zev