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-arm-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards a36ef70f 2: update: binutils-gcc-linux-qemu: 22312
new 885fec3c 2: update: binutils-gcc-linux-qemu: 22333
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 (a36ef70f)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ne [...]
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 1576 -> 1556 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2752 bytes
03-build_abe-binutils/console.log.xz | Bin 30276 -> 29916 bytes
04-build_abe-stage1/console.log.xz | Bin 89664 -> 89160 bytes
05-build_abe-qemu/console.log.xz | Bin 31028 -> 30508 bytes
06-build_linux/console.log.xz | Bin 16076 -> 16168 bytes
08-check_regression/console.log.xz | Bin 480 -> 484 bytes
09-update_baseline/console.log | 58 +++++++++++++++++------------------
jenkins/manifest.sh | 22 ++++++-------
results | 2 +-
10 files changed, 41 insertions(+), 41 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_build/master-arm
in repository toolchain/ci/qemu.
from 95a3fcc748 Update version for v7.0.0-rc3 release
adds 9569f5cb5b display/qxl-render: fix race condition in qxl_cursor (CVE-20 [...]
adds fa892e9abb ui/cursor: fix integer overflow in cursor_alloc (CVE-2021-4206)
adds dde8689d1f Merge tag 'fixes-20220408-pull-request' of git://git.kraxel. [...]
No new revisions were added by this update.
Summary of changes:
hw/display/qxl-render.c | 9 ++++++++-
hw/display/vmware_vga.c | 2 ++
ui/cursor.c | 8 +++++++-
3 files changed, 17 insertions(+), 2 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_build/master-arm
in repository toolchain/ci/base-artifacts.
discards 499be4a6 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new 5c8e8d13 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
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 (499be4a6)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1540 -> 1720 bytes
02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes
04-build_abe-binutils/console.log.xz | Bin 30824 -> 29916 bytes
05-build_abe-stage1/console.log.xz | Bin 90496 -> 89788 bytes
06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes
07-build_abe-linux/console.log.xz | Bin 9904 -> 9244 bytes
08-build_abe-glibc/console.log.xz | Bin 231636 -> 231828 bytes
09-build_abe-stage2/console.log.xz | Bin 220972 -> 221540 bytes
10-build_abe-gdb/console.log.xz | Bin 37080 -> 37024 bytes
11-build_abe-qemu/console.log.xz | Bin 30948 -> 31272 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 26 +++++++++++++-------------
13 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_kernel/llvm-master-aarch64-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 7faa4250 2: update: qemu-bc6ec396d471d9e4aae7e2ff8b72e11da9a97665: 37
new f8369392 2: update: linux-fa4e78627f15dfb1c16d1f1dab18340ab99f4d15: 37
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 (7faa4250)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-aarch [...]
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 1588 -> 1540 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2748 bytes
03-build_abe-binutils/console.log.xz | Bin 30108 -> 29996 bytes
04-build_llvm/console.log.xz | Bin 63124 -> 62540 bytes
05-build_abe-qemu/console.log.xz | Bin 31412 -> 33012 bytes
06-build_linux/console.log.xz | Bin 5472 -> 3792 bytes
08-check_regression/console.log.xz | Bin 476 -> 476 bytes
09-update_baseline/console.log | 212 +++++++++++++++++------------------
jenkins/manifest.sh | 10 +-
9 files changed, 111 insertions(+), 111 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-aarch64
in repository toolchain/ci/base-artifacts.
discards aa15195c 0: update: gdb-916c9be4a31d91ee0ebbb33efbf87a8e3cf13349: 1
new ea8dfdfa 0: update: glibc-5325233313c66aea13e86f5dd59618e9dd74b510: 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 (aa15195c)
\
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 1616 -> 1624 bytes
02-prepare_abe/console.log.xz | Bin 2760 -> 2780 bytes
03-build_abe-binutils/console.log.xz | Bin 30012 -> 30112 bytes
04-build_abe-stage1/console.log.xz | Bin 72704 -> 73072 bytes
05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes
06-build_abe-linux/console.log.xz | Bin 11016 -> 11228 bytes
07-build_abe-glibc/console.log.xz | Bin 235952 -> 237600 bytes
08-build_abe-stage2/console.log.xz | Bin 199916 -> 199636 bytes
09-build_abe-gdb/console.log.xz | Bin 37280 -> 34564 bytes
10-build_abe-qemu/console.log.xz | Bin 32324 -> 32124 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3880 bytes
12-build_abe-check_gcc/console.log.xz | Bin 2744 -> 2736 bytes
13-check_regression/console.log.xz | Bin 8420 -> 8252 bytes
13-check_regression/extra-bisect-params | 2 +-
13-check_regression/fails.sum | 73 +-
13-check_regression/results.compare | 59 +-
13-check_regression/results.compare2 | 556 ++-
13-check_regression/results.regressions | 46 +-
14-update_baseline/console.log | 817 ++---
14-update_baseline/extra-bisect-params | 2 +-
14-update_baseline/fails.sum | 73 +-
14-update_baseline/results.compare | 59 +-
14-update_baseline/results.compare2 | 556 ++-
14-update_baseline/results.regressions | 46 +-
jenkins/manifest.sh | 6 +-
sumfiles/g++.log.xz | Bin 3342456 -> 3338132 bytes
sumfiles/g++.sum | 161 +-
sumfiles/gcc.log.xz | Bin 2934872 -> 2936632 bytes
sumfiles/gcc.sum | 5913 ++++++++++++++++---------------
sumfiles/gfortran.log.xz | Bin 1021644 -> 1020056 bytes
sumfiles/gfortran.sum | 40 +-
sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 196412 -> 196464 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 407276 -> 409360 bytes
sumfiles/libstdc++.sum | 14 +-
39 files changed, 4254 insertions(+), 4195 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.