Add initial parts of automated compatibility tests #129
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 uutils#128 Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>
Codecov Report
@@ Coverage Diff @@
## main #129 +/- ##
=======================================
Coverage 49.80% 49.80%
=======================================
Files 19 19
Lines 2594 2594
Branches 702 702
=======================================
Hits 1292 1292
Misses 1046 1046
Partials 256 256 Continue to review full report at Codecov.
|
|
This is terrific, thanks :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Like the commit message mentions, this is the first half of the changes, because the second half needs already-built artifacts available. i.e., this needs to be merged first, then once CI passes, the second PR can be created and merged in.
I have tested these changes in a fork, you can see the results here:
-printin this one)I presume with this out of the way, I'll begin to see some of the open PRs merged? 😉 (Worth noting that, combining the current PRs with some offline work I have for
-L, the amount of passing tests for BFS's suite goes up from the current 98 to 109!)