This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 4503af8fd 0: update: llvm-linux: all
new 38fd869ab 0: update: llvm-linux: all
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 (4503af8fd)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-m [...]
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" 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 "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log | 220 +-
02-build_llvm/console.log | 12247 +++++++++++++++++------------------
03-build_linux/console.log | 762 +--
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 8 +-
06-update_baseline/console.log | 8 +-
console.log | 13264 +++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
8 files changed, 13280 insertions(+), 13245 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards a5a1049aa 0: update: binutils-gcc-linux: boot
new 791ed82ea 0: update: binutils-gcc-linux: boot
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 (a5a1049aa)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-s [...]
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" 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 "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log | 231 +-
02-prepare_abe/console.log | 436 +-
03-build_abe-binutils/console.log | 11020 ++++++-------
04-build_abe-stage1/console.log | 18649 ++++++++++-----------
05-build_linux/console.log | 1076 +-
06-boot_linux/console.log | 476 +-
07-check_regression/console.log | 8 +-
08-update_baseline/console.log | 14 +-
console.log | 31910 ++++++++++++++++++------------------
jenkins/manifest.sh | 14 +-
10 files changed, 31929 insertions(+), 31905 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-defconfig
in repository toolchain/ci/base-artifacts.
discards f3cc0edd7 0: update: binutils-gcc-linux: boot
new f40036b4e 0: update: binutils-gcc-linux: boot
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 (f3cc0edd7)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-m [...]
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 "omits" are not gone; other references still
refer to them. Any revisions marked "discards" 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 "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log | 78 +-
02-prepare_abe/console.log | 180 +-
03-build_abe-binutils/console.log | 10959 ++++++-------
04-build_abe-stage1/console.log | 18569 ++++++++++-----------
05-build_linux/console.log | 680 +-
06-boot_linux/console.log | 482 +-
07-check_regression/console.log | 8 +-
08-update_baseline/console.log | 8 +-
console.log | 31055 ++++++++++++++++++------------------
jenkins/manifest.sh | 14 +-
10 files changed, 31010 insertions(+), 31023 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk
in repository toolchain/ci/interesting-commits.
from f1fd5ba Add bad-merge-base 7b5565418f4d6e113ba805dad40d471d23bca6f6 f [...]
new 21e573a Add bad-merge-base 56c86f5dd516284558e106d04b92875d5b623b7a f [...]
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
glibc | 1 +
1 file changed, 1 insertion(+)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.