This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/release-arm
in repository toolchain/ci/base-artifacts.
discards 11b554f07 0: update: binutils-gcc-linux-glibc-gdb: 6
new 6ea317ca5 0: update: binutils-gcc-linux-glibc-gdb: 6
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 (11b554f07)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/release [...]
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.xz | Bin 1540 -> 1540 bytes
02-prepare_abe/console.log.xz | Bin 2712 -> 2720 bytes
04-build_abe-binutils/console.log.xz | Bin 62588 -> 62452 bytes
05-build_abe-gcc/console.log.xz | Bin 222760 -> 223832 bytes
06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes
07-build_abe-linux/console.log.xz | Bin 9120 -> 9060 bytes
08-build_abe-glibc/console.log.xz | Bin 234092 -> 234568 bytes
09-build_abe-gdb/console.log.xz | Bin 50332 -> 50480 bytes
10-check_regression/console.log.xz | Bin 420 -> 420 bytes
11-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 12 ++++++------
11 files changed, 14 insertions(+), 14 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/llvm-master-arm-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 097a516c6 2: update: binutils-llvm-linux-qemu: 22486
new 6fd10942d 2: update: binutils-llvm-linux-qemu: 22736
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 (097a516c6)
\
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.xz | Bin 1592 -> 1624 bytes
02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes
03-build_abe-binutils/console.log.xz | Bin 30540 -> 30388 bytes
04-build_kernel_llvm/console.log.xz | Bin 0 -> 62524 bytes
04-build_llvm/console.log.xz | Bin 62180 -> 0 bytes
05-build_abe-qemu/console.log.xz | Bin 31624 -> 31544 bytes
06-build_linux/console.log.xz | Bin 4700 -> 4836 bytes
08-check_regression/console.log.xz | Bin 484 -> 484 bytes
09-update_baseline/console.log | 115 ++++-------------------------------
jenkins/manifest.sh | 22 +++----
results | 4 +-
11 files changed, 26 insertions(+), 115 deletions(-)
create mode 100644 04-build_kernel_llvm/console.log.xz
delete mode 100644 04-build_llvm/console.log.xz
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.