-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve CI #281
base: main
Are you sure you want to change the base?
Improve CI #281
Conversation
f2c7c2b
to
accf52f
Compare
Is there any reason to maintain |
It is purely for debugging purposes. It tests memory arguments for operations. We can close the bug (or reduce tests) if it is not necessary. Especially if it increases the CI time. |
@@ -89,8 +89,10 @@ jobs: | |||
rm $GITHUB_WORKSPACE/test/wasm-spec/core/call_indirect.wast | |||
$RUNNER --engine="$GITHUB_WORKSPACE/out/clang/x86/walrus" | |||
$RUNNER --jit --engine="$GITHUB_WORKSPACE/out/clang/x64/walrus" | |||
$RUNNER --jit --engine="$GITHUB_WORKSPACE/out/pure/x86/walrus" basic-tests wasm-test-core jit | |||
$RUNNER --no-reg-alloc --engine="$GITHUB_WORKSPACE/out/clang/x64/walrus" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
--no-reg-alloc
also enables --jit
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
$RUNNER --jit --engine="$GITHUB_WORKSPACE/out/pure/x86/walrus" basic-tests wasm-test-core jit | ||
$RUNNER --no-reg-alloc --engine="$GITHUB_WORKSPACE/out/clang/x64/walrus" | ||
$RUNNER --engine="$GITHUB_WORKSPACE/out/pure/x64/walrus" basic-tests wasm-test-core jit | ||
$RUNNER --jit --engine="$GITHUB_WORKSPACE/out/pure/x86/walrus" basic-tests wasm-test-core jit | ||
$RUNNER --no-reg-alloc --engine="$GITHUB_WORKSPACE/out/pure/x86/walrus" basic-tests wasm-test-core jit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The number of build options increased a lot and seems quite complex.
What about utilizing matrix
feature of actions to run each test simply?
(reference of matrix: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/using-a-matrix-for-your-jobs)
d205578
to
5527785
Compare
Test with jit-no-reg-alloc Signed-off-by: Laszlo Voros <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only one change.
@@ -178,10 +185,18 @@ def main(): | |||
parser.add_argument('suite', metavar='SUITE', nargs='*', default=sorted(DEFAULT_RUNNERS), | |||
help='test suite to run (%s; default: %s)' % (', '.join(sorted(RUNNERS.keys())), ' '.join(sorted(DEFAULT_RUNNERS)))) | |||
parser.add_argument('--jit', action='store_true', help='test with JIT') | |||
parser.add_argument('--no-reg-alloc', action='store_true', help='test with JIT without register allocation') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
--jit-no-reg-alloc
Test with jit-no-reg-alloc