| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
| |
After a change Brad did to the event dispatcher we are no longer
guaranteed that processEvents will process *all* events in the event
queue. (most of the time _it_will_ process all events)
I only replaced processEvents for the tests that fail.
|
| |
|
|
|
|
|
|
| |
As indicated by the comments, if the test fails, the timeouts may need
to be increased. Since this is failing on the test cluster, where CPU
time is limited, doubling the timeouts seems to do the trick.
Reviewed-by: Richard Moe Gustavsen
|
| | |
|
| |
|
|
|
|
| |
for the Q3Table one, it sometimes fail with XPASS.
There is no point trying to stabilize a failure on a test for a class
we are not likely to touch anyway.
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
|
| |
By using QTRY_{COMPARE,VERIFY} instead of waiting an arbitrary amount of
time waiting for the window manager to do his job.
Also use QApplication::setActiveWindow which seems to be more robust
then QWidget::activateWindow
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
