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-release-aarch64-next-defconfig
in repository toolchain/ci/binutils-gdb.
from f0b3db3175 Automatic date update in version.in
adds 37eaf1f099 Automatic date update in version.in
adds 178b942b8e Automatic date update in version.in
adds 3972c8ffe0 Automatic date update in version.in
adds 2365eacffe Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
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-release-aarch64-next-defconfig
in repository toolchain/ci/base-artifacts.
discards 616f718a 0: update: binutils-llvm-linux-qemu: boot
new 71e5c52d 0: update: binutils-llvm-linux-qemu: 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 (616f718a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-aarc [...]
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 1632 -> 1632 bytes
02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes
03-build_abe-binutils/console.log.xz | Bin 30244 -> 29980 bytes
04-build_kernel_llvm/console.log.xz | Bin 61256 -> 61060 bytes
05-build_abe-qemu/console.log.xz | Bin 32508 -> 32204 bytes
06-build_linux/console.log.xz | Bin 3660 -> 3444 bytes
07-boot_linux/console.log.xz | Bin 6220 -> 6288 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 18 +++++++++---------
results | 2 +-
11 files changed, 15 insertions(+), 15 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-master-aarch64-next-allnoconfig
in repository toolchain/ci/base-artifacts.
discards ce6c1cc7 0: update: binutils-gcc-linux-qemu: boot
new 0c1912bc 0: update: binutils-gcc-linux-qemu: 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 (ce6c1cc7)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-aarch6 [...]
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 1632 -> 1636 bytes
02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes
03-build_abe-binutils/console.log.xz | Bin 30396 -> 32152 bytes
04-build_abe-stage1/console.log.xz | Bin 73068 -> 72356 bytes
05-build_abe-qemu/console.log.xz | Bin 32972 -> 32804 bytes
06-build_linux/console.log.xz | Bin 4288 -> 4272 bytes
07-boot_linux/console.log.xz | Bin 504 -> 504 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 22 +++++++++++-----------
10 files changed, 16 insertions(+), 16 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_gnu_cross_check_gcc/master-arm
in repository toolchain/ci/base-artifacts.
discards cc09ce6a 0: update: linux-9f09069cde34dcd86f5ecf3a3139fd752020812f: 1
new b0a03499 0: update: qemu-8e9398e3b1a860b8c29c670c1b6c36afe8d87849: 1
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 (cc09ce6a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1608 -> 1604 bytes
02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes
03-build_abe-binutils/console.log.xz | Bin 29768 -> 29568 bytes
04-build_abe-stage1/console.log.xz | Bin 92760 -> 93056 bytes
06-build_abe-linux/console.log.xz | Bin 8856 -> 11020 bytes
07-build_abe-glibc/console.log.xz | Bin 230428 -> 231104 bytes
08-build_abe-stage2/console.log.xz | Bin 224376 -> 224620 bytes
09-build_abe-gdb/console.log.xz | Bin 34920 -> 34456 bytes
10-build_abe-qemu/console.log.xz | Bin 33500 -> 32020 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3852 bytes
12-build_abe-check_gcc/console.log.xz | Bin 2688 -> 2604 bytes
13-check_regression/console.log.xz | Bin 2352 -> 2364 bytes
13-check_regression/results.compare2 | 4 +-
14-update_baseline/console.log | 306 ++---
14-update_baseline/results.compare2 | 4 +-
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 2685752 -> 2677408 bytes
sumfiles/g++.sum | 8 +-
sumfiles/gcc.log.xz | Bin 2202420 -> 2218712 bytes
sumfiles/gcc.sum | 2140 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 883540 -> 886224 bytes
sumfiles/gfortran.sum | 2 +-
sumfiles/libatomic.log.xz | Bin 2268 -> 2260 bytes
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log.xz | Bin 198744 -> 198772 bytes
sumfiles/libgomp.sum | 2 +-
sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log.xz | Bin 425388 -> 426872 bytes
sumfiles/libstdc++.sum | 2 +-
30 files changed, 1240 insertions(+), 1240 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.