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-aarch64
in repository toolchain/ci/base-artifacts.
discards d14405857 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1
new d1d78e312 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 (d14405857)
\
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 1552 -> 1564 bytes
02-prepare_abe/console.log.xz | Bin 2760 -> 2776 bytes
03-build_abe-binutils/console.log.xz | Bin 30472 -> 30572 bytes
04-build_abe-stage1/console.log.xz | Bin 70988 -> 71280 bytes
06-build_abe-linux/console.log.xz | Bin 8716 -> 8848 bytes
07-build_abe-glibc/console.log.xz | Bin 235736 -> 236624 bytes
08-build_abe-stage2/console.log.xz | Bin 194204 -> 194440 bytes
09-build_abe-gdb/console.log.xz | Bin 38000 -> 38208 bytes
10-build_abe-qemu/console.log.xz | Bin 29992 -> 30300 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3880 bytes
12-build_abe-check_gcc/console.log.xz | Bin 2452 -> 2788 bytes
13-check_regression/console.log.xz | Bin 10576 -> 3248 bytes
13-check_regression/extra-bisect-params | 2 +-
13-check_regression/fails.sum | 28 +-
13-check_regression/results.compare | 49 +-
13-check_regression/results.compare2 | 2030 +---------------
13-check_regression/results.regressions | 49 +-
14-update_baseline/console.log | 2485 ++-----------------
14-update_baseline/extra-bisect-params | 2 +-
14-update_baseline/fails.sum | 28 +-
14-update_baseline/results.compare | 49 +-
14-update_baseline/results.compare2 | 2030 +---------------
14-update_baseline/results.regressions | 49 +-
jenkins/manifest.sh | 10 +-
sumfiles/g++.log.xz | Bin 3289292 -> 3292280 bytes
sumfiles/g++.sum | 48 +-
sumfiles/gcc.log.xz | Bin 2887828 -> 2892860 bytes
sumfiles/gcc.sum | 3979 ++++++++++++++++---------------
sumfiles/gfortran.log.xz | Bin 879452 -> 872060 bytes
sumfiles/gfortran.sum | 8 +-
sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log.xz | Bin 170632 -> 170676 bytes
sumfiles/libgomp.sum | 8 +-
sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log.xz | Bin 406176 -> 406968 bytes
sumfiles/libstdc++.sum | 6 +-
38 files changed, 2421 insertions(+), 8443 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-aarch64-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 374984e1f 0: update: gcc-8320b0e2997bc656228b1ef40da7c197fed0347b: boot
new 4486ca249 0: update: linux-3c241e0a66b121a7ef4af0afe1bbfeffa42a1308: 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 (374984e1f)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-aarch [...]
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 1760 -> 1608 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 41848 -> 41940 bytes
04-build_abe-stage1/console.log.xz | Bin 67388 -> 68896 bytes
05-build_abe-qemu/console.log.xz | Bin 30876 -> 30712 bytes
06-build_linux/console.log.xz | Bin 5096 -> 3356 bytes
07-boot_linux/console.log.xz | Bin 508 -> 508 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 8 ++++----
10 files changed, 5 insertions(+), 5 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 8d34471f70a gdb: add assert in remote_target::wait relating to async being off
new fa8f0a0ff05 gdb: add "exit" command as an alias for "quit"
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:
gdb/NEWS | 4 ++++
gdb/cli/cli-cmds.c | 3 ++-
gdb/doc/gdb.texinfo | 15 +++++++++------
3 files changed, 15 insertions(+), 7 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.