Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.0
-
None
-
210fd52e0d5e77105c676c064e7c3a69a00e2122 (qt/qtbase/5.14) c58ee54a707717b142f6e90cf48302884feb0b12 (qt/qtbase/5.14)
Description
On macOS 10.14 (clang-x86_64) I've seen repeated failures of
FAIL! : tst_QTcpSocket::bind(WithoutProxy:[::]:1) '!socket->bind(addr, port)' returned FALSE. () Loc: [../tst_qtcpsocket.cpp(619)] FAIL! : tst_PlatformSocketEngine::bind() '!binder.bind(QHostAddress::AnyIPv4, 82)' returned FALSE. () Loc: [tst_platformsocketengine.cpp(535)]
These are both Unix-only tests of low port numbers, which are normally privileged, so I presume the tests expect bind() to fail based on the test process not having the needed privilege to bind to these ports.
I've only seen this failure on dev, when testing a change before integration.
It's possible macOS 10.14 is new in dev and/or the Coin config for it uses a more privileged account than usual to run tests.
Attachments
Issue Links
- is required for
-
QTBUG-75786 macOS 10.14 autotest failures
- Closed
-
QTBUG-81053 Upgrade remaining single-UTF16-codepoint members of QLocaleData
- Closed
For Gerrit Dashboard: QTBUG-81905 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
289433,6 | Skip test cases that is failing on macOS >= 10.14 | dev | qt/qtbase | Status: MERGED | +2 | 0 |
289764,2 | Autotest: adapt to certain OSes always allowing binding to low ports | 5.14 | qt/qtbase | Status: MERGED | +2 | 0 |
291201,2 | That's potentially a demo for the recent failure to catch a broken test in CI | 5.14 | qt/qtbase | Status: ABANDONED | 0 | 0 |
291291,4 | tst_qtcpsocket::bind - amend the recent fix | 5.14 | qt/qtbase | Status: MERGED | +2 | 0 |