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
Extract test results when there are failures #76
Comments
I use something similar to the following in my workflows: - name: Store reports
if: failure()
uses: actions/upload-artifact@v3
with:
name: reports
path: |
**/build/reports/
**/build/test-results/ See https://docs.github.com/en/actions/learn-github-actions/expressions#status-check-functions Note that the name is important if you have more than one Gradle invocation in the whole workflow (e.g. in a matrix build). To me, that's not the role of the gradle-build-action to do that, or that'll require it to be much more complex, if only in configurability. |
Related to gradle/gradle-build-action#98 |
Is this Kotlin MPP specific? Build scans contain JUnit test results. |
PS: There are other OSS actions available already, maybe it's sufficient to provide references?
(there may be others...) |
I think it would be nice to at least document the solution |
Hello,
When tests fail in CI, here's what I get:
This is so unhelpful as the runner deletes everything on exit, and you won't find the test failure report in the Gradle scan…
Can you extract the containing directory as a downloadable GitHub Action run artifact if it has files, so that we can actually find out why the tests failed in CI?
I find it hard to believe that I'd be the first one encountering this issue, but I'll accept the truth.
Thank you and have a great day!
Louis CAD
The text was updated successfully, but these errors were encountered: