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 6d56a4c5 2: update: binutils-gcc-linux: 17559
new 0c305733 2: update: binutils-gcc-linux: 17559
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 (6d56a4c5)
\
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 | 90 +-
02-prepare_abe/console.log | 424 +-
03-build_abe-binutils/console.log | 12157 ++++++------
04-build_abe-stage1/console.log | 16158 ++++++++--------
05-build_linux/console.log | 1080 +-
07-check_regression/console.log | 14 +-
07-check_regression/results.regressions | 20 +-
08-update_baseline/console.log | 64 +-
08-update_baseline/results.regressions | 20 +-
console.log | 29987 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
11 files changed, 30036 insertions(+), 29990 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-release-arm-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 0d88294a 2: update: llvm-ef32c611aa214dea855364efd7ba451ec5ec3f74: 20963
new 74eb72a6 2: update: llvm-linux: 20965
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 (0d88294a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-arm- [...]
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 | 226 +-
02-build_llvm/console.log | 12654 +++++++++++++--------------
03-build_linux/console.log | 733 +-
05-check_regression/console.log | 68 +-
05-check_regression/results.regressions | 8 +-
06-update_baseline/console.log | 106 +-
06-update_baseline/results.regressions | 8 +-
console.log | 13787 +++++++++++++++---------------
jenkins/manifest.sh | 10 +-
results | 2 +-
10 files changed, 13951 insertions(+), 13651 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-defconfig
in repository toolchain/ci/base-artifacts.
discards 3ab15f7a 0: update: binutils-gcc-linux: boot
new fde7af0f 0: update: binutils-gcc: 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 (3ab15f7a)
\
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 | 216 +-
02-prepare_abe/console.log | 418 +-
03-build_abe-binutils/console.log | 11472 ++++++-------
04-build_abe-stage1/console.log | 13944 +++++++--------
05-build_linux/console.log | 590 +-
06-boot_linux/console.log | 482 +-
07-check_regression/console.log | 18 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 22 +-
08-update_baseline/results.regressions | 2 +-
console.log | 27162 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
12 files changed, 27085 insertions(+), 27255 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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards b311c046 2: update: llvm-linux: 18953
new 5adf1353 2: update: llvm-linux: 18953
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 (b311c046)
\
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 | 58 +-
02-build_llvm/console.log | 13362 +++++++++++++--------------
03-build_linux/console.log | 860 +-
05-check_regression/console.log | 34 +-
05-check_regression/results.regressions | 12 +-
06-update_baseline/console.log | 138 +-
06-update_baseline/results.regressions | 12 +-
console.log | 14452 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
9 files changed, 14474 insertions(+), 14466 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.