-
Notifications
You must be signed in to change notification settings - Fork 112
Clean up Test Specification in our Github Actions #1419
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
Conversation
f1237e8 to
c762f60
Compare
| uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4 | ||
| with: | ||
| name: specified-upload | ||
| name: ${{inputs.failure-upload-name}} |
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.
@zach-klippenstein I also fixed test report upload on failure - so you can download the typical .html report and see the reasons for all your different test failures in CI.
| restore-cache-key: build-logic | ||
| write-cache-key: main-build-artifacts | ||
| failure-path-upload: '**/build/reports/tests/*[tT]est' | ||
| failure-upload-name: 'unit-tests-report' |
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.
Here is where we specify failure-path-upload (what to upload when there is a failure on the job).
c762f60 to
d1d9b43
Compare
We were using
jvmTestpreviously for the tests where we specify the runtime via the environment arg, but thejvmTesttask is only for KMP modules. Those KMP modules (namelyworkflow-runtime) already accounted for multiple runtimes usingBurst, so we were just running the same tests multiple times (it was not even using theJvmTestRuntimeConfigToolsto pull the arg).We should be running the regular java/android
testtask with the runtime specification, then the arg will be picked up.Also some other fixes for the proper targets - e.g.,
iosSimulatorArm64andjsBrowserTest.AND fixes the
failure-path-uploadusage so that we upload the test report successfully (the html one) when there is a failure (whether JVM or Android tests). (I've tested this when the tests were failing that I fixed).I had to modify two tests to check for particular runtime configs that are incompatible with the test structure, but everything else is working. yay!