Thank you Joe for getting the CI back into a working state. Do you have any
insights into what went wrong to get into the dysfunctional state?

On Mon, 2020-06-01 at 12:17 -0700, Joe Evans wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you can confirm the sender and know the
> content is safe.
> 
> 
> 
> Hi dev community,
> 
> 
> The Jenkins CI server had to be restarted due to a high number of jobs
> being hung in the queue. If you have open PRs waiting for status checks,
> you may have to re-trigger CI checks using mxnet-ci bot.
> 
> 
> To re-trigger CI checks that have failed, comment on your PR using the
> following syntax:
> 
> 
> @mxnet-bot run ci [<checks requested>]
> 
> 
> Example:
> 
> @mxnet-bot run ci [unix-gpu]
> 
> 
> Sorry for the inconvenience.
> 
> 
> Joe

Reply via email to