This is an automated email from the ASF dual-hosted git repository.
leandron pushed a change to branch ci-docker-staging
in repository https://gitbox.apache.org/repos/asf/tvm.git
discard 52f5c155f1 Apply transformers fix.
discard 93c88ca603 Apply ONNX fix
discard 231854d1d2 [CI] Update Docker image tags to 20220817-102754-01a1034ccp
new 341d8dbac7 [CI] Update Docker image tags to 20220822-105603-52f5c155f
new 4b66fb99f6 Apply ONNX fix
new 1c42d5e5e6 Apply transformers fix.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (52f5c155f1)
\
N -- N -- N refs/heads/ci-docker-staging (1c42d5e5e6)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
Jenkinsfile | 22 +++++++++++-----------
ci/jenkins/Jenkinsfile.j2 | 20 ++++++++++----------
2 files changed, 21 insertions(+), 21 deletions(-)
