UpdateHub / updatehub / 32296078407

70%

push

github

test: fs: stop the disk space test racing with the filesystem

`a_requirement_beyond_the_available_space_is_rejected` read the free space, then
handed the very same number to `ensure_disk_space`, which reads it again. Any
other writer on that filesystem moves the second reading, and the boundary case
the test was pinned to then falls on the wrong side.

It failed exactly that way in the coverage step of
https://github.com/UpdateHub/updatehub/actions/runs/32294740390, with `available:
80615378944, required: 80615387136`: 8 KiB vanished while the two readings ran,
because `cargo llvm-cov` has the parallel tests writing .profraw files the whole
time.

Step back from the boundary on both sides. Half of the free space stays available
however busy the disk gets, and no filesystem answers with `u64::MAX`, so the
rejection no longer depends on what the second reading finds.

2 of 2 new or added lines in 1 file covered. (100.0%)

3261 of 5239 relevant lines covered (62.24%)

951.75 hits per line