Randall S. Becker

More info The 75-test_quicapi.t test fails as follows: ``` # Subtest: ../../test/quicapitest 1..21 # Subtest: test_quic_write_read 1..3 ok 1 - iteration 1 # ERROR: (bool) 'globserverret == true' failed @...

To confirm, yes, this is PUT, not KLT. I won't have a production KLT for some time. I will have to update that in my fork - so that I...

This is what I got from `quicapitest`: ``` # Subtest: ../../test/quicapitest 1..21 # Subtest: test_quic_write_read 1..3 ok 1 - iteration 1 # INFO: @ /home/jenkinsbuild/.jenkins/workspace/OpenSSL-3.4_Monitor/test/helpers/quictestlib.c:427 # globserverret = 0x0 at...

For test_threads, I am suspecting that we end up with a number overflow after a hard loop. The iteration count is huge, and I think blows up at INT_MAX.

Thread tests are now looping forever and never finishing in PUT. No longer hitting INT_MAX on counter. Worse, not better.

> what changed? Or is this just changing from run to run with the same build? I really don't know. I'm trying to figure that out. One thing is that...

> can you try build this branch: https://github.com/nhorman/openssl/tree/lock_trace and run the following: > > ``` > make TESTS=test_threads V=1 OPENSSL_TRACE=LOCK test > ``` > > capturing the output (warning, it...

Even more confused... ``` 90-test_threads.t .. # The results of this test will end up in test-runs/test_threads 1..3 # Subtest: ../../test/threadstest 1..15 ok 1 - test_multi_default ok 2 - test_lock...

Did OPENSSL_THREADS get added at some point recently?

I just put enable["threads"] in the configuration. Have not seen OPENSSL_THREADS in any other config. Presumably it is derived from something.