ci: upload test results as an artifact by sadlerap · Pull Request #293 · servicebinding/runtime
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.
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.
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>
sadlerap
marked this pull request as ready for review
@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 Report
Patch and project coverage have no change.
Comparison is base (
748e4c2) 81.53% compared to head (2e76a52) 81.53%.
❗ 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.
📢 Do you have feedback about the report comment? Let us know in this issue.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters