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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards f2c4fd69 0: update: llvm-linux: all
new 4c2098d7 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 (f2c4fd69)
\
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 | 170 +-
02-build_llvm/console.log | 12702 +++++++++++++++++------------------
03-build_linux/console.log | 812 ++-
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 15 +-
06-update_baseline/console.log | 15 +-
console.log | 13716 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
regressions.txt | 2 +
9 files changed, 13731 insertions(+), 13713 deletions(-)
create mode 100644 regressions.txt
--
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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards d3c59e75 2: update: llvm-linux: 18459
new 7ee2e676 2: update: llvm-linux: 18463
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 (d3c59e75)
\
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 | 68 +-
02-build_llvm/console.log | 12761 +++++++++++++++++-----------------
03-build_linux/console.log | 1035 +--
05-check_regression/console.log | 25 +-
06-update_baseline/console.log | 172 +-
console.log | 14061 +++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
regressions.txt | 6 +
results | 2 +-
9 files changed, 14060 insertions(+), 14084 deletions(-)
create mode 100644 regressions.txt
--
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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards ba7b4f5b 0: update: binutils-gcc-linux: all
new 2fe54315 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 (ba7b4f5b)
\
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 | 132 +-
02-prepare_abe/console.log | 438 +-
03-build_abe-binutils/console.log | 11776 ++++++------
04-build_abe-stage1/console.log | 15825 ++++++++--------
05-build_linux/console.log | 7811 ++++----
06-boot_linux/console.log | 8 +-
07-check_regression/console.log | 7 +-
08-update_baseline/console.log | 7 +-
console.log | 36034 ++++++++++++++++++------------------
jenkins/manifest.sh | 18 +-
regressions.txt | 4 +
results | 2 +-
12 files changed, 35985 insertions(+), 36077 deletions(-)
create mode 100644 regressions.txt
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.