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-release-arm-next-allnoconfig
in repository toolchain/ci/binutils-gdb.
from 929adb5ce7 Automatic date update in version.in
adds 5a0802e35e Automatic date update in version.in
adds c20c7adbea PR28422, build_id use-after-free
adds ac5145d6df Automatic date update in version.in
adds f7c07ade85 Automatic date update in version.in
adds 6fc54b1d1e Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/format.c | 1 +
bfd/version.h | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
--
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-release-arm-next-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 6cd378be8 0: update: binutils-gcc-linux-qemu: all
new 496ea4006 0: update: binutils-gcc-linux-qemu: 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 (6cd378be8)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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.xz | Bin 1556 -> 1564 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 41696 -> 41928 bytes
04-build_abe-stage1/console.log.xz | Bin 85456 -> 85868 bytes
05-build_abe-qemu/console.log.xz | Bin 29512 -> 29836 bytes
06-build_linux/console.log.xz | Bin 3424 -> 3212 bytes
07-boot_linux/console.log.xz | Bin 496 -> 496 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 22 +++++++++++-----------
10 files changed, 16 insertions(+), 16 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-release-aarch64-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 29dec4dc9 0: update: binutils-gcc-qemu: boot
new 47ce91bee 0: update: linux-080735f6de7479ea07c4811d9115d240ee372271: 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 (29dec4dc9)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 1568 -> 1588 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 42492 -> 42352 bytes
04-build_abe-stage1/console.log.xz | Bin 67968 -> 69080 bytes
05-build_abe-qemu/console.log.xz | Bin 30172 -> 30972 bytes
06-build_linux/console.log.xz | Bin 5188 -> 3276 bytes
07-boot_linux/console.log.xz | Bin 508 -> 508 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 12 +++++-------
results | 2 +-
11 files changed, 7 insertions(+), 9 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 releases/gcc-11
in repository gcc.
from 142ae9f5f06 Daily bump.
new 309827c85f1 var-tracking: Fix a wrong-debug issue caused by my r10-7665 [...]
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:
gcc/var-tracking.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
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 gcc.
from 882d806c1a8 tree-optimization: [PR102622]: wrong code due to signed one [...]
new 9583b26f370 var-tracking: Fix a wrong-debug issue caused by my r10-7665 [...]
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:
gcc/var-tracking.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.