Some experimentation revealed that it is flaky and that this might just
be the first event missing on a racy event gathering job.

I was running it in a loop (on a x86 autopkgtest VM) and after some
initial tests and 200 iterations is seems like it is ~18% good in regard
to the "mv <>" event.

But if we look further sometimes other events come up in the error report, like:
^touch.* C\?W\?O /tmp/autopkgtest.cWRPFV/build.Y7S/src/test.txt not found in 
log:
^mkdir(.*): + /tmp/autopkgtest.cWRPFV/build.Y7S/src$ not found in log:
...


So it is not limited to the rename event, maybe the buffer got slower or 
asynchronous?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885188

Title:
  fatrace autopkgtest failure due to rename test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fatrace/+bug/1885188/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to