On 27/07/2020 07:25, Bernhard Voelker wrote:
On openSUSE's build system, I sometimes see a test failure from the
above test on x86_64. Trying again usually makes the test pass.
I'm not sure if we have a race in the test, but the result looks identical as if
tail(1) would have been started with the (test-only) option ---disable-inotify
(thus not being able to "revert to polling" as it started in this mode).
Any idea?
Well it doesn't even print the message:
"tail: 'dir/file' has become inaccessible: No such file or directory"
which should happen in any mode.
I can't see where the issue is TBH.
All I can suggest is to change --max-unchanged-stats and --sleep-interval
in an attempt to make it more reproducible.
cheers,
Pádraig
