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 4b2c3c6b 0: update: binutils-gcc: 1
new f39a9158 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 (4b2c3c6b)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (f39a9158)
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 1476 -> 1528 bytes
02-prepare_abe/console.log.xz | Bin 2732 -> 2756 bytes
03-build_abe-binutils/console.log.xz | Bin 50492 -> 50852 bytes
04-build_abe-gcc/console.log.xz | Bin 229540 -> 229196 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3856 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2652 -> 2664 bytes
07-check_regression/console.log.xz | Bin 2808 -> 3340 bytes
07-check_regression/extra-bisect-params | 1 +
07-check_regression/fails.sum | 8 +
07-check_regression/results.compare | 27 +-
07-check_regression/results.compare2 | 145 +-
07-check_regression/results.regressions | 28 +
08-update_baseline/console.log | 525 ++--
08-update_baseline/extra-bisect-params | 1 +
08-update_baseline/fails.sum | 8 +
08-update_baseline/results.compare | 27 +-
08-update_baseline/results.compare2 | 145 +-
08-update_baseline/results.regressions | 28 +
jenkins/manifest.sh | 14 +-
sumfiles/g++.log.xz | Bin 2766800 -> 2761432 bytes
sumfiles/g++.sum | 141 +-
sumfiles/gcc.log.xz | Bin 2335512 -> 2346276 bytes
sumfiles/gcc.sum | 4395 ++++++++++++++++---------------
sumfiles/gfortran.log.xz | Bin 902720 -> 897428 bytes
sumfiles/gfortran.sum | 40 +-
sumfiles/libatomic.log.xz | Bin 2176 -> 2164 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 199024 -> 199152 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2536 -> 2544 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 455940 -> 451936 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 2919 insertions(+), 2650 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-release-arm-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards a240a464 3: reset: linux-62eb29526b48d20704668a2fdf97a49d01bf52ce: 20209
discards e3c0201a 2: update: linux-5191290407668028179f2544a11ae9b57f0bcf07: 20222
new 577b69c2 2: update: linux-5191290407668028179f2544a11ae9b57f0bcf07: 20222
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 (a240a464)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/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.xz | Bin 1624 -> 1712 bytes
02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 28932 -> 28900 bytes
04-build_llvm/console.log.xz | Bin 61312 -> 61556 bytes
05-build_abe-qemu/console.log.xz | Bin 31720 -> 31520 bytes
06-build_linux/console.log.xz | Bin 5212 -> 5304 bytes
08-check_regression/console.log.xz | Bin 1248 -> 484 bytes
08-check_regression/jira-body.txt | 2 -
08-check_regression/mail-body.txt | 37 ------------
08-check_regression/mail-subject.txt | 1 -
08-check_regression/results.regressions | 11 ----
08-check_regression/trigger-bisect | 2 -
09-update_baseline/console.log | 104 +++++++++++++++++++++++++++++---
jenkins/manifest.sh | 10 +--
mail/jira-body.txt | 5 --
mail/mail-body.txt | 40 ------------
mail/mail-subject.txt | 1 -
reset-baseline | 0
results | 13 +---
19 files changed, 103 insertions(+), 123 deletions(-)
delete mode 100644 08-check_regression/jira-body.txt
delete mode 100644 08-check_regression/mail-body.txt
delete mode 100644 08-check_regression/mail-subject.txt
delete mode 100644 08-check_regression/results.regressions
delete mode 100644 08-check_regression/trigger-bisect
delete mode 100644 mail/jira-body.txt
delete mode 100644 mail/mail-body.txt
delete mode 100644 mail/mail-subject.txt
delete mode 100644 reset-baseline
--
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_llvm_tx1/llvm-master-aarch64-spec2k6-O3_LTO
in repository toolchain/ci/base-artifacts.
discards ae1acefe 7: update: linux-79714efdeed8e6dc41147c31d44f31a1a17cc6da: 1
discards e6221b1c 6: reset: llvm-ee4ba9f3a182397c60e17f14823eb22b2e5831c7: 1
new ae012b02 6: reset: : 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 (ae1acefe)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_llvm_tx1/llvm-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 1628 -> 1760 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 30548 -> 30600 bytes
04-build_abe-stage1/console.log.xz | Bin 76052 -> 76288 bytes
05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes
06-build_abe-linux/console.log.xz | Bin 9112 -> 10724 bytes
07-build_abe-glibc/console.log.xz | Bin 237028 -> 237748 bytes
08-build_abe-stage2/console.log.xz | Bin 182404 -> 183816 bytes
09-build_llvm-true/console.log.xz | Bin 61588 -> 61756 bytes
10-benchmark/benchmark-build.log | 60 +-
10-benchmark/benchmark.log | 58 +-
10-benchmark/console.log.xz | Bin 3376 -> 3392 bytes
11-check_regression/console.log.xz | Bin 2832 -> 2824 bytes
11-check_regression/results-0.csv | 469 +-
11-check_regression/results-1.csv | 2275 +-
11-check_regression/results-brief.csv | 34 +-
11-check_regression/results-full.csv | 94 +-
11-check_regression/results-perf-0.csv | 91 +-
11-check_regression/results-perf-1.csv | 90 +-
11-check_regression/results-size-0.csv | 187048 ++++++++--------
11-check_regression/results-size-1.csv | 201706 +++++++++---------
11-check_regression/results-vect-0.csv | 16 +-
11-check_regression/results-vect-1.csv | 22 +-
11-check_regression/results.csv | 42 +-
11-check_regression/results.log | 2724 +-
12-update_baseline/console.log | 4633 +-
12-update_baseline/exe.regressions | 2 +-
12-update_baseline/jira-body.txt | 2 +-
12-update_baseline/mail-body.txt | 2 +-
12-update_baseline/results-1.csv | 2275 +-
12-update_baseline/results-brief.csv | 34 +-
12-update_baseline/results-full.csv | 90 +-
12-update_baseline/results-perf-1.csv | 90 +-
12-update_baseline/results-size-1.csv | 201706 +++++++++---------
12-update_baseline/results-vect-1.csv | 22 +-
12-update_baseline/results.csv | 42 +-
12-update_baseline/results.log | 2042 +-
12-update_baseline/results.regressions | 2 +-
.../top-artifacts/save-temps/400.perlbench.tar.xz | Bin 400540 -> 396944 bytes
.../top-artifacts/save-temps/401.bzip2.tar.xz | Bin 44020 -> 43912 bytes
.../top-artifacts/save-temps/403.gcc.tar.xz | Bin 1197020 -> 1189256 bytes
.../top-artifacts/save-temps/429.mcf.tar.xz | Bin 22352 -> 22328 bytes
.../top-artifacts/save-temps/444.namd.tar.xz | Bin 46264 -> 46204 bytes
.../top-artifacts/save-temps/445.gobmk.tar.xz | Bin 612372 -> 612168 bytes
.../top-artifacts/save-temps/447.dealII.tar.xz | Bin 864332 -> 864384 bytes
.../top-artifacts/save-temps/450.soplex.tar.xz | Bin 199620 -> 197588 bytes
.../top-artifacts/save-temps/453.povray.tar.xz | Bin 455500 -> 452456 bytes
.../top-artifacts/save-temps/456.hmmer.tar.xz | Bin 122084 -> 121852 bytes
.../top-artifacts/save-temps/458.sjeng.tar.xz | Bin 51644 -> 51688 bytes
.../top-artifacts/save-temps/462.libquantum.tar.xz | Bin 23612 -> 23544 bytes
.../top-artifacts/save-temps/470.lbm.tar.xz | Bin 15824 -> 15808 bytes
.../top-artifacts/save-temps/471.omnetpp.tar.xz | Bin 333388 -> 330568 bytes
.../top-artifacts/save-temps/473.astar.tar.xz | Bin 43132 -> 42960 bytes
.../top-artifacts/save-temps/482.sphinx3.tar.xz | Bin 93632 -> 93560 bytes
.../top-artifacts/save-temps/483.xalancbmk.tar.xz | Bin 3159760 -> 3223088 bytes
jenkins/manifest.sh | 9 +-
reset-baseline | 0
results | 2 +-
results_id | 2 +-
save-temps/400.perlbench.tar.xz | Bin 400540 -> 396944 bytes
save-temps/401.bzip2.tar.xz | Bin 44020 -> 43912 bytes
save-temps/403.gcc.tar.xz | Bin 1197020 -> 1189256 bytes
save-temps/429.mcf.tar.xz | Bin 22352 -> 22328 bytes
save-temps/444.namd.tar.xz | Bin 46264 -> 46204 bytes
save-temps/445.gobmk.tar.xz | Bin 612372 -> 612168 bytes
save-temps/447.dealII.tar.xz | Bin 864332 -> 864384 bytes
save-temps/450.soplex.tar.xz | Bin 199620 -> 197588 bytes
save-temps/453.povray.tar.xz | Bin 455500 -> 452456 bytes
save-temps/456.hmmer.tar.xz | Bin 122084 -> 121852 bytes
save-temps/458.sjeng.tar.xz | Bin 51644 -> 51688 bytes
save-temps/462.libquantum.tar.xz | Bin 23612 -> 23544 bytes
save-temps/470.lbm.tar.xz | Bin 15824 -> 15808 bytes
save-temps/471.omnetpp.tar.xz | Bin 333388 -> 330568 bytes
save-temps/473.astar.tar.xz | Bin 43132 -> 42960 bytes
save-temps/482.sphinx3.tar.xz | Bin 93632 -> 93560 bytes
save-temps/483.xalancbmk.tar.xz | Bin 3159760 -> 3223088 bytes
76 files changed, 299384 insertions(+), 306300 deletions(-)
create mode 100644 reset-baseline
--
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_ubsan
in repository toolchain/ci/base-artifacts.
discards 252efc96 2: update: binutils-gcc: 0
new f58beb31 2: update: binutils-gcc: 0
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 (252efc96)
\
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 1504 -> 1540 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes
04-build_abe-binutils/console.log.xz | Bin 24424 -> 24996 bytes
06-check_regression/console.log.xz | Bin 412 -> 412 bytes
07-update_baseline/console.log | 120 +++++++++++++++++------------------
jenkins/manifest.sh | 12 ++--
6 files changed, 66 insertions(+), 66 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_llvm_tx1/llvm-release-aarch64-spec2k6-O3_LTO
in repository toolchain/ci/binutils-gdb.
from 4a50e8e714 Automatic date update in version.in
adds 5bb1199bbe Automatic date update in version.in
adds 907a9b092a Automatic date update in version.in
adds 72a6a32099 Automatic date update in version.in
adds 2de7516720 Automatic date update in version.in
adds 06ef3111fd Automatic date update in version.in
adds 158dafe913 Automatic date update in version.in
No new revisions were added by this update.
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.