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 e3848fe9 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1
new bc5f15bd 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 (e3848fe9)
\
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 1540 -> 1576 bytes
02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes
03-build_abe-binutils/console.log.xz | Bin 30872 -> 30824 bytes
04-build_abe-stage1/console.log.xz | Bin 90496 -> 89848 bytes
05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes
06-build_abe-linux/console.log.xz | Bin 8820 -> 9000 bytes
07-build_abe-glibc/console.log.xz | Bin 230504 -> 230216 bytes
08-build_abe-stage2/console.log.xz | Bin 217720 -> 216484 bytes
09-build_abe-gdb/console.log.xz | Bin 38560 -> 38520 bytes
10-build_abe-qemu/console.log.xz | Bin 29736 -> 29672 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3896 bytes
12-build_abe-check_gcc/console.log.xz | Bin 2944 -> 2464 bytes
13-check_regression/console.log.xz | Bin 3032 -> 2584 bytes
13-check_regression/results.compare | 24 +-
13-check_regression/results.compare2 | 147 +-
14-update_baseline/console.log | 295 ++--
14-update_baseline/results.compare | 24 +-
14-update_baseline/results.compare2 | 147 +-
jenkins/manifest.sh | 26 +-
sumfiles/g++.log.xz | Bin 2612396 -> 2582216 bytes
sumfiles/g++.sum | 126 +-
sumfiles/gcc.log.xz | Bin 2109380 -> 2151952 bytes
sumfiles/gcc.sum | 2450 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 861864 -> 865152 bytes
sumfiles/gfortran.sum | 40 +-
sumfiles/libatomic.log.xz | Bin 2244 -> 2248 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 169724 -> 169844 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2648 -> 2652 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 410620 -> 413900 bytes
sumfiles/libstdc++.sum | 16 +-
33 files changed, 1508 insertions(+), 1813 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-mainline-defconfig
in repository toolchain/ci/base-artifacts.
discards 32083d75 0: update: binutils-gcc-linux-qemu: boot
new e8de6a0a 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 (32083d75)
\
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 1592 -> 1580 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes
03-build_abe-binutils/console.log.xz | Bin 45560 -> 31036 bytes
04-build_abe-stage1/console.log.xz | Bin 71716 -> 70848 bytes
05-build_abe-qemu/console.log.xz | Bin 30456 -> 30476 bytes
06-build_linux/console.log.xz | Bin 4824 -> 4704 bytes
07-boot_linux/console.log.xz | Bin 6092 -> 6104 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 20 ++++++++++----------
10 files changed, 18 insertions(+), 18 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.
unknown user pushed a change to branch master
in repository binutils-gdb.
from e8f6cf14c97 Automatic date update in version.in
new 671fac7c452 gdbsupport: fix memory leak in create_file_handler when re- [...]
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:
gdbsupport/event-loop.cc | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.