This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm
in repository toolchain/ci/binutils-gdb.
from 86416e21f2 Automatic date update in version.in
adds cd1a989fe1 Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
1 file changed, 1 insertion(+), 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_gnu_cross_build/master-arm
in repository toolchain/ci/base-artifacts.
discards 7f005bad 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new b06daee7 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
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 (7f005bad)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1584 -> 1724 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2748 bytes
04-build_abe-binutils/console.log.xz | Bin 30120 -> 29996 bytes
05-build_abe-stage1/console.log.xz | Bin 89920 -> 89900 bytes
06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes
07-build_abe-linux/console.log.xz | Bin 8988 -> 8624 bytes
08-build_abe-glibc/console.log.xz | Bin 231756 -> 232444 bytes
09-build_abe-stage2/console.log.xz | Bin 221076 -> 221884 bytes
10-build_abe-gdb/console.log.xz | Bin 37060 -> 37120 bytes
11-build_abe-qemu/console.log.xz | Bin 30428 -> 30380 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 22 +++++++++++-----------
13 files changed, 19 insertions(+), 19 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_gcc_bootstrap/master-aarch64-bootstrap_O1
in repository toolchain/ci/base-artifacts.
discards b582c01c 2: update: binutils-gcc: 0
new b1578a36 2: update: binutils-gcc: 0
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 (b582c01c)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]
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 1536 -> 1668 bytes
02-prepare_abe/console.log.xz | Bin 2728 -> 2744 bytes
04-build_abe-binutils/console.log.xz | Bin 24844 -> 24572 bytes
06-check_regression/console.log.xz | Bin 412 -> 412 bytes
07-update_baseline/console.log | 52 +++++++++++++++++------------------
jenkins/manifest.sh | 12 ++++----
6 files changed, 32 insertions(+), 32 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_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto_lean
in repository toolchain/ci/base-artifacts.
discards 8ba69119 2: update: binutils-gcc: 0
new 38b04363 2: update: binutils-gcc: 0
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 (8ba69119)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]
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 1720 -> 1712 bytes
02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes
04-build_abe-binutils/console.log.xz | Bin 24832 -> 20644 bytes
06-check_regression/console.log.xz | Bin 412 -> 412 bytes
07-update_baseline/console.log | 12 ++++++------
jenkins/manifest.sh | 12 ++++++------
6 files changed, 12 insertions(+), 12 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.