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
follo
Hi dev community,
We have made the changes to the mxnet CI system to incorporate the
staggered build pipelines. With this change, when a new PR is created or an
existing PR is updated, the status checks will only show
“ci/jenkins/mxnet-validation/sanity” build job at first. Once this build
comple
Hi dev community,
The Jenkins CI server had to be restarted due to a high number of jobs
being inadvertently triggered and overloading the server. 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, c
load that to dockerhub, then we'd save build time and things
> breaking
> > > > randomly. Users can use those docker images too. At release time we
> do
> > a
> > > > round of updates and testing when we're ready. Can we find a balance
> > > > bet
me, so let me ask this way: are we actually
> > > rebuilding every single time or do you mean the docker cache? Pulling
> the
> > > cache should only take a few seconds from my experience - docker build
> > > should be a no-op in most cases.
> > >
> &g
s driving the duration for sanity? It used to be 50 sec
> execution and 60 sec preparation.
>
> -Marco
>
> Joe Evans schrieb am Do., 26. März 2020, 20:31:
>
> > Thanks Marco and Aaron for your input.
> >
> > > Can you show by how much the duration will increase?
&
on and thus heavily reduce the time spent
> > on
> > > the tasks instead of staggering?
> > >
> > > I feel concerned that these measures to save cost are paid in the form
> > of a
> > > worse user experience. I see a big potential to save costs by
>
further execution of CI builds. This
will increase the time required to test a PR, but will prevent unnecessary
builds from running.
Does anyone have any concerns with this change or suggestions?
Thanks.
Joe Evans
joseph.ev...@gmail.com
