driazati opened a new issue, #13337: URL: https://github.com/apache/tvm/issues/13337
Right now all CI (excluding GitHub Actions, which this doesn't address at all) goes through 1 indirection to get any useful information outside of a basic pass/fail, the `tvm-ci/pr-head` job here:  The `tvm-ci/pr-head` job then mixes all the tests together, which with sharding means dozens of tests in a long vertical column where it's hard to find exactly what failed. https://github.com/driazati/tvm/pull/38 shows an alternative where each platform (cpu, gpu, arm, etc) has its own job that reports from Jenkins to GitHub independently. To implement this, (1) Jenkins needs to be configured with job definitions for each of these platforms and (2) the `Jenkinsfile` in apache/tvm needs to be broken up - [ ] https://github.com/apache/tvm/pull/13300 splits up the Jenkinsfile into multiple ones per platform, which each of the jobs from (1) are set up to read. This doesn't do anything on its own. - [ ] for (1) that happens in https://github.com/tlc-pack/ci with the jenkins jobs here: https://github.com/tlc-pack/ci/blob/main/jenkins/jenkins-jobs/prod/tvm.yaml. https://github.com/tlc-pack/ci/pull/58 has the changes to move them over from my test repo to the main repo. Once merged this will start reporting the new statuses to GitHub - [ ] Once the previous step is working we can merge https://github.com/apache/tvm/pull/13316 which will make the new statuses required and get rid of the old `tvm-ci/pr-head` requirement. - [ ] Another PR in tlc-pack/ci to remove the `tvm-ci/pr-head` will stop it reporting to GitHub This will remove the `Jenkinsfile` at the top level, so Docker image updates would happen now in the `ci/jenkins/data.py` file which has the source data for the Jenkinsfile templates. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
