I tried the former 0.13 version.
The format changed a bit and some support was not there.
So let us not think about the latter 6 events. But the first 4 events can be
found and are only present in some runs.
# for i in fatrace.log.*; do ./grepcheck $i; done
fatrace.log.4Y4sj : ....FFFFFF - 6 matches missing
fatrace.log.BmDhE : ....FFFFFF - 6 matches missing
fatrace.log.D3Q0R : .FF.FFFFFF - 8 matches missing
fatrace.log.dBKeg : ....FFFFFF - 6 matches missing
fatrace.log.DwbX5 : ....FFFFFF - 6 matches missing
fatrace.log.FfiSG : .FF.FFFFFF - 8 matches missing
fatrace.log.HZY4w : ....FFFFFF - 6 matches missing
fatrace.log.KQgf3 : ....FFFFFF - 6 matches missing
fatrace.log.kWx9y : ....FFFFFF - 6 matches missing
fatrace.log.lM669 : FFFFFFFFFF - 10 matches missing
fatrace.log.mYvpw : ....FFFFFF - 6 matches missing
fatrace.log.n78BL : ....FFFFFF - 6 matches missing
fatrace.log.qr7ll : ....FFFFFF - 6 matches missing
fatrace.log.rglRA : ....FFFFFF - 6 matches missing
fatrace.log.s3gPp : ....FFFFFF - 6 matches missing
fatrace.log.sktJy : ....FFFFFF - 6 matches missing
This leads to the assumption that this never worked better, but now is catched.
How can this test well in Debian CI as I can reproduce in Debian just as well?
The answer - just as Brian pointed out initially - still seems to be:
checking log...
skipping FAN_REPORT_FID tests, not available on this kernel
It will most likely hit Debian once the kernel in the test env gets bumped.
--
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/fatrace/+bug/1885188/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
