8de1ed8979
Because we will do a small wait after the final connection (to see if there are any unexpected extra connections) we can save some time by reducing _how long_ we wait for it. In general we only need an extra long wait for the first connection, subsequent connections are faster. So we change the loop structure from looping until we hit 20(!) connections, when anything larger than 6 will fail the test anyway! And use qWaitFor instead of repeatedly calling enterLoop and checking the state of an ElapsedTimer, the total wait time is not super interesting, and made it a guarantee that the test would take 10 seconds. While we are here, update the attribute we use to test HTTP/2 connections. We were previously enabling http/2, but this is the new default so it's not needed. We do, however, need to enable h2c if we want to see it trying to upgrade to http/2 over cleartext. Not a big issue, so we don't pick it very far back. Pick-to: 6.7 Change-Id: Ia314ae2827ab8a8baaa4af2c5136c5e531bcb1f8 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> |
||
|---|---|---|
| .. | ||
| access | ||
| kernel | ||
| selftest | ||
| socket | ||
| ssl | ||
| CMakeLists.txt | ||