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 1f248f0f1 0: update: binutils-gcc: 2
new 9386a8961 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 (1f248f0f1)
\
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 1496 -> 1536 bytes
02-prepare_abe/console.log.xz | Bin 2748 -> 2760 bytes
04-build_abe-binutils/console.log.xz | Bin 50932 -> 51368 bytes
05-build_abe-bootstrap_lto/console.log.xz | Bin 485252 -> 490476 bytes
06-check_regression/console.log.xz | Bin 416 -> 416 bytes
07-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 12 ++++++------
7 files changed, 7 insertions(+), 7 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_build/master-aarch64
in repository toolchain/ci/linux.
from 40c843218f11 Merge tag 'perf-tools-for-v5.17-2022-01-22' of git://git.k [...]
adds e783362eb54c Linux 5.17-rc1
No new revisions were added by this update.
Summary of changes:
Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 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_build/master-aarch64
in repository toolchain/ci/gcc.
from 9718bc4b03c c++: array temporary at file scope [PR104182]
adds 603a9ab41f4 contrib: filter out one more Clang warning.
No new revisions were added by this update.
Summary of changes:
contrib/filter-clang-warnings.py | 3 ++-
1 file changed, 2 insertions(+), 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_gnu_cross_build/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 6758df6fd 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new 513025697 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 (6758df6fd)
\
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 2768 -> 2772 bytes
04-build_abe-binutils/console.log.xz | Bin 30196 -> 30108 bytes
05-build_abe-stage1/console.log.xz | Bin 71448 -> 71192 bytes
07-build_abe-linux/console.log.xz | Bin 9560 -> 8520 bytes
08-build_abe-glibc/console.log.xz | Bin 236968 -> 236980 bytes
09-build_abe-stage2/console.log.xz | Bin 198312 -> 198676 bytes
10-build_abe-gdb/console.log.xz | Bin 37132 -> 37020 bytes
11-build_abe-qemu/console.log.xz | Bin 30612 -> 30676 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 14 +++++++-------
12 files changed, 8 insertions(+), 8 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/gcc.
from 9718bc4b03c c++: array temporary at file scope [PR104182]
adds 603a9ab41f4 contrib: filter out one more Clang warning.
No new revisions were added by this update.
Summary of changes:
contrib/filter-clang-warnings.py | 3 ++-
1 file changed, 2 insertions(+), 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_gcc_check/master-aarch64
in repository toolchain/ci/base-artifacts.
discards d666dd516 0: update: binutils-gcc: 1
new e16755256 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 (d666dd516)
\
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 -> 1536 bytes
02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes
03-build_abe-binutils/console.log.xz | Bin 37920 -> 37512 bytes
04-build_abe-gcc/console.log.xz | Bin 207964 -> 207244 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2732 -> 2476 bytes
07-check_regression/console.log.xz | Bin 3256 -> 3016 bytes
07-check_regression/extra-bisect-params | 2 +-
07-check_regression/fails.sum | 11 +-
07-check_regression/results.compare | 34 +-
07-check_regression/results.compare2 | 61 +-
07-check_regression/results.regressions | 34 +-
08-update_baseline/console.log | 431 ++-
08-update_baseline/extra-bisect-params | 2 +-
08-update_baseline/fails.sum | 11 +-
08-update_baseline/results.compare | 34 +-
08-update_baseline/results.compare2 | 61 +-
08-update_baseline/results.regressions | 34 +-
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 3455652 -> 3458012 bytes
sumfiles/g++.sum | 118 +-
sumfiles/gcc.log.xz | Bin 2986016 -> 2986648 bytes
sumfiles/gcc.sum | 5170 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 1021084 -> 1027808 bytes
sumfiles/gfortran.sum | 40 +-
sumfiles/libatomic.log.xz | Bin 2188 -> 2192 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 189804 -> 189580 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2552 -> 2544 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 430028 -> 431108 bytes
sumfiles/libstdc++.sum | 12 +-
33 files changed, 3015 insertions(+), 3074 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_profiled_lto_lean
in repository toolchain/ci/base-artifacts.
discards 940ef187a 0: update: binutils-gcc: 2
new 348660693 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 (940ef187a)
\
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 -> 1560 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes
04-build_abe-binutils/console.log.xz | Bin 51732 -> 50400 bytes
.../console.log.xz | Bin 1048388 -> 1048620 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.