[GitHub] [tvm] driazati opened a new issue, #12392: [ci] Don't merge before running CI on `main`

[GitBox <gi...@apache.org>]

driazati opened a new issue, #12392:
URL: https://github.com/apache/tvm/issues/12392

   Here Jenkins fetches the latest `main` and merges code with it to make sure PRs are up to date before running everything: https://github.com/apache/tvm/blob/de124862714e747764aa8b7f41a90bcb25f3c6a8/ci/jenkins/Prepare.groovy.j2#L16-L27
   
   This should have a guard so it doesn't happen on main (i.e. when `env.BRANCH_NAME` is `main`) and instead `upstream_revision` is just set to `HEAD`. Right now the behavior is not correct, since if 2 builds come in in rapid succession, the first one would get merged with the later one and wouldn't be tested independently. This also messes up re-runs of old builds on `main` since they get merged with the current `main`.


-- 
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: commits-unsubscribe@tvm.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [tvm] driazati closed issue #12392: [ci] Don't merge before running CI on `main`

[GitBox <gi...@apache.org>]

driazati closed issue #12392: [ci] Don't merge before running CI on `main`
URL: https://github.com/apache/tvm/issues/12392


-- 
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: commits-unsubscribe@tvm.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org