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/release-aarch64-check_bootstrap
in repository toolchain/ci/base-artifacts.
discards 5ef67f79 0: update: binutils-gcc: 1
new dfc34158 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 (5ef67f79)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check_bootstrap/rele [...]
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 -> 1544 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes
03-build_abe-binutils/console.log.xz | Bin 49820 -> 50064 bytes
04-build_abe-bootstrap/console.log.xz | Bin 244956 -> 244868 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3816 bytes
06-build_abe-check_bootstrap/console.log.xz | Bin 2400 -> 2392 bytes
07-check_regression/console.log.xz | Bin 2488 -> 3348 bytes
07-check_regression/extra-bisect-params | 1 +
07-check_regression/fails.sum | 7 +
07-check_regression/results.compare | 26 +-
07-check_regression/results.compare2 | 107 +-
07-check_regression/results.regressions | 27 +
08-update_baseline/console.log | 464 ++--
08-update_baseline/extra-bisect-params | 1 +
08-update_baseline/fails.sum | 7 +
08-update_baseline/results.compare | 26 +-
08-update_baseline/results.compare2 | 107 +-
08-update_baseline/results.regressions | 27 +
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 3390340 -> 3385380 bytes
sumfiles/g++.sum | 135 +-
sumfiles/gcc.log.xz | Bin 2969536 -> 2948156 bytes
sumfiles/gcc.sum | 3939 ++++++++++++++-------------
sumfiles/gfortran.log.xz | Bin 844932 -> 855200 bytes
sumfiles/gfortran.sum | 46 +-
sumfiles/libatomic.log.xz | Bin 2336 -> 2336 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 145220 -> 145804 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2708 -> 2720 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 426620 -> 443356 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 2694 insertions(+), 2274 deletions(-)
create mode 100644 07-check_regression/extra-bisect-params
create mode 100644 07-check_regression/fails.sum
create mode 100644 07-check_regression/results.regressions
create mode 100644 08-update_baseline/extra-bisect-params
create mode 100644 08-update_baseline/fails.sum
create 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_kernel/llvm-master-aarch64-next-defconfig
in repository toolchain/ci/base-artifacts.
discards 0b7e1f5b 2: update: binutils-llvm-linux-qemu: 37
new 0a0020d5 2: update: binutils-llvm-linux-qemu: 37
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 (0b7e1f5b)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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 1560 -> 1552 bytes
02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 45840 -> 45744 bytes
04-build_llvm/console.log.xz | Bin 60364 -> 60280 bytes
05-build_abe-qemu/console.log.xz | Bin 29824 -> 29980 bytes
06-build_linux/console.log.xz | Bin 3736 -> 3552 bytes
08-check_regression/console.log.xz | Bin 476 -> 476 bytes
09-update_baseline/console.log | 225 ++++++++++++++++++-----------------
jenkins/manifest.sh | 16 +--
9 files changed, 121 insertions(+), 120 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-aarch64-bootstrap_profiled
in repository toolchain/ci/base-artifacts.
discards d2cd32eb 0: update: binutils-gcc: 2
new f844575c 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 (d2cd32eb)
\
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 1520 -> 1512 bytes
02-prepare_abe/console.log.xz | Bin 2772 -> 2748 bytes
04-build_abe-binutils/console.log.xz | Bin 53052 -> 53440 bytes
05-build_abe-bootstrap_profiled/console.log.xz | Bin 500184 -> 500536 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.
unknown user pushed a change to branch master
in repository binutils-gdb.
from 9f6148cb853 gdb: more compile fixes for gnu-nat.c
new 2990bf40964 Update bug reporting address
new 0c3e266dc28 binutils debuginfod test
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:
bfd/README | 2 +-
bfd/configure | 2 +-
bfd/configure.ac | 2 +-
bfd/po/Make-in | 4 ++--
binutils/po/Make-in | 2 +-
binutils/testsuite/binutils-all/debuginfod.exp | 3 ++-
gas/README | 6 +-----
gas/po/Make-in | 2 +-
gold/po/Make-in | 2 +-
gprof/po/Make-in | 2 +-
ld/po/Make-in | 4 ++--
opcodes/po/Make-in | 2 +-
12 files changed, 15 insertions(+), 18 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.