Add regression testing based on decomp.me scratches#66
Open
violetbrownie wants to merge 7 commits intodecompals:mainfrom
Open
Add regression testing based on decomp.me scratches#66violetbrownie wants to merge 7 commits intodecompals:mainfrom
violetbrownie wants to merge 7 commits intodecompals:mainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
because what good is writing a program if you don't put it through the twelve labours of hercules?
This PR implements regressions tests against all the compilers decomp.me uses wibo to run. It pulls in a static bank of decomp.me scratches (hosted here for the moment), runs the current wibo build against all of them, and compares the output assembly to ground-truth compilations generated with wine.
This PR only directly adds a new CI workflow that pulls in and calls the repo above - most of the new methodology and explanations of are located there.
the new tests are failing for the moment - this seems to be the same bug recorded in #62