This is an automated email from the ASF dual-hosted git repository.
vega pushed a change to branch ci-docker-staging
in repository https://gitbox.apache.org/repos/asf/tvm-vta.git.
discard 81850c7 add devcommon
discard 112eb31 update docker bash
discard 9bb632c update ci files
discard 85e68e4 update cpptest
discard 9f8a46e update llvm
discard ea6829f update cmake variable
discard e092d48 update docker
new 522df61 update ci files
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 (81850c7)
\
N -- N -- N refs/heads/ci-docker-staging (522df61)
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 1 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 | 1 +
tests/scripts/dev_common.sh | 69 -----
tests/scripts/docker_bash.sh | 437 ++++-------------------------
tests/scripts/task_tvm_build.sh | 2 +-
tests/scripts/task_tvm_config_build_cpu.sh | 11 -
tests/scripts/task_tvm_cpptest.sh | 8 +-
6 files changed, 56 insertions(+), 472 deletions(-)
delete mode 100644 tests/scripts/dev_common.sh
