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-aarch64-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards a169d23a4 2: update: binutils-llvm-linux-qemu: 40
new 52cf14168 2: update: binutils-llvm-linux-qemu: 40
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 (a169d23a4)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-aarc [...]
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 1800 -> 1572 bytes
02-prepare_abe/console.log.xz | Bin 2792 -> 2788 bytes
03-build_abe-binutils/console.log.xz | Bin 42692 -> 43172 bytes
04-build_llvm/console.log.xz | Bin 58020 -> 58096 bytes
05-build_abe-qemu/console.log.xz | Bin 30764 -> 30692 bytes
06-build_linux/console.log.xz | Bin 4072 -> 3852 bytes
08-check_regression/console.log.xz | Bin 476 -> 492 bytes
09-update_baseline/console.log | 86 +++++++++++++++++------------------
jenkins/manifest.sh | 8 ++--
9 files changed, 47 insertions(+), 47 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_bootstrap/master-arm-check_bootstrap_lto
in repository toolchain/ci/base-artifacts.
discards 1e74e7d1a 0: update: binutils-gcc: 1
new 7b69438bd 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 (1e74e7d1a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check_bootstrap/mast [...]
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 1532 -> 1544 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 52488 -> 51844 bytes
04-build_abe-bootstrap_lto/console.log.xz | Bin 491408 -> 489164 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3808 bytes
06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2436 -> 2432 bytes
07-check_regression/console.log.xz | Bin 4936 -> 3596 bytes
07-check_regression/extra-bisect-params | 1 -
07-check_regression/fails.sum | 16 -
07-check_regression/results.compare | 25 +-
07-check_regression/results.compare2 | 470 +--
07-check_regression/results.regressions | 36 -
08-update_baseline/console.log | 724 +---
08-update_baseline/extra-bisect-params | 1 -
08-update_baseline/fails.sum | 16 -
08-update_baseline/results.compare | 25 +-
08-update_baseline/results.compare2 | 470 +--
08-update_baseline/results.regressions | 36 -
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 2824132 -> 2762804 bytes
sumfiles/g++.sum | 168 +-
sumfiles/gcc.log.xz | Bin 2415788 -> 2432188 bytes
sumfiles/gcc.sum | 4604 ++++++++++++-----------
sumfiles/gfortran.log.xz | Bin 937124 -> 933492 bytes
sumfiles/gfortran.sum | 48 +-
sumfiles/libatomic.log.xz | Bin 2312 -> 2304 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 193884 -> 195032 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 468564 -> 455904 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 2800 insertions(+), 3888 deletions(-)
delete mode 100644 07-check_regression/extra-bisect-params
delete mode 100644 07-check_regression/fails.sum
delete mode 100644 07-check_regression/results.regressions
delete mode 100644 08-update_baseline/extra-bisect-params
delete mode 100644 08-update_baseline/fails.sum
delete 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-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards b902a8b54 2: update: binutils-llvm-linux-qemu: 19900
new ade9b0b4a 2: update: binutils-llvm-linux-qemu: 19900
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 (b902a8b54)
\
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 1592 -> 1616 bytes
02-prepare_abe/console.log.xz | Bin 2780 -> 2784 bytes
03-build_abe-binutils/console.log.xz | Bin 41940 -> 42116 bytes
04-build_llvm/console.log.xz | Bin 57188 -> 57652 bytes
05-build_abe-qemu/console.log.xz | Bin 30332 -> 30332 bytes
06-build_linux/console.log.xz | Bin 5080 -> 5036 bytes
08-check_regression/console.log.xz | Bin 476 -> 476 bytes
09-update_baseline/console.log | 22 +++++++++++-----------
jenkins/manifest.sh | 8 ++++----
9 files changed, 15 insertions(+), 15 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_cross_check_gcc/master-arm
in repository toolchain/ci/base-artifacts.
discards 623f9d698 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1
new 068c93397 0: update: binutils-gcc-linux-glibc-gdb-qemu: 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 (623f9d698)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1524 -> 1544 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 29924 -> 30348 bytes
04-build_abe-stage1/console.log.xz | Bin 90908 -> 90716 bytes
05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes
06-build_abe-linux/console.log.xz | Bin 9740 -> 9684 bytes
07-build_abe-glibc/console.log.xz | Bin 232308 -> 232636 bytes
08-build_abe-stage2/console.log.xz | Bin 228988 -> 229920 bytes
09-build_abe-gdb/console.log.xz | Bin 36720 -> 37524 bytes
10-build_abe-qemu/console.log.xz | Bin 30884 -> 30504 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3872 bytes
12-build_abe-check_gcc/console.log.xz | Bin 3556 -> 2452 bytes
13-check_regression/console.log.xz | Bin 2524 -> 2796 bytes
13-check_regression/results.compare | 24 +-
13-check_regression/results.compare2 | 61 +-
14-update_baseline/console.log | 259 ++--
14-update_baseline/results.compare | 24 +-
14-update_baseline/results.compare2 | 61 +-
jenkins/manifest.sh | 18 +-
sumfiles/g++.log.xz | Bin 2641528 -> 2607140 bytes
sumfiles/g++.sum | 156 ++-
sumfiles/gcc.log.xz | Bin 2161608 -> 2169904 bytes
sumfiles/gcc.sum | 2326 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 872736 -> 871524 bytes
sumfiles/gfortran.sum | 48 +-
sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 184224 -> 184260 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 419488 -> 418420 bytes
sumfiles/libstdc++.sum | 16 +-
33 files changed, 1589 insertions(+), 1430 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.