Bot Commands

(This page is generated. Don't directly edit here. Your changes may be overwritten in future updates.)

Important

Triggering CI pipeline with !test is still working in progress. Until you hear further notice that it's ready, please remain using !build as usual.

The !build command without any option runs a default set of jobs, including C++ and python tests, examples build and run, sanity checks, etc.

The default set of jobs always run regardless of extra build options, unless specified otherwise.

You may use the options below to run extra optional tests.

CI bot commands:

Usage: !build [options]
  Options:
    --diff
      Run codegen diff jobs (fast): python tests and binary tests
    --diff-bench
      Run codegen diff jobs (slow): binary benchmark
    --matmul-bench
      Run python and binary matmul benchmark tests with LH plugin
    --pybench
      Run python benchmark jobs with `--disable-benchmarking` to check 
      functionality 
    --serde
      Run serialization and deserialization jobs

Example:

!build --diff

This runs the codegen diff jobs (fast) in addition to the default set of tests.

Re: jit_python_bc_advisory jobs

This job is created to detect backward compatibility (BC) breaking changes in python API. The job will build nvfuser from your PR head commit and run python tests from its merge base with the main branch, to catch any BC-breaking changes in python API.

If your PR has python tests passed but python_bc_advisory tests failed, you have two options:

1. Update the version.txt file. With that, the python_bc_advisory job will be skipped. We have a convention that a patch version update indicates python API changes.

   Sometimes when two PRs are both bumping version.txt at the same time and the other was merged before yours, you may see this error. This reminds you that you may need to bump version.txt again.

2. Ignore the failure in python_bc_advisory job, if it's for test only or you believe it's safe. This is why the job is named advisory.

Remember, you always have to make sure the jit_python_tests passed. Those are built and tested on your current PR head commit.