nodece commented on PR #28: URL: https://github.com/apache/pulsar-test-infra/pull/28#issuecomment-1092396641
@lhotari Thanks for your explanation! > There's a misunderstanding. The new CI requires using the new API for re-running just failed jobs and not the complete workflow. Please report what is broken first and we can think of a solution. 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? > I explained some of the changes in https://lists.apache.org/thread/n05xp17krb4f3cc0jjkh65ytqk1w6130 . > "The limitation is that you need to wait for all jobs to complete before failed jobs can be re-run." > > You can also provide feedback on the mailing list. This is detailed. > With the new CI there's another case where you see a red mark. It's when flaky tests fail, but later pass in a retry, the failed test result will get recorded to a test report. That doesn't block merging, but will show up so that the failures can be inspected. It's a bit confusing since GitHub Actions has a bug that the test reports get attached randomly to a workflow when there are multiple workflows executing. I'll write to the dev list explaining this since I have received a few questions about this. > It might appear that re-running doesn't work because of the new test reports. Those failures won't clear off, but they don't block merging either. This is confusing, I'm looking forward your solution. -- 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
