This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_cross/gnu-release-aarch64-check_cross
in repository toolchain/ci/base-artifacts.
discards de13d64da 0: update: glibc-61e8ae9b660d98d3a139d3dd617dea16de798f88: 1
new bc12b709c 0: update: qemu-99c5874a9b6c9f70aef285d6eff85d4f46de3c52: 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 (de13d64da)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_cross/gnu-release-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 | 191 +-
02-prepare_abe/console.log | 236 +-
03-build_abe-binutils/console.log | 10199 +--
04-build_abe-stage1/console.log | 13362 +--
05-build_abe-linux/console.log | 296 +-
06-build_abe-glibc/console.log | 39815 ++++-----
07-build_abe-stage2/console.log | 39427 ++++----
08-build_abe-qemu/console.log | 2392 +-
09-build_abe-dejagnu/console.log | 328 +-
10-build_abe-check_gcc/console.log | 30897 ++++---
11-check_regression/console.log | 57 +-
11-check_regression/results.regressions | 6 +-
12-update_baseline/console.log | 156 +-
12-update_baseline/results.regressions | 6 +-
console.log | 139250 ++++++++++++++---------------
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 1753792 -> 1753084 bytes
sumfiles/g++.sum | 70 +-
sumfiles/gcc.log.xz | Bin 1820244 -> 1818384 bytes
sumfiles/gcc.sum | 292 +-
sumfiles/gfortran.log.xz | Bin 734252 -> 734396 bytes
sumfiles/gfortran.sum | 28 +-
sumfiles/libatomic.log.xz | Bin 2060 -> 2056 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 101640 -> 101636 bytes
sumfiles/libgomp.sum | 18 +-
sumfiles/libitm.log.xz | Bin 2344 -> 2348 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 354268 -> 352788 bytes
sumfiles/libstdc++.sum | 8 +-
30 files changed, 137734 insertions(+), 139318 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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 3f27f9b05 0: update: binutils-gcc-linux: all
new 097ef6fff 0: update: binutils-gcc-linux: all
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 (3f27f9b05)
\
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 | 166 +-
02-prepare_abe/console.log | 424 +-
03-build_abe-binutils/console.log | 11482 +++++-----
04-build_abe-stage1/console.log | 16136 +++++++-------
05-build_linux/console.log | 6210 +++---
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 2 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 2 +-
08-update_baseline/results.regressions | 2 +-
console.log | 34438 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
12 files changed, 34367 insertions(+), 34511 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 azanella/futex-refactor
in repository glibc.
discards f92702293d y2038: Convert aio_suspend to support 64 bit time
new c435196bf2 y2038: Convert aio_suspend to support 64 bit time
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 (f92702293d)
\
N -- N -- N refs/heads/azanella/futex-refactor (c435196bf2)
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:
sysdeps/pthread/aio_suspend.c | 47 ++++++-------------------------------------
1 file changed, 6 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_cross/gnu-release-aarch64-check_cross
in repository toolchain/ci/base-artifacts.
discards fe2ddd2cc 0: update: gcc-23114fd9ba06f315276dfbc0dd5decbadfb423de: 1
new de13d64da 0: update: glibc-61e8ae9b660d98d3a139d3dd617dea16de798f88: 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 (fe2ddd2cc)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_cross/gnu-release-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 | 182 +-
02-prepare_abe/console.log | 236 +-
03-build_abe-binutils/console.log | 10138 +--
04-build_abe-stage1/console.log | 13723 ++-
05-build_abe-linux/console.log | 294 +-
06-build_abe-glibc/console.log | 39821 +++++----
07-build_abe-stage2/console.log | 40451 +++++----
08-build_abe-qemu/console.log | 2160 +-
09-build_abe-dejagnu/console.log | 328 +-
10-build_abe-check_gcc/console.log | 30592 ++++---
11-check_regression/console.log | 300 +-
11-check_regression/results.regressions | 28 +-
12-update_baseline/console.log | 199 +-
12-update_baseline/results.regressions | 28 +-
console.log | 138760 +++++++++++++++--------------
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 1748060 -> 1753792 bytes
sumfiles/g++.sum | 70 +-
sumfiles/gcc.log.xz | Bin 1820308 -> 1820244 bytes
sumfiles/gcc.sum | 292 +-
sumfiles/gfortran.log.xz | Bin 732184 -> 734252 bytes
sumfiles/gfortran.sum | 28 +-
sumfiles/libatomic.log.xz | Bin 2056 -> 2060 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 101652 -> 101640 bytes
sumfiles/libgomp.sum | 18 +-
sumfiles/libitm.log.xz | Bin 2348 -> 2344 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 352620 -> 354268 bytes
sumfiles/libstdc++.sum | 8 +-
30 files changed, 139825 insertions(+), 137849 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 azanella/futex-refactor
in repository glibc.
at f92702293d y2038: Convert aio_suspend to support 64 bit time
This branch includes the following new commits:
new c71301052e linux: Remove unused internal futex functions
new 468ebb8804 nptl: Remove futex_wait_cancelable
new 49406c47c5 nptl: Remove clockwait_tid
new 808735547d linux: Extend __futex_abstimed_wait_cancelable64 comment
new aaa99af378 linux: nptl: Consolidate __futex_abstimed_wait_{cancelable}64
new d300f941a8 linux: nptl: Remove _futex_clock_wait_bitset64
new 277e843a9f linux: nptl: Replace __futex_clocklock_wait64 with __futex_a [...]
new bff7f266fb linux: nptl: Replace lll_timedwait with __futex_abstimed_wait64
new 2da7124e7f linux: nptl: Replace lll_futex_{timed_}wait by futex-internal.h
new 4c9675eaf1 linux: nptl: Replace lll_futex_supported_clockid with futex- [...]
new 7c5c9eb91a nptl: Replace lll_futex_wake with futex-internal.h
new 96d0e49f01 nptl: Return EINVAL for pthread_mutex_clocklock/PI with CLOC [...]
new 686d38b35e linux: Return EINVAL for invalid clock for pthread_clockjoin_np
new f92702293d y2038: Convert aio_suspend to support 64 bit time
The 14 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.
--
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-aarch64-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 282a47beb 0: update: llvm-linux: boot
new 0a6b42776 0: update: llvm-linux: 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 (282a47beb)
\
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 | 162 +-
02-build_llvm/console.log | 12718 ++++++++--------
03-build_linux/console.log | 18412 +++++++++++-----------
04-boot_linux/console.log | 4 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 10 +-
console.log | 31308 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
8 files changed, 31312 insertions(+), 31312 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.