Mirv suggested that https://launchpadlibrarian.net/218473113/qtbase-
opensource-src_5.4.1%2Bdfsg-2ubuntu8_5.4.1%2Bdfsg-2ubuntu9.diff.gz could
very well be when the test started failing, and it looks plausible. Not
sure what conclusions to draw from the diff though. Is the issue in the
way the test server handles incoming connections, or is it an actual bug
in QNAM?
In doubt, I’ll mark qtbase-opensource-src also affected, for further
investigation.
** Also affects: qtbase-opensource-src (Ubuntu)
Importance: Undecided
Status: New
** Changed in: webbrowser-app (Ubuntu)
Status: In Progress => Confirmed
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1498539
Title:
FaviconFetcherTests random failures in silo builds
Status in qtbase-opensource-src package in Ubuntu:
New
Status in webbrowser-app package in Ubuntu:
Triaged
Bug description:
Since yesterday (2015-09-21), FaviconFetcherTests started failing at
random in silo builds (not failing all the time, but in about 75% of
the builds, on amd64 and i386, not on armhf).
Since it has been happening in several silos, it’s very unlikely that
it’s a change in webbrowser-app itself that triggered the failure.
It’s more likely a change somewhere else in the stack that triggered a
bug that was already there.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1498539/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
