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-arm-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards f15fbb2f0 0: update: llvm-linux: 16
new 0e92a1c32 0: update: llvm-linux: 16
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 (f15fbb2f0)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-l [...]
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 | 171 +-
02-build_llvm/console.log | 12928 ++++++++++++++--------------
03-build_linux/console.log | 622 +-
05-check_regression/console.log | 30 +-
05-check_regression/results.regressions | 20 +-
06-update_baseline/console.log | 10 +-
06-update_baseline/results.regressions | 20 +-
console.log | 13761 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
9 files changed, 13763 insertions(+), 13811 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-arm-lts-defconfig
in repository toolchain/ci/binutils-gdb.
from 7cfd74cfc6 Fix gdb.multi/multi-re-run.exp with native-gdbserver
adds 966dc1a27c Automatic date update in version.in
adds 7f32a4d5ae Stop considering hw and sw breakpoint locations duplicates ( [...]
adds 83d27139ca binutils: Add myself as maintainer for OpenRISC
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
binutils/ChangeLog | 4 +
binutils/MAINTAINERS | 1 +
gdb/ChangeLog | 22 ++
gdb/breakpoint.c | 253 ++++++++++++++-------
gdb/testsuite/ChangeLog | 5 +
.../gdb.base/hw-sw-break-same-address.exp | 73 ++++++
7 files changed, 273 insertions(+), 87 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/hw-sw-break-same-address.exp
--
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-arm-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 7dbd8dcc2 0: update: binutils-gcc-linux: boot
new 61a7c956d 0: update: binutils-gcc-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 (7dbd8dcc2)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-lt [...]
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 | 130 +-
02-prepare_abe/console.log | 434 +-
03-build_abe-binutils/console.log | 11707 +++++-----
04-build_abe-stage1/console.log | 20405 ++++++++---------
05-build_linux/console.log | 3118 +--
06-boot_linux/console.log | 386 +-
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 | 36184 +++++++++++++++---------------
jenkins/manifest.sh | 15 +-
12 files changed, 36172 insertions(+), 36215 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-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 95748dd39 0: update: llvm-linux: boot
new ee2a33d88 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 (95748dd39)
\
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 | 130 +-
02-build_llvm/console.log | 12730 ++++++++--------
03-build_linux/console.log | 17690 +++++++++++-----------
04-boot_linux/console.log | 4 +-
05-check_regression/console.log | 30 +-
06-update_baseline/console.log | 12 +-
console.log | 30596 +++++++++++++++++++-------------------
jenkins/manifest.sh | 16 +-
8 files changed, 30603 insertions(+), 30605 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-arm-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 29cdbb711 0: update: llvm-linux: all
new c20aac047 0: update: llvm-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 (29cdbb711)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-n [...]
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 | 175 +-
02-build_llvm/console.log | 12960 ++++++++++++++++++-----------------
03-build_linux/console.log | 808 +--
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 6 +-
06-update_baseline/console.log | 12 +-
console.log | 13963 +++++++++++++++++++-------------------
jenkins/manifest.sh | 12 +-
8 files changed, 13947 insertions(+), 13991 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.