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-next-defconfig
in repository toolchain/ci/base-artifacts.
discards 284b4ef96 0: update: qemu-41192db338588051f21501abc13743e62b0a5605: boot
new efe4d5120 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 (284b4ef96)
\
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 | 177 +-
02-prepare_abe/console.log | 444 +-
03-build_abe-binutils/console.log | 11764 +++++-----
04-build_abe-stage1/console.log | 16188 ++++++-------
05-build_linux/console.log | 568 +-
06-build_abe-qemu/console.log | 6764 +++---
07-boot_linux/console.log | 408 +-
08-check_regression/console.log | 12 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 18 +-
09-update_baseline/results.regressions | 2 +-
console.log | 36323 +++++++++++++++---------------
jenkins/manifest.sh | 24 +-
results | 2 +-
14 files changed, 37094 insertions(+), 35602 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-arm-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards b6bc033a1 0: update: gcc-a8a453d82e2c2ce04f40742327033214b9d3582c: all
new ec41dddd9 0: update: qemu-386b2a5767f7642521cd07930c681ec8a6057e60: 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 (b6bc033a1)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 | 182 +-
02-prepare_abe/console.log | 434 +-
03-build_abe-binutils/console.log | 10186 ++++-----
04-build_abe-stage1/console.log | 18329 ++++++++--------
05-build_linux/console.log | 418 +-
06-build_abe-qemu/console.log | 4430 ++--
07-boot_linux/console.log | 6 +-
08-check_regression/console.log | 20 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 22 +-
09-update_baseline/results.regressions | 2 +-
console.log | 34247 +++++++++++++++---------------
jenkins/manifest.sh | 10 +-
13 files changed, 34125 insertions(+), 34163 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-allyesconfig
in repository toolchain/ci/qemu.
from 41192db338 Merge remote-tracking branch 'remotes/ehabkost-gl/tags/machi [...]
adds 593621f36b readline: Fix possible array index out of bounds in readline [...]
adds e551455f1e Merge remote-tracking branch 'remotes/stefanha-gitlab/tags/b [...]
No new revisions were added by this update.
Summary of changes:
util/readline.c | 3 +++
1 file changed, 3 insertions(+)
--
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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards c3f95b1d3 2: update: gcc-2e96eec614e8e73f76df3a3f1e199ce36b747bac: 19203
new 2cc938708 2: update: qemu-e551455f1e7a3d7eee9e11e2903e4050bc5511ae: 19203
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 (c3f95b1d3)
\
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 | 129 +-
02-prepare_abe/console.log | 276 +-
03-build_abe-binutils/console.log | 11024 ++++-----
04-build_abe-stage1/console.log | 16269 +++++++------
05-build_linux/console.log | 8944 ++++----
08-check_regression/console.log | 2 +-
08-check_regression/results.regressions | 4 +-
09-update_baseline/console.log | 74 +-
09-update_baseline/results.regressions | 4 +-
console.log | 36718 +++++++++++++++---------------
jenkins/manifest.sh | 8 +-
11 files changed, 36566 insertions(+), 36886 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-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 5d648da88 0: update: binutils-9cab1e193165a1f815120b19ce981133ed0cfe51: boot
new 328756a3c 0: update: gcc-a8a453d82e2c2ce04f40742327033214b9d3582c: 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 (5d648da88)
\
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 | 157 +-
02-prepare_abe/console.log | 404 +-
03-build_abe-binutils/console.log | 11367 ++++++-----
04-build_abe-stage1/console.log | 13672 +++++++-------
05-build_linux/console.log | 324 +-
06-build_abe-qemu/console.log | 4332 ++---
07-boot_linux/console.log | 4 +-
08-check_regression/console.log | 2 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 10 +-
09-update_baseline/results.regressions | 2 +-
console.log | 30280 +++++++++++++++---------------
jenkins/manifest.sh | 10 +-
13 files changed, 30033 insertions(+), 30533 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-9
in repository gcc.
from b7be64f9079 Fortran: Delay vtab generation until after parsing [PR92587]
new 2bfcf6011a6 PR fortran/96381 - invalid read in gfc_find_derived_vtab
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/fortran/class.c | 4 +++-
1 file changed, 3 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 releases/gcc-10
in repository gcc.
from 6f3f06e431c Fortran: Delay vtab generation until after parsing [PR92587]
new 78ff090d0a0 PR fortran/96381 - invalid read in gfc_find_derived_vtab
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/fortran/class.c | 4 +++-
1 file changed, 3 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-stable-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 75799c371 0: update: gcc-a8a453d82e2c2ce04f40742327033214b9d3582c: all
new 49c0a1eec 0: update: qemu-386b2a5767f7642521cd07930c681ec8a6057e60: 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 (75799c371)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-s [...]
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 | 127 +-
02-prepare_abe/console.log | 428 +-
03-build_abe-binutils/console.log | 10486 ++++-----
04-build_abe-stage1/console.log | 18305 ++++++++--------
05-build_linux/console.log | 384 +-
06-build_abe-qemu/console.log | 4420 ++--
07-boot_linux/console.log | 2 +-
08-check_regression/console.log | 8 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 2 +-
09-update_baseline/results.regressions | 2 +-
console.log | 34168 +++++++++++++++---------------
jenkins/manifest.sh | 8 +-
13 files changed, 34159 insertions(+), 34183 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-arm-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 122c3534e 0: update: gcc-a8a453d82e2c2ce04f40742327033214b9d3582c: all
new bdd50fc55 0: update: qemu-386b2a5767f7642521cd07930c681ec8a6057e60: 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 (122c3534e)
\
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 | 127 +-
02-prepare_abe/console.log | 424 +-
03-build_abe-binutils/console.log | 10702 ++++-----
04-build_abe-stage1/console.log | 18336 ++++++++--------
05-build_linux/console.log | 406 +-
06-build_abe-qemu/console.log | 4461 ++--
07-boot_linux/console.log | 2 +-
08-check_regression/console.log | 18 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 12 +-
09-update_baseline/results.regressions | 2 +-
console.log | 34488 +++++++++++++++---------------
jenkins/manifest.sh | 8 +-
13 files changed, 34478 insertions(+), 34510 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.