Generate Test Report for wasm test cases #103
Merged
+642
−0
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
ansalma6
requested review from
m-hemmings,
rennergade,
yashaswi2000 and
Yaxuan-w
|
Off the bat the PR should be named something more clear, and it probably shouldnt have your name in it. (The branch name should be better as well but thats fine for now). |
ansalma6
changed the title
Yaxuan-w
requested changes
Feb 7, 2025
|
@m-hemmings and @yashaswi2000 can you review this today? |
m-hemmings
reviewed
Feb 11, 2025
Yaxuan-w
requested changes
Feb 12, 2025
ansalma6
force-pushed
the
ansal_test_report_script
branch
from
f931cc8 to
4d2c133
Compare
rennergade
approved these changes
Feb 21, 2025
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.
PR for the python script that generates the test report.
We take all the files with .c extension. Test cases are considered deterministic or non deterministic by checking the parent folder name.
For determinstic tests, we compile and run using gcc, stores the output and then compiles using wasm and stores the output after running. The outputs are compared and is success if they match.
For non deterministic tests, we compile and using wasm only
All wasm compilations and runs are done using the lindtool.sh bash script
Finally a JSON file is generated with determinstic and non-deterministic as childs and each having the counts/lists of success/failure/timeout/segfaults and a list of all files and what their result was.