Unfortunately, the previous change had issues restarting more than 1 build job.
The problem has been resolved now. The change was
https://github.com/apache/pulsar-test-infra/pull/34 . I merged the change, so
please do post-merge reviews.
"/pulsarbot rerun-failure-checks" should work now. I'm sor
I have made a fix to the problem described below.
Please review https://github.com/apache/pulsar-test-infra/pull/33 .
After this change is merged, closing and reopening PRs could be used to pick up
most recent change from the master branch and "/pulsarbot rerun-failure-checks"
will be able to re
GitHub Actions has some problem and the UI has a warning
"We are having problems searching workflow runs. The results may not be
complete."
(I can see this warning on https://github.com/apache/pulsar/actions)
The impact of this is that "/pulsarbot rerun-failure-checks" doesn't work when
it canno
With the new GitHub Actions CI workflow there are cases where you see a red
mark as a failure, but there's no need to rerun failed jobs since the red
failure marks are a result of failed test reports (usually from failed flaky
tests).
The new Pulsar CI workflow renders Junit xml test reports an
I now realized that my advice to close & reopen PRs to pick up master branch
changes is problematic. This will cause issues with "/pulsarbot
rerun-failure-checks". The script currently looks for the build to restart with
the PR's head commit sha. If closing and reopening is used to start new PR
Hi all,
There's a small limitation in re-running failed jobs (builds that fail because
of flaky tests) in the refactored Pulsar CI workflow which combines multiple
jobs into a single workflow.
The limitation is that you need to wait for all jobs to complete before failed
jobs can be re-run.
Ye
