In addition to they delay in the trigger phrases, I'm seeing multi-hour (!)
delays in running tests.

For example: https://github.com/apache/beam/pull/5545

I triggered the Dataflow ValidatesRunner tests. The check showed up as
yellow with no "Details" link, which generally means it had not yet been
scheduled on Jenkins. It stayed like this for two hours, never even
starting to run. Apparently there were a ton of idle Jenkins executors at
the time, so it's not that all our Jenkins executors were busy. As of now,
it still has not started running.

Does anybody have any idea what's going on here?

Reuven

Reply via email to