qt5base-lts

History

Olivier Goffart b52b509ae4 QLockFile: Don't deadlock if the lock file has a mtime in the future Stale Lock files in the future can happen in some situations. For exemple two computers with different clocks access the same file system. It could be that one of the timestamp is totaly off (several years into the future). [ChangeLog][QtCore][QLockFile] Fixed a deadlock occurring if a corrupted lock file's modification time is in the future. Change-Id: I8dac98a0e898c76bcef67f8c195e126c996b6add Reviewed-by: David Faure <david.faure@kdab.com>		2017-03-10 17:09:24 +00:00
..
auto	QLockFile: Don't deadlock if the lock file has a mtime in the future	2017-03-10 17:09:24 +00:00
baselineserver	Properly use the "process" feature	2017-02-27 15:44:46 +00:00
benchmarks	Properly use the "process" feature	2017-02-27 15:44:46 +00:00
global
manual	use regular configure mechanism for openssl library references	2017-02-22 07:45:59 +00:00
shared	Windows CE cleanup.	2016-04-14 12:45:56 +00:00
README
tests.pro	Use qtConfig throughout in qtbase	2016-08-19 04:28:05 +00:00

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.