Public bug reported: fatrace version 0.15-1 is stuck in groovy-proposed because the "file renaming" test in fatrace-currentmount is failing. This is reproducable using a qemu virtualization server.
The package passed Debian ci because the test was skipped as it was run on a 4.19 kernel which doesn't support directory events. On Ubuntu a 5.04 kernel was used and so the test was ran and it failed. Complete logs are here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/amd64/f/fatrace/20200501_155154_7ae8a@/log.gz The relevant excerpt is: checking log... ^mv(.*): <> /tmp/autopkgtest.TV550j/build.0mf/src not found in log: Looking at the log file I didn't actually see any events relating to test.txt.2 or any lines containing "<>". ** Affects: fatrace (Ubuntu) Importance: Undecided Status: New ** Tags: groovy update-excuse ** Tags added: groovy update-excuse -- 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
