Daniel Kahn Gillmor wrote on 13.04.2020 19:12: > Hi Enigmail folks-- > > https://bugs.debian.org/954268 indicates that when the Internet > connection is flakey, enigmail's tests can sometimes fail or timeout in > unreliable ways. > > It would be great if we could update the tests so that they could cope > with an unreliable network. > > If anyone wants to suggest a simple way to do that, i could take a stab > at writing a patch, but i'm not sure where to begin.
The test suite only needs a network to download Thunderbird and and the required Debian packages. There is no network access required for running any test; in particular, the test suite contains no request to any keyserver or similar. You mentioned the following line in the log: > 2020-02-26 18:05:54.188 [DEBUG] keyRefreshService.jsm: Either no keyservers exist or the protocols specified are invalid. Will recheck in an hour. This has nothing to do with network access from the test suite. The correct interpretation of such Debug log entries is the following: The test suite is running so long that the usual key refresh service is becoming active. However, there is no valid configured keyserver, thus the service doesn't do anything. It will retry in an hour to see if there is a configured keyserver. I checked the log file, and I believe that the problem is in the infrastructure. There are error messages from GnuPG that I would expect under normal circumstances. The first suspicious log entry is this one: 2020-02-26 17:05:06.247 All of a sudden, GnuPG cannot access pubring.kbx anymore, and thus the test fail. I assume that some test cases don't foresee such errors and get stuck. HTH -Patrick
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
