This has happened in the past. Usually there is some issue where Jenkins isn't notified of new PRs by Github or doesn't see the PR phrases and hence Jenkins sits around idle. This is usually fixed after a few hours without any action on our part.
On Wed, Jul 10, 2019 at 10:28 AM Katarzyna Kucharczyk < ka.kucharc...@gmail.com> wrote: > Hi all, > > Hope it's not duplicate but I can't find if any issue with phrase > triggering in Jenkins was already here. > Currently, I started third PR and no test were triggered there. I tried to > trigger some tests manually, but with no effect. > > Am I missing something? > > Here are links to my problematic PRs: > https://github.com/apache/beam/pull/9033 > https://github.com/apache/beam/pull/9034 > https://github.com/apache/beam/pull/9035 > > Thanks, > Kasia >
