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-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards eb4f5ce66 0: update: binutils-gcc-linux: all
new b60d590d9 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 (eb4f5ce66)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ma [...]
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 | 166 +-
02-prepare_abe/console.log | 438 +-
03-build_abe-binutils/console.log | 11611 +++++++------
04-build_abe-stage1/console.log | 20162 +++++++++++-----------
05-build_linux/console.log | 632 +-
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 2 +-
08-update_baseline/console.log | 2 +-
console.log | 33015 ++++++++++++++++++------------------
jenkins/manifest.sh | 16 +-
regressions.txt | 2 +-
11 files changed, 33005 insertions(+), 33043 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-mainline-allmodconfig
in repository toolchain/ci/linux.
from 7557c1b3f715 Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/lin [...]
adds 9e661cedcc0a i2c: jz4780: silence log flood on txabrt
adds 54498e8070e1 i2c: altera: Fix potential integer overflow
adds 38b17afb0ebb macintosh: therm_windtunnel: fix regression when instantia [...]
adds fb279f4e2386 Merge branch 'i2c/for-current-fixed' of git://git.kernel.o [...]
No new revisions were added by this update.
Summary of changes:
drivers/i2c/busses/i2c-altera.c | 2 +-
drivers/i2c/busses/i2c-jz4780.c | 36 ++-----------------------
drivers/macintosh/therm_windtunnel.c | 52 +++++++++++++++++++++---------------
3 files changed, 34 insertions(+), 56 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-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards b8f9b44f8 0: update: binutils-gcc-linux: all
new 5df9f7a63 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 (b8f9b44f8)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-m [...]
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 | 184 +-
02-prepare_abe/console.log | 240 +-
03-build_abe-binutils/console.log | 11142 ++++++-------
04-build_abe-stage1/console.log | 18224 ++++++++++-----------
05-build_linux/console.log | 768 +-
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 12 +-
08-update_baseline/console.log | 12 +-
console.log | 30722 ++++++++++++++++++------------------
jenkins/manifest.sh | 12 +-
regressions.txt | 2 +-
11 files changed, 30666 insertions(+), 30654 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-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 3ab279b58 0: update: binutils-gcc-linux: all
new 5be0a1388 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 (3ab279b58)
\
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 | 166 +-
02-prepare_abe/console.log | 122 +-
03-build_abe-binutils/console.log | 11094 ++++++++-------
04-build_abe-stage1/console.log | 13657 +++++++++----------
05-build_linux/console.log | 858 +-
06-boot_linux/console.log | 8 +-
07-check_regression/console.log | 2 +-
08-update_baseline/console.log | 4 +-
console.log | 25921 ++++++++++++++++++------------------
jenkins/manifest.sh | 8 +-
regressions.txt | 3 +-
11 files changed, 25923 insertions(+), 25920 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-defconfig
in repository toolchain/ci/base-artifacts.
discards 92a48ade8 0: update: binutils-gcc-linux: boot
new 2a89ee383 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 (92a48ade8)
\
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 | 216 +-
02-prepare_abe/console.log | 240 +-
03-build_abe-binutils/console.log | 11430 ++++++-------
04-build_abe-stage1/console.log | 18142 ++++++++++-----------
05-build_linux/console.log | 738 +-
06-boot_linux/console.log | 392 +-
07-check_regression/console.log | 12 +-
08-update_baseline/console.log | 12 +-
console.log | 31182 ++++++++++++++++++------------------
jenkins/manifest.sh | 8 +-
regressions.txt | 3 +-
11 files changed, 31188 insertions(+), 31187 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_gnu/gnu-master-aarch64-bootstrap_O3
in repository toolchain/ci/base-artifacts.
discards 50d32516b 0: update: gcc-ae7051590d4bf9b844874e727791f236315c835a: 1
new 96f9f55ee 0: update: gcc-7067f8c814088c1d02e40adf79a80f5ec53dbdde: 1
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 (50d32516b)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu/gnu-master-aarch64-b [...]
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 | 128 +-
02-prepare_abe/console.log | 414 +-
03-build_abe-bootstrap_O3/console.log | 71271 ++++++++++++++++---------------
05-check_regression/console.log | 20 +-
06-update_baseline/console.log | 30 +-
console.log | 71863 ++++++++++++++++----------------
jenkins/manifest.sh | 8 +-
regressions.txt | 12 +-
8 files changed, 71868 insertions(+), 71878 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.