driazati opened a new issue, #12388: URL: https://github.com/apache/tvm/issues/12388
Concurrent Jenkinsfile changes that happen in a sequence like: 1. PR 1 makes changes 2. PR 2 makes changes 3. PR 1 merges 4. PR 2 merges Can create a situation where both PRs pass CI but break `main` when merged with failures like https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/4024/pipeline. There is a timestamp in the `Jenkinsfile` that makes it so these PRs will have a merge conflict (in the example above PR 2 must be rebased and run through CI again before it can merge), we should check that any changes to the Jenkinsfile also change this timestamp (so if say PR 2 did not change the timestamp it wouldn't pass PR CI) -- 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]
