78e167ab7b
The test relies on things ending up in the h2RequestsToSend container internally. For h2c we would have to use the http1 upgrade mechanism, and while I have not verified it, it seems to not reliably put enough requests in the container, and so the test is flaky for macos, which is the only platform where we use h2c. In CI at least. Fix it by forcing it by using h2 direct, which will work even on macOS without server-side ALPN. Pick-to: 6.7 6.5 6.2 Change-Id: I55816d400baa831524100f075e1b50fd3d9781a6 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io> Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> (cherry picked from commit 4e827e42e339a2774be26ba844bd5e87a14d83b5) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
README
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.