+1, this is helpful. We had a similar situation with DataflowTemplates <https://github.com/GoogleCloudPlatform/DataflowTemplates>. Even though we used a different repository (mikepenz/action-junit-report <https://github.com/mikepenz/action-junit-report>), this strategy was invaluable to reduce troubleshoot time (sample report <https://github.com/GoogleCloudPlatform/DataflowTemplates/pull/1025/checks?check_run_id=16466087985> ).
Thanks Yi! On Tue, Sep 5, 2023 at 11:26 AM Danny McCormick via dev <dev@beam.apache.org> wrote: > Thanks Yi, I'm definitely +1 on adding this, this is definitely a gap in > our GitHub Actions infra today. > > Thanks, > Danny > > On Tue, Sep 5, 2023 at 10:35 AM Yi Hu via dev <dev@beam.apache.org> wrote: > >> Hi everyone, >> >> As you may have noticed, GitHub Action for test suites are setting up in >> the Beam repository. A current gap is that Jenkins has a pretty convenient >> test result page showing all tests / failed tests and stack trace, while >> these are not available in github workflow logs. >> >> Here we propose to introduce EnricoMi/publish-unit-test-result-action ( >> https://github.com/EnricoMi/publish-unit-test-result-action) to publish >> Java (and possibly Python in the future) test results. An example PR can be >> found [1] and an INFRA ticket in [2]. Currently both Java and Python test >> reports are supported by this action (note that Jenkins test report page is >> also available only for Java and Python currently). >> >> Please feel free to comment if you have any questions and suggestions. >> >> >> [1] https://github.com/apache/beam/pull/28075 >> [2] https://issues.apache.org/jira/browse/INFRA-24950 >> >> Regards, >> Yi >> -- >> >> Yi Hu, (he/him/his) >> >> Software Engineer >> >> >>
