qt5base-lts/tests/auto/concurrent
Jędrzej Nowacki 3760120ab3 Remove tst_qtconcurrentiteratekernel blockSize test
The test is just wrong.

It suggests, that it tests minimal block size,
but in reality it is checking if a maximal peak of block size
is bigger then expected minimum block size.

The minimal block size is 1, not 1024 / ideal threads count and
it is defined in BlockSizeManagerV2.

The maximal block size is defined and it is fixed, but it is an
implementation detail, probably not worth testing.

The test is based on a race condition as peakBegin and
peakBlockSize are modified in parallel from multiple threads,
without any synchronization.

Change-Id: I430eedcf83b0fa3e2ce2cfd294eaee7b301e48ae
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-07-29 09:35:16 +00:00
..
qtconcurrentfilter Updated license headers 2016-01-21 18:55:18 +00:00
qtconcurrentiteratekernel Remove tst_qtconcurrentiteratekernel blockSize test 2017-07-29 09:35:16 +00:00
qtconcurrentmap Adapt to the C++ SIC introduced by P0012: noexcept overloading 2017-02-17 13:57:30 +00:00
qtconcurrentmedian Updated license headers 2016-01-21 18:55:18 +00:00
qtconcurrentrun Adapt to the C++ SIC introduced by P0012: noexcept overloading 2017-02-17 13:57:30 +00:00
qtconcurrentthreadengine Updated license headers 2016-01-21 18:55:18 +00:00
concurrent.pro QtConcurrent: Workaround GCC bug 58800 in median calculation 2013-12-03 11:45:18 +01:00