By default, artifacts are only downloaded from the latest successful
workflow, meaning that, if the compat tests regressed, then it is
impossible to compare against the new current state. This isn't a
perfect solution, but I believe it should by far be "good enough" for
these purposes.
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>
This adds support for -regextype, -regex, and -iregex, using Oniguruma
to implement support for the Emacs, grep, POSIX basic, and POSIX
extended regex types.
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>
This adds the rest of the compatibility test workflow, in order to
automatically run against the GNU findutils & BFS test suites as part of
standard CI and compare the results to the latest from the 'main'
branch.
Closes#128
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>
This is the first half of the needed changes to set up automated
compatibility tests against GNU findutils and bfs, handling the uploads
of the build logs and JSON results. The workflow itself is heavily based
on the one from uutils/coreutils:
https://github.com/uutils/coreutils/blob/main/.github/workflows/GnuTests.yml
but with various cleanups & tweaks to better suit findutils.
This does *not* include the actual regression comparisons, because those
will only pass once archives of these files are up on the main branch.
Ref #128
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>