qt/qtbase.git - Qt Base (Core, Gui, Widgets, Network, ...)

	Commit message (Collapse)	Author	Age	Files	Lines
*	Extend blacklisting of tst_QSemaphore	Tony Sarajärvi	2017-05-31	1	-0/+1
\| \| \| \| \| \| \| \| \|	tryAcquireWithTimeout(0.2s) was already blacklisted and now the same failed with "(2s)". Task-number: QTBUG-58745 Change-Id: I82363238c08056d2969a7616e3a6e5af080d537d Reviewed-by: Liang Qi <liang.qi@qt.io>
*	Blacklist tst_qsemaphore on macOS 10.12	Tony Sarajärvi	2017-04-24	1	-0/+1
\| \| \| \| \| \|	Task-number: QTBUG-58745 Change-Id: I085a2ac60cc24c287140788a88512657238a2c4b Reviewed-by: Liang Qi <liang.qi@qt.io>
*	Blacklist also tst_QSemaphore::tryAcquireWithTimeout(2s)	Marc Mutz	2017-03-17	1	-0/+2
\| \| \| \| \| \| \| \|	It has started failing recently on the CI, too. Task-number: QTBUG-58745 Change-Id: I4c8834917e6455d00c300549ed448b06da75d5bc Reviewed-by: Rafael Roquetto <rafael.roquetto@kdab.com>
*	Blacklist tst_QSemaphore::tryAcquireWithTimeout(0.2s) on Windows	Marc Mutz	2017-02-10	1	-0/+2
\| \| \| \| \| \| \| \| \|	This test was determined to be flaky on the CI, depite attempts to stabilize it (b750a3786f42395f0cddd8ed8f92a2bcfda1b270). Task-number: QTBUG-58745 Change-Id: I933199cd537002699906147d172bb797f1dc90c1 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
*	Lower timeout on tst_QSemaphore::tryAcquireWithTimeout	Allan Sandfeld Jensen	2016-12-14	1	-3/+0
\| \| \| \| \| \| \| \|	The test was so slow it was blacklisted on all platforms for timing out. This patch lowers the timeout to a 5th and tries removing the blacklist. Change-Id: Ib28b21de572517c548a14300f26815598efe91e2 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
*	Blacklist tryAcquireWithTimeout	Simon Hausmann	2015-06-20	1	-1/+1
\| \| \| \| \| \| \|	All variants of the tests are timing out randomly on all platforms :( Change-Id: I9244602a8d06fd07d3cc99b2fb8fdf6e07e92cf2 Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>
*	Blacklist and skip various tests that are flakey	Simon Hausmann	2015-06-14	1	-0/+3
	They didn't show up in the "old" CI runs because they usually pass the second time they are executed - which the testrunner does. The new CI doesn't do that anymore, instead we now mark those tests explicitly and will track their record of passing and failing in the new metrics database. Change-Id: Id34dd6f792f38995b07b6fec88f833df64de2f8b Reviewed-by: Lars Knoll <lars.knoll@digia.com>