qt6-bb10

History

Thiago Macieira 1ed0dd88a3 QThread/Unix: make QThreadPrivate::finish() be called much later We need it to run after all the thread-local destructors have run, to ensure that some user code hasn't run after QThreadPrivate::finish() has finished. We achieve that by making it get called from a thread-local destructor itself, in the form of a qScopeGuard. This ought to have been done since C++11 thread_local with non-trivial destructors became available. However, it only started showing up after commit `4a93285b16` began using thread_local inside Qt itself. The visible symptom was that QThreadPrivate::finish() had already destroyed the thread's event dispatcher, but some user code ran later and expected it to still exist (or, worse, recreated it, via QEventLoop → QThreadData::ensureEventDispatcher). Fixes: QTBUG-117996 Pick-to: 6.7 Change-Id: I8f3ce163ccc5408cac39fffd178d682e5bfa6955 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>		2024-05-07 14:22:27 -07:00
..
auto	QThread/Unix: make QThreadPrivate::finish() be called much later	2024-05-07 14:22:27 -07:00
baseline	Fix test compilation issues with QtLite configuration	2024-05-06 14:29:02 +00:00
benchmarks	Fix test compilation issues with QtLite configuration	2024-05-06 14:29:02 +00:00
global	…
libfuzzer	Add CMYK support to QColorSpace	2024-04-12 21:53:54 +02:00
manual	Correct SPDX license tag	2024-05-03 14:04:52 +02:00
shared	Replace incorrect Metal config check in nativewindow.h	2024-05-01 14:24:06 +02:00
testserver	Add copyright and licensing to tools and utils files missing it	2024-05-03 10:58:54 +02:00
CMakeLists.txt	Rid of 'special case' markers	2023-04-13 18:30:58 +02:00
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.