qt6-bb10/tests/auto/network/access/qnetworkreply
Mårten Nordheim 0592369df4 tst_qnetworkreply: stabilize and unblacklist getFromHttpIntoBuffer2
The test in general is fine, but it was making an assumption that the
first 5 readyRead emissions would never result in the whole message
being received. In certain scenarios with slowdown however it was still
possible that we would receive the whole message after just a few
readyReady emissions. While I didn't check it's most likely due to a
mechanic in the QNetworkReply machinery where we suppress some
emissions if we know there's more data just about to be available.

Task-number: QTBUG-88943
Change-Id: I0cf06edb34d4e86cc8a42c0f1cd7e8c35765f6ee
Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>
2020-12-04 00:17:46 +01:00
..
certs Merge remote-tracking branch 'origin/5.12' into 5.13 2019-06-25 15:47:42 +02:00
echo CMake: Regenerate projects to use new qt_internal_ API 2020-09-23 16:59:06 +02:00
test CMake: Regenerate projects to use new qt_internal_ API 2020-09-23 16:59:06 +02:00
.gitattributes
.gitignore
BLACKLIST tst_qnetworkreply: stabilize and unblacklist getFromHttpIntoBuffer2 2020-12-04 00:17:46 +01:00
CMakeLists.txt Remove winrt 2020-06-06 20:25:49 +02:00
bigfile
element.xml
empty
image1.jpg
image2.jpg
image3.jpg
index.html
qnetworkreply.pro Remove winrt 2020-06-06 20:25:49 +02:00
qnetworkreply.qrc
resource
rfc3252.txt
smb-file.txt
testserver_index.html
tst_qnetworkreply.cpp tst_qnetworkreply: stabilize and unblacklist getFromHttpIntoBuffer2 2020-12-04 00:17:46 +01:00