Re: Update on upcoming changes to the MXNet CI: Jenkins

2020-02-13 Thread Davydenko, Denis
This makes total sense, Aaron. We can probably spend some time on these modifications once we complete originally mentioned changes __ On 2/13/20, 9:21 AM, "Aaron Markham" wrote: +1 These are good action items that should help alleviate part of the CI issues. The following

Re: Update on upcoming changes to the MXNet CI: Jenkins

2020-02-13 Thread Aaron Markham
+1 These are good action items that should help alleviate part of the CI issues. The following comments are not to take away from your proposal. Move forward, assuming the community agrees. I'd really like to see particular tests run only when the PR is touching a related part. While this is more

Re: Update on upcoming changes to the MXNet CI: Jenkins

2020-02-12 Thread Tao Lv
Can someone educate me how to re-trigger a single test suite in CI? On Thu, Feb 13, 2020 at 5:10 AM Lausen, Leonard wrote: > Hi Denis, > > pipeline may be the wrong word, job may be the correct one. For example, > commiters can currently access a job page like > >

Re: Update on upcoming changes to the MXNet CI: Jenkins

2020-02-12 Thread Lausen, Leonard
Hi Denis, pipeline may be the wrong word, job may be the correct one. For example, commiters can currently access a job page like http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-17521/5/ , press "Login" and then the restart button to only

Re: Update on upcoming changes to the MXNet CI: Jenkins

2020-02-12 Thread Davydenko, Denis
This might or might not work given that GH PR is failed or not given overall CI run status, not just few builds from it. But it is a good suggestion to try out, we will evaluate whether it could be accomplished. Thanks! On 2/12/20, 11:05 AM, "Lausen, Leonard" wrote: Thank you Denis for

Re: Update on upcoming changes to the MXNet CI: Jenkins

2020-02-12 Thread Davydenko, Denis
We intend this bot to be very simplistic initially. But your idea is very interesting and we will consider if we can roll this out as phase 2. On 2/12/20, 10:57 AM, "PrzemysÅ≠aw TrÄ˙dak" wrote: Hi Denis, Could this bot be smart enough to first do the sanity pipeline (to catch

Re: Update on upcoming changes to the MXNet CI: Jenkins

2020-02-12 Thread Lausen, Leonard
Thank you Denis for taking up this initiative. With respect to "Introduce per-PR CI bot" and the "[mxnet-ci] run" command. Would it make sense to add "retriggering only failed pipelines" to the scope? For example users could be asked to specify the name of the pipeline, or have "[mxnet-ci] run

Re: Update on upcoming changes to the MXNet CI: Jenkins

2020-02-12 Thread Przemysław Trędak
Hi Denis, Could this bot be smart enough to first do the sanity pipeline (to catch stuff like lint errors etc.) before launching the full thing? Thanks Przemek On 2020/02/12 18:12:07, "Davydenko, Denis" wrote: > Hello, MXNet dev community, > As you all know, the experience with CI