ci: upload test results as an artifact#293
Conversation
|
As discussion on the working group call. We need to make sure the output artifact is capture for each test run (it's currently overwriting). Another option is to dump the logs to the console in the diagnostics step. |
fcfbf90 to
fe933d4
Compare
|
Not required for this PR, but using something like https://github.com/marketplace/actions/junit-report-action could make the test reports more accessible without downloading the zip |
|
This PR was useful to uncover servicebinding/conformance#59 |
|
@sadlerap can we merge this? |
Since we run tests in parallel, behavex doesn't output a lot to the console. To retain some sense of ability to debug testing failures in CI, we should upload the output of behavex as an artifact to be inspected. Signed-off-by: Andy Sadler <ansadler@redhat.com>
fe933d4 to
92583bd
Compare
|
@scothis Should be good to merge at this point IMO, unless you have any particular reason to hold up on this. |
Signed-off-by: Scott Andrews <scott@andrews.me>
Codecov ReportPatch and project coverage have no change.
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## main #293 +/- ##
=======================================
Coverage 81.53% 81.53%
=======================================
Files 15 15
Lines 1446 1446
=======================================
Hits 1179 1179
Misses 219 219
Partials 48 48 ☔ View full report in Codecov by Sentry. |
Since we run tests in parallel, behavex doesn't output a lot to the console. To retain some sense of ability to debug testing failures in CI, we should upload the output of behavex as an artifact to be inspected.