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_check_gcc/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 1b74a32d 0: update: binutils-gcc-linux-glibc-gdb: 1
new c0cfaf3e 0: update: binutils-gcc-linux-glibc-gdb: 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 (1b74a32d)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 1572 -> 1564 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 37988 -> 38220 bytes
04-build_abe-gcc/console.log.xz | Bin 208048 -> 208064 bytes
05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes
06-build_abe-linux/console.log.xz | Bin 9720 -> 8928 bytes
07-build_abe-glibc/console.log.xz | Bin 238084 -> 238224 bytes
08-build_abe-gdb/console.log.xz | Bin 37620 -> 37212 bytes
09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3840 bytes
10-build_abe-check_gcc/console.log.xz | Bin 2720 -> 2608 bytes
11-check_regression/console.log.xz | Bin 7744 -> 3156 bytes
11-check_regression/extra-bisect-params | 2 +-
11-check_regression/fails.sum | 9 +-
11-check_regression/results.compare | 57 +-
11-check_regression/results.compare2 | 1299 +-------
11-check_regression/results.regressions | 57 +-
12-update_baseline/console.log | 1544 +--------
12-update_baseline/extra-bisect-params | 2 +-
12-update_baseline/fails.sum | 9 +-
12-update_baseline/results.compare | 57 +-
12-update_baseline/results.compare2 | 1299 +-------
12-update_baseline/results.regressions | 57 +-
jenkins/manifest.sh | 24 +-
sumfiles/g++.log.xz | Bin 3603600 -> 3610276 bytes
sumfiles/g++.sum | 142 +-
sumfiles/gcc.log.xz | Bin 3156732 -> 3135444 bytes
sumfiles/gcc.sum | 5271 ++++++++++++++++---------------
sumfiles/gfortran.log.xz | Bin 1058732 -> 1053808 bytes
sumfiles/gfortran.sum | 42 +-
sumfiles/libatomic.log.xz | Bin 2280 -> 2276 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 200748 -> 199856 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 432764 -> 423004 bytes
sumfiles/libstdc++.sum | 10 +-
37 files changed, 3044 insertions(+), 6863 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/gnu-master-aarch64-lts-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 1efab4d0 0: update: binutils-gcc-linux-qemu: boot
new 74d19967 0: update: binutils-gcc-linux-qemu: boot
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 (1efab4d0)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-aarch6 [...]
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 1580 -> 1752 bytes
02-prepare_abe/console.log.xz | Bin 2760 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 30692 -> 30168 bytes
04-build_abe-stage1/console.log.xz | Bin 71620 -> 71656 bytes
05-build_abe-qemu/console.log.xz | Bin 31620 -> 31836 bytes
06-build_linux/console.log.xz | Bin 3916 -> 4112 bytes
07-boot_linux/console.log.xz | Bin 504 -> 504 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 18 +++++++++---------
10 files changed, 14 insertions(+), 14 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 linux.
from 080eba785fe1 Merge tag 'char-misc-5.17-rc4' of git://git.kernel.org/pub [...]
new c80b27cfd93b scsi: lpfc: Remove NVMe support if kernel has NVME_FC disabled
new 5852ed2a6a39 scsi: lpfc: Reduce log messages seen after firmware download
new b81b1829e7e3 Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/lin [...]
The 3 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:
drivers/scsi/lpfc/lpfc.h | 13 ++++++++++---
drivers/scsi/lpfc/lpfc_attr.c | 4 ++--
drivers/scsi/lpfc/lpfc_init.c | 2 +-
drivers/scsi/lpfc/lpfc_sli.c | 8 +++++++-
4 files changed, 20 insertions(+), 7 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.