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_tk1/gnu-release-arm-spec2k6-O3_LTO
in repository toolchain/ci/base-artifacts.
discards 84057eb09 16: update: binutils-linux-glibc: 1
new 5072469c4 16: update: binutils-gcc-linux-glibc: 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 (84057eb09)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-release- [...]
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 -> 1672 bytes
02-prepare_abe/console.log.xz | Bin 2772 -> 2756 bytes
03-build_abe-binutils/console.log.xz | Bin 41984 -> 42320 bytes
04-build_abe-stage1/console.log.xz | Bin 84408 -> 90420 bytes
06-build_abe-linux/console.log.xz | Bin 9008 -> 8828 bytes
07-build_abe-glibc/console.log.xz | Bin 224320 -> 229640 bytes
08-build_abe-stage2/console.log.xz | Bin 203292 -> 207540 bytes
10-benchmark/benchmark-start.log | 2 +-
10-benchmark/benchmark.log | 113 +-
10-benchmark/console.log.xz | Bin 2260 -> 3188 bytes
11-check_regression/console.log.xz | Bin 1956 -> 1988 bytes
11-check_regression/results-0.csv | 197 +-
11-check_regression/results-1.csv | 203 +-
11-check_regression/results-brief.csv | 58 +-
11-check_regression/results-compare.csv | 34 +-
11-check_regression/results-full.csv | 205 +-
11-check_regression/results.csv | 70 +-
11-check_regression/results.log | 5146 ++++++++++++++++---------------
12-update_baseline/console.log | 3316 ++++++++++----------
12-update_baseline/extra-bisect-params | 2 +-
12-update_baseline/results-1.csv | 203 +-
12-update_baseline/results-brief.csv | 58 +-
12-update_baseline/results-compare.csv | 2 +-
12-update_baseline/results-full.csv | 201 +-
12-update_baseline/results.csv | 70 +-
12-update_baseline/results.log | 3492 +++++++++++----------
12-update_baseline/results.regressions | 3 +-
jenkins/manifest.sh | 17 +-
results_id | 2 +-
29 files changed, 6743 insertions(+), 6651 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_O3
in repository toolchain/ci/base-artifacts.
discards b11bc49d8 0: update: binutils-gcc: 2
new b6c734efe 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 (b11bc49d8)
\
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 1600 -> 1684 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2752 bytes
04-build_abe-binutils/console.log.xz | Bin 65684 -> 64528 bytes
05-build_abe-bootstrap_O3/console.log.xz | Bin 466828 -> 461916 bytes
06-check_regression/console.log.xz | Bin 400 -> 400 bytes
07-update_baseline/console.log | 20 ++++++++++----------
jenkins/manifest.sh | 14 +++++++-------
7 files changed, 17 insertions(+), 17 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 0b99a66053f gdb: Enable finish command and inferior calls for _Float16 [...]
new 7a6cb96b710 [gdb/testsuite] Add untested case in gdb.gdb/complaints.exp
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.gdb/complaints.exp | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
--
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-aarch64
in repository toolchain/ci/base-artifacts.
discards 0aabc0100 0: update: binutils-gcc-linux-glibc-gdb: 6
new 06ca13a01 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 (0aabc0100)
\
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 1508 -> 1852 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes
04-build_abe-binutils/console.log.xz | Bin 51428 -> 51312 bytes
05-build_abe-gcc/console.log.xz | Bin 201240 -> 200084 bytes
06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes
07-build_abe-linux/console.log.xz | Bin 9544 -> 9416 bytes
08-build_abe-glibc/console.log.xz | Bin 236328 -> 237000 bytes
09-build_abe-gdb/console.log.xz | Bin 44032 -> 44276 bytes
10-check_regression/console.log.xz | Bin 404 -> 400 bytes
11-update_baseline/console.log | 40 +++++++++++++++++------------------
jenkins/manifest.sh | 22 +++++++++----------
11 files changed, 31 insertions(+), 31 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 master
in repository toolchain/gcc-compare-results.
from f734f68 From https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc-bisec [...]
new 64ad75f From https://ci.linaro.org/job/tcwg_gnu_native_check_gcc-bise [...]
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:
...tcwg_gnu_native_check_gcc-release-aarch64.xfail | 32 ++++++++++++++++++++++
1 file changed, 32 insertions(+)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.