-
Notifications
You must be signed in to change notification settings - Fork 6.7k
[CI][1.6.x] fix centos 7 url to unblock centos-cpu & gpu pipeline #18560
Conversation
|
Hey @ChaiBapchya , Thanks for submitting the PR
CI supported jobs: [clang, website, sanity, unix-cpu, miscellaneous, centos-gpu, windows-cpu, unix-gpu, edge, windows-gpu, centos-cpu] Note: |
* update dockerfile for jetson * add toolchain files * update build_jetson function * update ubuntu_julia.sh * update FindCUDAToolkit.cmake * Update centos7_python.sh * revert changes on ubuntu_julia.sh * disable TVM for gpu build * Disable TVM_OP on GPU builds Co-authored-by: Wei Chu <[email protected]> Co-authored-by: Leonard Lausen <[email protected]>
* Fix quantized concat when inputs are mixed int8 and uint8 Change-Id: I4da04bf4502425134a466823fb5f73da2d7a419b * skip flaky test * trigger ci
|
@szha can we revert this PR? While it fixed centos-cpu & centos-gpu So as a result, unix-gpu & edge pipeline are now broken. Way forward:
The reason why it showed you green was because it only ran sanity pipeline & didn't run other 10 pipelines. allowing you to merge with just 1 pipeline instead of other 10. |
This needs to be configured in Github Project Settings. There is a setting related to "require checks". It's currently only turned on for the master branch. This may require Apache Infra to change the setting. |
|
@ChaiBapchya I think it's ok to fix forward. |
|
We opted to not turn that in for feature branches to not bother infra too much and also allow the release manager to make certain calls without hitting limits. It's the general policy within the project that PRs with failed CI do not get merged. If a PR was merged, then the committer who merged the PR should be contacted and reminded. But I think sheng is aware of his mistake :) |
I don't think that's the case. We didn't have explicit discussion on this, nor do I think it's the right approach. It doesn't make sense to allow force push to release branches while protecting the development branch. Also, enabling branch protection for release branches doesn't necessarily "bother" apache infra either, as the setup is likely one-time. Branch protection can be turned on for branches that match a pattern, and we do have an explicit pattern for release branches according to the release process. |
|
Makes sense. |
|
We'd need a vote on dev@ first |
|
we should be able to do so with a lazy consensus. |
|
In any case there's a dev@ vote thread necessary |
…line (apache#18560)" This reverts commit d271348.
* add the missing build_ubuntu_gpu_cuda101_cudnn7_mkldnn_cpp_test in runtime_functions.sh * Revert "add the missing build_ubuntu_gpu_cuda101_cudnn7_mkldnn_cpp_test in runtime_functions.sh" This reverts commit de173b0. * Revert "[CI][1.6.x] fix centos 7 url to unblock centos-cpu & gpu pipeline (#18560)" This reverts commit d271348. * fix centos 7 url to unblock centos-cpu & gpu pipeline * skip quantized conv flaky case (#16866) * Fix quantized concat when inputs are mixed int8 and uint8 Change-Id: I4da04bf4502425134a466823fb5f73da2d7a419b * skip flaky test * trigger ci * Trigger empty commit * [v1.7.x] update jetson dockerfile to support CUDA 10.0 (#18339) * update dockerfile for jetson * add toolchain files * update build_jetson function * update ubuntu_julia.sh * update FindCUDAToolkit.cmake * Update centos7_python.sh * revert changes on ubuntu_julia.sh * disable TVM for gpu build * Disable TVM_OP on GPU builds Co-authored-by: Wei Chu <[email protected]> Co-authored-by: Leonard Lausen <[email protected]> * add setuptools to ci/docker/install/requirements * add missing build_ubuntu_gpu_cuda101_cudnn7_mkldnn_cpp_test * add setuptool to docker & cpp-test build syntax error * remove erroneously added cpp tests in 1.6.x * py3 to p2 Co-authored-by: Xinyu Chen <[email protected]> Co-authored-by: waytrue17 <[email protected]> Co-authored-by: Wei Chu <[email protected]> Co-authored-by: Leonard Lausen <[email protected]>
Currently, 1.6.x branch is failing on multiple pipelines
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fcentos-cpu/detail/v1.6.x/51/pipeline