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/release-arm
in repository toolchain/ci/base-artifacts.
discards e3fee8f49 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1
new 4786c1145 0: update: binutils-gcc-linux-glibc-gdb-qemu: 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 (e3fee8f49)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/rele [...]
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 1568 -> 1568 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 42684 -> 42632 bytes
04-build_abe-stage1/console.log.xz | Bin 85364 -> 85024 bytes
06-build_abe-linux/console.log.xz | Bin 8776 -> 8932 bytes
07-build_abe-glibc/console.log.xz | Bin 284868 -> 284000 bytes
08-build_abe-stage2/console.log.xz | Bin 217828 -> 218760 bytes
09-build_abe-gdb/console.log.xz | Bin 40860 -> 40768 bytes
10-build_abe-qemu/console.log.xz | Bin 30464 -> 30364 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3828 bytes
12-build_abe-check_gcc/console.log.xz | Bin 2856 -> 2432 bytes
13-check_regression/console.log.xz | Bin 2960 -> 2544 bytes
13-check_regression/results.compare | 16 +-
13-check_regression/results.compare2 | 75 +-
14-update_baseline/console.log | 353 +++---
14-update_baseline/results.compare | 16 +-
14-update_baseline/results.compare2 | 75 +-
jenkins/manifest.sh | 28 +-
sumfiles/g++.log.xz | Bin 2453900 -> 2497168 bytes
sumfiles/g++.sum | 26 +-
sumfiles/gcc.log.xz | Bin 2038232 -> 2014616 bytes
sumfiles/gcc.sum | 1946 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 784120 -> 800804 bytes
sumfiles/gfortran.sum | 4 +-
sumfiles/libatomic.log.xz | Bin 2248 -> 2244 bytes
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log.xz | Bin 136116 -> 136020 bytes
sumfiles/libgomp.sum | 2 +-
sumfiles/libitm.log.xz | Bin 2652 -> 2648 bytes
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log.xz | Bin 411600 -> 420612 bytes
sumfiles/libstdc++.sum | 10 +-
32 files changed, 1216 insertions(+), 1339 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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 0e18bc955 2: update: binutils-llvm-linux-qemu: 19898
new 55d6060ed 2: update: linux-7d42e98182586f57f376406d033f05fe135edb75: 19898
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 (0e18bc955)
\
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 1608 -> 1544 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2752 bytes
03-build_abe-binutils/console.log.xz | Bin 41940 -> 42092 bytes
04-build_llvm/console.log.xz | Bin 59484 -> 59076 bytes
05-build_abe-qemu/console.log.xz | Bin 30096 -> 31660 bytes
06-build_linux/console.log.xz | Bin 4936 -> 4864 bytes
08-check_regression/console.log.xz | Bin 540 -> 480 bytes
08-check_regression/results.regressions | 2 -
09-update_baseline/console.log | 117 ++++++++++++++++----------------
jenkins/manifest.sh | 15 ++--
10 files changed, 64 insertions(+), 70 deletions(-)
delete mode 100644 08-check_regression/results.regressions
--
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_build/master-arm
in repository toolchain/ci/base-artifacts.
discards 9ad0fbf58 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new c7e062b55 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
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 (9ad0fbf58)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1568 -> 1572 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2796 bytes
04-build_abe-binutils/console.log.xz | Bin 42404 -> 42612 bytes
05-build_abe-stage1/console.log.xz | Bin 89536 -> 90604 bytes
06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes
07-build_abe-linux/console.log.xz | Bin 9016 -> 9540 bytes
08-build_abe-glibc/console.log.xz | Bin 229100 -> 229104 bytes
09-build_abe-stage2/console.log.xz | Bin 216156 -> 217028 bytes
10-build_abe-gdb/console.log.xz | Bin 42256 -> 42908 bytes
11-build_abe-qemu/console.log.xz | Bin 30204 -> 30440 bytes
12-check_regression/console.log.xz | Bin 416 -> 420 bytes
13-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 12 ++++++------
13 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_bmk_gnu_tx1/gnu-release-aarch64-spec2k6-O3
in repository toolchain/ci/binutils-gdb.
from 0d5a11affe Automatic date update in version.in
adds 6060c2f337 Automatic date update in version.in
adds 27439f0eda Automatic date update in version.in
adds fcc561a54d Automatic date update in version.in
adds f0f39c9cfa Automatic date update in version.in
adds ca0a5bdccf Automatic date update in version.in
adds 34223865b0 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.