-
Notifications
You must be signed in to change notification settings - Fork 15
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
Run TrustEVM Contract Tests in CI #312
Conversation
5a5fd4c
to
434080d
Compare
434080d
to
b2cc85f
Compare
run: .github/workflows/test-contract.sh | ||
|
||
- name: Upload Test Metrics | ||
if: matrix.DWITH_TEST_ACTIONS == 'on' || matrix.DWITH_TEST_ACTIONS == 'true' |
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.
what's the need to check for on
or true
here? It seems like it could never be a value not defined in the matrix (on
or off
)?
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.
I guess I don't understand the question.
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.
Why can't this line (and all the other similar if
s) just be if: matrix.DWITH_TEST_ACTIONS == 'on'
?
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.
Ah! I understand, now. The purpose of the or
statement is in case someone uses true
and false
instead of on
or off
, which are also valid inputs to boolean cmake
flags.
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.
So is yes
and 1
though, but you're testing against the matrix
value which can only be
strategy:
matrix:
DWITH_TEST_ACTIONS: ['on', 'off']
From TrustEVM issue 242, this pull request builds on pull request 293 to add steps to the TrustEVM contract CI pipeline to run the contract tests and export xUnit test metrics.
The tests do not pass for me and I was informed on 2023-01-12 they are not expected to pass.
This pull requests runs them, but does not fail the build if the tests fail. I do not like this pattern, but this was requested by the team to track progress towards getting all tests passing.
See Also
.gitignore
.gitignore
-Deosio_DIR
cmake
Flag from Contract Tests