Hi, I revisited this today and it still is present. I tried 0.15 (groovy-proposed) and 0.13 (groovy-release) against the current test of 0.15 and they both failed the same way. So it really is the new test that seemed broken.
But then I looked deeper and it seems worse than I thought. [1] has detailed steps on how I got there, but the TL;DR is that it misses random events in a non reliable way. I've had the test (already extended -s parameter and the following sleep to ensure it is no late start or early exit) running in a loop a few times and modified the log checking to report which matches are found and which are missing. fatrace.log.7XZ3Ief : ...F...F.F - 3 matches missing fatrace.log.DHuzcGX : ....F..... - 1 matches missing fatrace.log.DtQWtxF : ......FF.. - 2 matches missing fatrace.log.IPN1ZZX : ...F...F.F - 3 matches missing fatrace.log.JmcGCpx : .......... - 0 matches missing fatrace.log.K06ToCE : .......... - 0 matches missing fatrace.log.KSdRSG8 : .......F.. - 1 matches missing fatrace.log.NepBJN8 : .......F.. - 1 matches missing fatrace.log.OiECdoh : ......FF.F - 3 matches missing fatrace.log.TydkhKd : .......... - 0 matches missing fatrace.log.UV22acQ : .......F.. - 1 matches missing fatrace.log.UxzxTRb : ....F..... - 1 matches missing fatrace.log.VApdiDa : ......FF.F - 3 matches missing fatrace.log.Y8rSY2G : .......... - 0 matches missing fatrace.log.ehxRpk7 : .......F.. - 1 matches missing fatrace.log.k8NBKKk : ....F..F.. - 2 matches missing fatrace.log.kLmSHVi : ...FF.F.FF - 5 matches missing fatrace.log.kb4wV7v : ...FF..... - 2 matches missing fatrace.log.nsbCDTm : ......FF.. - 2 matches missing fatrace.log.oR5UZ58 : ......FF.. - 2 matches missing fatrace.log.qACUHvY : ....F.FF.. - 3 matches missing fatrace.log.rxWTYs5 : ....F...FF - 3 matches missing fatrace.log.rxrJBZl : .......... - 0 matches missing fatrace.log.uCDFrK1 : .......F.. - 1 matches missing fatrace.log.uTSKJQF : .......F.. - 1 matches missing fatrace.log.wNQsl8z : .FF..FFF.. - 5 matches missing fatrace.log.zT5gLQF : .......F.. - 1 matches missing This indicates that we miss a random set of events, sometimes none sometimes half of them. I know that events might be lost if the event queue is full, but on this system not a lot is going on. I'm puzzled, does that make any sense to you? [1]: https://bugs.launchpad.net/ubuntu/+source/fatrace/+bug/1885188 -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd
