Add runtime testing harness #48
Merged
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
SamTebbs33
commented
Jul 1, 2019
SamTebbs33
force-pushed
the
feature/runtime-testing
branch
from
c3e8a3b
to
efda008
Compare
SamTebbs33
force-pushed
the
feature/runtime-testing
branch
from
efda008
to
145ae6b
Compare
Thanks! I addressed my comments and moved |
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 patch adds a python script that acts as a runtime testing harness (test/rt-test.py), a new parameter to
zig build, as well as some extra log messages for proper testing. The test harness script imports the arch-specific rt testing script from its arch directory.It is recommended to run pkill on the qemu process after doing the testing as the process doesn't seem to be killed all the time:
zig build test -Drt-test=true; pkill qemu-system-i38.I would like to extend this to do more rigorous testing with more log statements once I find out how to tell the difference between an rt-test build and normal build from within the source, as adding more logging from a normal build would only pollute things.
Closes #12