The way the test works it collects data for 2 seconds and then expects
everything to be there.
That isn't sufficient in any case where the I/O takes longer than two seconds
which can for many reasons happen (e.g. disk spindown, cpu overload, ...).
Note: also one of the 2 seconds is already the "sleep 1" that tries to
allow the process to start.
I started to make it slower and throw in sync's - just to be on the very safe
side.
Like:
--- a/tests/fatrace-currentmount
+++ b/tests/fatrace-currentmount
@@ -3,8 +3,8 @@ set -euC
LOG="$AUTOPKGTEST_TMP/fatrace.log"
echo "starting fatrace..."
-fatrace --current-mount -s 2 -o $LOG &
-sleep 1
+fatrace --current-mount -s 40 -o $LOG &
+sleep 20
echo "read a file..."
head NEWS > /dev/null
@@ -24,9 +24,11 @@ mkdir dest
mv "${TEST_FILE}.2" dest/"${TEST_FILE}.2"
rm dest/"${TEST_FILE}.2"
rmdir dest
+sync
echo "waiting for fatrace..."
wait
+sync
echo "checking log..."
check_log() {
This didn't fix it either - so it is not just late-start or early-exit
--
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
