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-aarch64-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 1089a822 6: update: linux-7f376f1917d7461e05b648983e8d2aea9d0712b2: 19198
new f03625b4 6: update: binutils-gcc: 19198
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 (1089a822)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-aarch6 [...]
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 | 170 +-
02-prepare_abe/console.log | 392 +-
03-build_abe-binutils/console.log | 11701 +++++-----
04-build_abe-stage1/console.log | 15977 ++++++-------
05-build_linux/console.log | 9410 ++++----
07-check_regression/console.log | 2 +-
07-check_regression/results.regressions | 20 +-
08-update_baseline/console.log | 36 +-
08-update_baseline/results.regressions | 20 +-
console.log | 37688 +++++++++++++++---------------
jenkins/manifest.sh | 16 +-
11 files changed, 38219 insertions(+), 37213 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_bmk_tk1/llvm-release-arm-spec2k6-O3_LTO
in repository toolchain/ci/base-artifacts.
discards 628f6733 0: update: binutils-gcc-glibc-llvm: 1
new c22fe03a 0: update: binutils-gcc-glibc-llvm: 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 (628f6733)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_tk1/llvm-release-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 | 77 +-
02-prepare_abe/console.log | 288 +-
03-build_abe-binutils/console.log | 11157 +-
04-build_abe-stage1/console.log | 17976 ++--
05-build_abe-linux/console.log | 293 +-
06-build_abe-glibc/console.log | 38763 +++----
07-build_abe-stage2/console.log | 44498 ++++----
08-build_llvm-true/console.log | 12711 +--
10-benchmark--O3_LTO_marm/benchmark-start.log | 2 +-
10-benchmark--O3_LTO_marm/benchmark.log | 15 +-
10-benchmark--O3_LTO_marm/console.log | 309 +-
11-check_regression/console.log | 764 +-
11-check_regression/results-0.csv | 122 +-
11-check_regression/results-1.csv | 116 +-
11-check_regression/results-brief.csv | 38 +-
11-check_regression/results-full.csv | 122 +-
11-check_regression/results.csv | 48 +-
11-check_regression/results.log | 2662 +-
12-update_baseline/console.log | 122 +-
12-update_baseline/results-0.csv | 122 +-
12-update_baseline/results-1.csv | 116 +-
12-update_baseline/results-brief.csv | 38 +-
12-update_baseline/results-full.csv | 122 +-
12-update_baseline/results.csv | 48 +-
12-update_baseline/results.log | 2730 +-
console.log | 126968 +++++++++++------------
jenkins/manifest.sh | 12 +-
results_id | 2 +-
28 files changed, 130079 insertions(+), 130162 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/gnu-release-aarch64-check_binutils
in repository toolchain/ci/binutils-gdb.
from b9d8df7609 Automatic date update in version.in
adds a5326bc6b3 Automatic date update in version.in
new 568796bfd7 Automatic date update in version.in
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:
bfd/version.h | 2 +-
1 file changed, 1 insertion(+), 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/gnu-release-aarch64-check_binutils
in repository toolchain/ci/base-artifacts.
discards e1f34752 0: update: binutils-b9d8df7609a181e436410460081b246744ea46a0: 1
new 82db74d1 0: update: binutils-568796bfd7c408fadf5a8012e59d1ec02d3e10a2: 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 (e1f34752)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu/gnu-release-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 | 128 +-
02-prepare_abe/console.log | 396 +-
03-build_abe-binutils/console.log | 13607 +++++++++++----------
04-build_abe-check_binutils/console.log | 5030 ++++----
05-check_regression/console.log | 172 +-
05-check_regression/results.regressions | 4 +-
06-update_baseline/console.log | 278 +-
06-update_baseline/results.regressions | 4 +-
console.log | 19613 +++++++++++++++---------------
jenkins/manifest.sh | 10 +-
sumfiles/binutils.log.xz | Bin 36852 -> 36680 bytes
sumfiles/binutils.sum | 2 +-
sumfiles/gas.log.xz | Bin 67420 -> 67444 bytes
sumfiles/gas.sum | 4 +-
sumfiles/ld.log.xz | Bin 92308 -> 92604 bytes
sumfiles/ld.sum | 4 +-
16 files changed, 19625 insertions(+), 19627 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 gcc.
from 2c3d487a9a8 VAX: Unify push operation selection
new b4cdc2a3d33 Daily bump.
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:
gcc/ChangeLog | 206 ++++++++++++++++++++++++++++++++++++++++++++++++
gcc/DATESTAMP | 2 +-
gcc/fortran/ChangeLog | 5 ++
gcc/testsuite/ChangeLog | 79 +++++++++++++++++++
4 files changed, 291 insertions(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.