[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: [kcoreaddons] autotests: Increase timeout in the hope of fixing test failure on the CI
From:       Milian Wolff <mail () milianw ! de>
Date:       2018-02-08 10:48:01
Message-ID: 27129098.gurLk1UTLm () milian-kdab2
[Download RAW message or body]

On Wednesday, February 7, 2018 11:36:06 PM CET David Faure wrote:
> On mardi 6 février 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'.
> > 
> > Increase timeout in the hope of fixing test failure on the CI
> > 
> > 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.
> 
> Does not help.
> 
> https://build.kde.org/view/Frameworks/job/Frameworks%20kcoreaddons%20kf5-qt5
> %20SUSEQt5.10/44/testReport/(root)/TestSuite/kdirwatch_qfswatch_unittest/
> 
> 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 
amount of files in both cases, so I doubt it's timing related. Maybe we run 
out of watchers or something like that on the CI? Some kernel configuration?

Bye

-- 
Milian Wolff
mail@milianw.de
http://milianw.de


[prev in list] [next in list] [prev in thread] [next in thread]