This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-release-arm_eabi-coremark-O3
in repository toolchain/ci/base-artifacts.
discards 352f0381e 0: update: binutils-gcc-newlib: 1
new 6cb5658e8 0: update: binutils-gcc-newlib: 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 (352f0381e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_e [...]
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 1568 -> 1552 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2740 bytes
03-build_abe-binutils/console.log.xz | Bin 30004 -> 29584 bytes
04-build_abe-stage1/console.log.xz | Bin 83444 -> 83676 bytes
06-build_abe-newlib/console.log.xz | Bin 16664 -> 16636 bytes
07-build_abe-stage2/console.log.xz | Bin 157576 -> 157564 bytes
08-benchmark/benchmark-build.log | 46 +++++++++++++++----------------
08-benchmark/benchmark.log | 44 ++++++++++++++---------------
08-benchmark/console.log.xz | Bin 3068 -> 3016 bytes
09-check_regression/console.log.xz | Bin 1664 -> 1664 bytes
09-check_regression/results-0.csv | 2 +-
09-check_regression/results-1.csv | 2 +-
09-check_regression/results-brief.csv | 2 +-
09-check_regression/results-full.csv | 2 +-
09-check_regression/results-internal.csv | 2 +-
09-check_regression/results-perf-0.csv | 2 +-
09-check_regression/results-perf-1.csv | 2 +-
09-check_regression/results.log | 8 +++---
10-update_baseline/console.log | 20 +++++++-------
10-update_baseline/results-0.csv | 2 +-
10-update_baseline/results-1.csv | 2 +-
10-update_baseline/results-brief.csv | 2 +-
10-update_baseline/results-full.csv | 2 +-
10-update_baseline/results-internal.csv | 2 +-
10-update_baseline/results-perf-0.csv | 2 +-
10-update_baseline/results-perf-1.csv | 2 +-
10-update_baseline/results.log | 8 +++---
jenkins/manifest.sh | 20 +++++++-------
results_id | 2 +-
29 files changed, 86 insertions(+), 90 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_native_build/master-arm
in repository toolchain/ci/glibc.
from cf73acb596 clock_settime/clock_gettime: Use __nonnull to avoid null pointer
adds 050cc5f7c1 benchtests: Add wcrtomb microbenchmark
adds 71e2a681f1 linux: Fix posix_spawn return code if clone fails (BZ#29109)
No new revisions were added by this update.
Summary of changes:
benchtests/Makefile | 1 +
benchtests/bench-wcrtomb.c | 139 +++++++++++++++++++++++++++++++++++++++
sysdeps/unix/sysv/linux/spawni.c | 2 +-
3 files changed, 141 insertions(+), 1 deletion(-)
create mode 100644 benchtests/bench-wcrtomb.c
--
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_native_build/master-arm
in repository toolchain/ci/base-artifacts.
discards d902049b1 0: update: binutils-gcc-linux-glibc-gdb: 6
new 43eaee829 0: update: binutils-gcc-linux-glibc-gdb: 6
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 (d902049b1)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]
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 1512 -> 1500 bytes
02-prepare_abe/console.log.xz | Bin 2720 -> 2696 bytes
04-build_abe-binutils/console.log.xz | Bin 52352 -> 51356 bytes
05-build_abe-gcc/console.log.xz | Bin 231148 -> 229164 bytes
06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes
07-build_abe-linux/console.log.xz | Bin 9116 -> 9116 bytes
08-build_abe-glibc/console.log.xz | Bin 230140 -> 230712 bytes
09-build_abe-gdb/console.log.xz | Bin 49604 -> 49936 bytes
10-check_regression/console.log.xz | Bin 416 -> 416 bytes
11-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 26 +++++++++++++-------------
11 files changed, 21 insertions(+), 21 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-arm
in repository toolchain/ci/base-artifacts.
discards 0fa0b64a9 0: update: binutils-gcc: 1
new f0b139166 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 (0fa0b64a9)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (f0 [...]
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 1516 -> 1524 bytes
02-prepare_abe/console.log.xz | Bin 2720 -> 2716 bytes
03-build_abe-binutils/console.log.xz | Bin 50936 -> 52160 bytes
04-build_abe-gcc/console.log.xz | Bin 229224 -> 231368 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3832 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2656 -> 2436 bytes
07-check_regression/console.log.xz | Bin 2604 -> 3072 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 | 80 +-
07-check_regression/results.regressions | 27 +
08-update_baseline/console.log | 287 +-
08-update_baseline/extra-bisect-params | 1 +
08-update_baseline/fails.sum | 7 +
08-update_baseline/results.compare | 26 +-
08-update_baseline/results.compare2 | 80 +-
08-update_baseline/results.regressions | 27 +
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 2745168 -> 2765108 bytes
sumfiles/g++.sum | 118 +-
sumfiles/gcc.log.xz | Bin 2352292 -> 2354164 bytes
sumfiles/gcc.sum | 4848 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 909728 -> 902292 bytes
sumfiles/gfortran.sum | 40 +-
sumfiles/libatomic.log.xz | Bin 2180 -> 2172 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 200012 -> 200188 bytes
sumfiles/libgomp.sum | 24 +-
sumfiles/libitm.log.xz | Bin 2532 -> 2536 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 457228 -> 462956 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 2894 insertions(+), 2733 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.
unknown user pushed a change to branch master
in repository binutils-gdb.
from 0ee8858e7ae bfd targmatch.h makefile rule
new dd9cd55e990 PowerPC: bp-permanent.exp, kill-after-signal fix
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:
gdb/testsuite/gdb.base/bp-permanent.exp | 25 +++++++++++++++++++++
gdb/testsuite/gdb.base/kill-after-signal.exp | 33 +++++++++++++++++++++++++++-
2 files changed, 57 insertions(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.