lhotari commented on PR #28: URL: https://github.com/apache/pulsar-test-infra/pull/28#issuecomment-1092402909
> I have a question about the `get_runs failure` don't seem to get the correct data, this data includes the `conclusion: success` item. Do you notice this? Yes. That happens when an actual build run hasn't failed. As explained in previous comments, the test reports added to the build are causing this. The benefit of seeing the failed test reports is that we can start paying more attention to the flaky test problem and fixing them. Flaky tests might be indicating real production code issues. > This is confusing, I'm looking forward your solution. There's really no other solution than documenting this. We could remove the rendered test reports, but I think that integrating test reports to GitHub Actions UI is useful. GitHub Actions UI has a bug that [test reports get attached to wrong workflows](https://github.com/dorny/test-reporter/issues/67) when there's more than one workflow that gets triggered by a build job. Perhaps some day GitHub fixes this issue and the test reports can be shown in the correct location, attached to each build job. That would help resolve the issue since the test reports wouldn't be a separate check and instead the test reports could be attached to the build job that runs the tests. That's currently not possible because of the GitHub Actions bug. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
