On Wednesday, February 7, 2018 11:36:06 PM CET David Faure wrote:
> On mardi 6 f=E9vrier 2018 10:37:12 CET Milian Wolff wrote:
> > Git commit 2cf36358fb40ae4d1c2945d28db8b4b9dc9426bd by Milian Wolff.
> > Committed on 06/02/2018 at 09:35.
> > Pushed by mwolff into branch 'master'.
> >=20
> > Increase timeout in the hope of fixing test failure on the CI
> >=20
> > The benchmark works fine for me on my local machine, but on the
> > CI the QFileSystemWatcher based benchmark fails. I suspect that
> > it is due to a timing issue. Let's see if that hunch is correct
> > by increasing the timeout.
>=20
> Does not help.
>=20
> https://build.kde.org/view/Frameworks/job/Frameworks%20kcoreaddons%20kf5-=
qt5
> %20SUSEQt5.10/44/testReport/(root)/TestSuite/kdirwatch_qfswatch_unittest/
>=20
> I see that it also fails with the "stat" backend, but I guess we can just
> skip the benchmark for that backend, which is obviously slower, but it's
> only a fallback when all else fails (not sure it can even happen
> automatically anymore, one probably has to select it explicitly).

That is very odd. Do you have an idea why that may fail? It read the same=20
amount of files in both cases, so I doubt it's timing related. Maybe we run=
=20
out of watchers or something like that on the CI? Some kernel configuration?

Bye

=2D-=20
Milian Wolff
mail@milianw.de
http://milianw.de