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-aarch64
in repository toolchain/ci/base-artifacts.
discards 879d4847 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new 06ce239b 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 (879d4847)
\
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 1544 -> 1560 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes
04-build_abe-binutils/console.log.xz | Bin 45016 -> 45196 bytes
05-build_abe-stage1/console.log.xz | Bin 71596 -> 71588 bytes
06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes
07-build_abe-linux/console.log.xz | Bin 9220 -> 9468 bytes
08-build_abe-glibc/console.log.xz | Bin 236520 -> 235856 bytes
09-build_abe-stage2/console.log.xz | Bin 200296 -> 200824 bytes
10-build_abe-gdb/console.log.xz | Bin 44440 -> 44740 bytes
11-build_abe-qemu/console.log.xz | Bin 30048 -> 30100 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 14 +++++++-------
13 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_gcc_bootstrap/master-arm-bootstrap_lto
in repository toolchain/ci/base-artifacts.
discards 9453a98f 0: update: binutils-gcc: 2
new b7a0c428 0: update: binutils-gcc: 2
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 (9453a98f)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...]
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 1548 -> 1696 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes
04-build_abe-binutils/console.log.xz | Bin 65912 -> 65716 bytes
05-build_abe-bootstrap_lto/console.log.xz | Bin 479304 -> 483140 bytes
06-check_regression/console.log.xz | Bin 416 -> 420 bytes
07-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 12 ++++++------
7 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_gcc_check/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 3fa43914 0: update: binutils-gcc: 1
new e3af33bd 0: update: binutils-gcc: 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 (3fa43914)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...]
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 1520 -> 1520 bytes
02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes
03-build_abe-binutils/console.log.xz | Bin 53200 -> 52668 bytes
04-build_abe-gcc/console.log.xz | Bin 210268 -> 210476 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3820 bytes
06-build_abe-check_gcc/console.log.xz | Bin 3348 -> 2588 bytes
07-check_regression/console.log.xz | Bin 5360 -> 2740 bytes
07-check_regression/extra-bisect-params | 1 -
07-check_regression/fails.sum | 24 -
07-check_regression/results.compare | 117 +-
07-check_regression/results.compare2 | 548 +----
07-check_regression/results.regressions | 101 -
08-update_baseline/console.log | 945 ++------
08-update_baseline/extra-bisect-params | 1 -
08-update_baseline/fails.sum | 24 -
08-update_baseline/results.compare | 117 +-
08-update_baseline/results.compare2 | 548 +----
08-update_baseline/results.regressions | 101 -
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 3421868 -> 3406436 bytes
sumfiles/g++.sum | 138 +-
sumfiles/gcc.log.xz | Bin 2881844 -> 2905120 bytes
sumfiles/gcc.sum | 4042 ++++++++++++++++---------------
sumfiles/gfortran.log.xz | Bin 872700 -> 875616 bytes
sumfiles/gfortran.sum | 94 +-
sumfiles/libatomic.log.xz | Bin 2164 -> 2168 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 170828 -> 170936 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2528 -> 2528 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 429628 -> 428000 bytes
sumfiles/libstdc++.sum | 12 +-
33 files changed, 2440 insertions(+), 4407 deletions(-)
delete mode 100644 07-check_regression/extra-bisect-params
delete mode 100644 07-check_regression/fails.sum
delete mode 100644 07-check_regression/results.regressions
delete mode 100644 08-update_baseline/extra-bisect-params
delete mode 100644 08-update_baseline/fails.sum
delete mode 100644 08-update_baseline/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_gcc_bootstrap/master-aarch64-bootstrap_ubsan
in repository toolchain/ci/base-artifacts.
discards ea6ad424 0: update: binutils-gcc: 2
new 63491eff 0: update: binutils-gcc: 2
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 (ea6ad424)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]
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 1580 -> 1516 bytes
02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes
04-build_abe-binutils/console.log.xz | Bin 52132 -> 52308 bytes
05-build_abe-bootstrap_ubsan/console.log.xz | Bin 329784 -> 330960 bytes
06-check_regression/console.log.xz | Bin 420 -> 420 bytes
07-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 12 ++++++------
7 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.
unknown user pushed a change to branch master
in repository glibc.
from e938c02748 Don't add access size hints to fortifiable functions
new a643f60c53 Make sure that the fortified function conditionals are constant
new ad6f2a010c debug: Add tests for _FORTIFY_SOURCE=3
The 2 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:
debug/Makefile | 13 ++-
debug/tst-chk1.c | 102 ++++++++++++-----------
debug/tst-chk7.c | 2 +
debug/tst-chk8.cc | 2 +
io/bits/poll2.h | 27 ++-----
libio/bits/stdio2.h | 106 ++++++++++--------------
misc/sys/cdefs.h | 47 +++++++++++
posix/bits/unistd.h | 174 +++++++++------------------------------
socket/bits/socket2.h | 34 +++-----
stdlib/bits/stdlib.h | 57 ++++---------
wcsmbs/bits/wchar2.h | 219 ++++++++++++++------------------------------------
11 files changed, 295 insertions(+), 488 deletions(-)
create mode 100644 debug/tst-chk7.c
create mode 100644 debug/tst-chk8.cc
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.