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 2346be62 0: update: binutils-gcc: 1
new 0a9f4301 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 (2346be62)
\
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 -> 1524 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes
03-build_abe-binutils/console.log.xz | Bin 37796 -> 38116 bytes
04-build_abe-gcc/console.log.xz | Bin 206464 -> 207560 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3888 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2400 -> 2388 bytes
07-check_regression/console.log.xz | Bin 3016 -> 3004 bytes
07-check_regression/extra-bisect-params | 2 +-
07-check_regression/fails.sum | 7 +-
07-check_regression/results.compare | 32 +-
07-check_regression/results.compare2 | 50 +-
07-check_regression/results.regressions | 32 +-
08-update_baseline/console.log | 292 +-
08-update_baseline/extra-bisect-params | 2 +-
08-update_baseline/fails.sum | 7 +-
08-update_baseline/results.compare | 32 +-
08-update_baseline/results.compare2 | 50 +-
08-update_baseline/results.regressions | 32 +-
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 3457868 -> 3497968 bytes
sumfiles/g++.sum | 144 +-
sumfiles/gcc.log.xz | Bin 2997636 -> 2985968 bytes
sumfiles/gcc.sum | 4582 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 1019924 -> 1013380 bytes
sumfiles/gfortran.sum | 42 +-
sumfiles/libatomic.log.xz | Bin 2192 -> 2188 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 190604 -> 190536 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2552 -> 2544 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 430688 -> 431648 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 2683 insertions(+), 2667 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-arm-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 27707329 6: update: binutils-gcc-linux-qemu: 19506
new a3dcaac2 6: update: binutils-gcc-linux-qemu: 19521
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 (27707329)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ne [...]
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 1560 -> 1556 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes
03-build_abe-binutils/console.log.xz | Bin 29808 -> 30056 bytes
04-build_abe-stage1/console.log.xz | Bin 90576 -> 89556 bytes
05-build_abe-qemu/console.log.xz | Bin 31404 -> 31456 bytes
06-build_linux/console.log.xz | Bin 82964 -> 83308 bytes
08-check_regression/console.log.xz | Bin 488 -> 480 bytes
09-update_baseline/console.log | 34 +++++++++++++++++-----------------
jenkins/manifest.sh | 22 +++++++++++-----------
results | 2 +-
10 files changed, 29 insertions(+), 29 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_bootstrap/master-arm-check_bootstrap
in repository toolchain/ci/base-artifacts.
discards 6acf8348 0: update: binutils-gcc: 1
new 4ddfecdd 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 (6acf8348)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check_bootstrap/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 -> 1556 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2764 bytes
03-build_abe-binutils/console.log.xz | Bin 51792 -> 50400 bytes
04-build_abe-bootstrap/console.log.xz | Bin 462920 -> 461268 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3808 bytes
06-build_abe-check_bootstrap/console.log.xz | Bin 2336 -> 2344 bytes
07-check_regression/console.log.xz | Bin 6604 -> 2572 bytes
07-check_regression/results.compare | 16 +-
07-check_regression/results.compare2 | 1214 +-------
08-update_baseline/console.log | 1376 +--------
08-update_baseline/results.compare | 16 +-
08-update_baseline/results.compare2 | 1214 +-------
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 2823484 -> 2768304 bytes
sumfiles/g++.sum | 127 +-
sumfiles/gcc.log.xz | Bin 2452580 -> 2473056 bytes
sumfiles/gcc.sum | 4395 ++++++++++++++-------------
sumfiles/gfortran.log.xz | Bin 935296 -> 938092 bytes
sumfiles/gfortran.sum | 42 +-
sumfiles/libatomic.log.xz | Bin 2304 -> 2308 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 195600 -> 195180 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 460276 -> 466468 bytes
sumfiles/libstdc++.sum | 10 +-
27 files changed, 2485 insertions(+), 5963 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.