Using TVM’s CI

TVM uses Jenkins for running Linux continuous integration (CI) tests on branches and pull requests through a build configuration specified in a Jenkinsfile. Non-critical jobs run in GitHub Actions for Windows and MacOS jobs.

A standard CI run looks something like this viewed in Jenkins’ BlueOcean viewer. CI runs usually take several hours to complete and pull requests (PRs) cannot be merged before CI has successfully completed. To diagnose failing steps, click through to the failing pipeline stage then to the failing step to see the output logs.

The Jenkins UI for a CI run

Debugging Failures

When CI fails for some reason, there are several methods to diagnose the issue.

Jenkins Logs

The first place to look for a failure is in the CI logs, follow the red Xs on the failing job to view the logs. Note:

  • Jenkins does not display the full log by default, at the top of the log viewer is a button “Show complete log” which will take you to a plaintext version of the log

  • pytest failures are summarized at the bottom of the log but you will likely need to scroll up to view the actual failure.

Reproduce Failures

Most TVM Python tests run under pytest and can be run as described in Testing.

Reporting Issues

Issues with CI should be reported on GitHub with a link to the relevant jobs, commits, or PRs.