tests/rng-op-key extrmely slow on the MinGW runners
The MinGW runners "hang" at tests/rng-op-key
for 20+ minutes.
Maybe the underlying random generator waits for events/entropy !?
Looks like gnutls_rnd()
needs a timeout value...
The MinGW runners "hang" at tests/rng-op-key
for 20+ minutes.
Maybe the underlying random generator waits for events/entropy !?
Looks like gnutls_rnd()
needs a timeout value...
I noticed it too, though these are not new tests, and the mingw runners were much faster than their current speed. We may be seeing the same MR so hopefully it is a glitch. If it persists we should check whether we can make this test faster (e.g., less iterations but still test what it is supposed to test). btw. yes it calls the random generator but it shouldn't be waiting for entropy... said that, I think there was a recent MR changing the API used by the random generator in windows...
No, the commit I had in mind was: !840 (cbedd86c)
and was not merged, so it is not that.
added 3_6_x label
changed milestone to %Release of GnuTLS 3.6.6
mentioned in issue #674
changed milestone to %Release of GnuTLS 3.6.7
added need information label
Last win32 builds are 30 and 28 minutes: https://gitlab.com/gnutls/gnutls/-/jobs/174790020 https://gitlab.com/gnutls/gnutls/-/jobs/174790019
should we close this?
removed milestone
I agree, looks good now.
closed