45d87f7bab
The test requires allocating 4GB of memory to handle a big file. On a 32b architecture, this leads to a std::bad_alloc exception and abort in result (tested on VxWorks 24.03 on an imx6 board). Because of that, the test can't work properly and it can't be blacklisted. Work around the issue by skipping the test. Pick-to: 6.7 Task-number: QTBUG-115777 Change-Id: I46002a27aed09706cd61d2e2c8d4bd1e12a16c36 Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io> (cherry picked from commit 4d2744e4345193cdf7ec2bbf06b0a0d169827d8b) 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.