Repository navigation
fastf 3.19.1: the AUR build's own tests no longer fail at random
Building fast-folder from source runs fastf's test suite (check() in the
AUR package). Three of those tests could fail on a busy machine for reasons
that had nothing to do with fastf. When one did, paru fast-folder stopped
with A failure occurred in check(), and running it again usually worked.
Each of those tests started a program, a fake shell or a lock, while other
tests were starting programs of their own. For a moment, a program another
test was starting could still hold the file this test needed. The tests now
work in a way that does not depend on that timing. On this machine they
failed about once in every thirteen runs before the fix and passed 90 runs
in a row after it.
fastf itself is unchanged from 3.19.0. Its release notes cover $, your
shell in the project folder.
What's Changed
- fastf 3.19.1: three unit tests no longer race the processes other tests start by @cristocola in #135
Full Changelog: v3.19.0...v3.19.1
