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-arm-bootstrap_O1
in repository toolchain/ci/base-artifacts.
discards 0360fb70e 0: update: binutils-gcc: 2
new 23e310227 0: update: binutils-gcc: 2
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 (0360fb70e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-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.xz | Bin 1540 -> 1496 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2752 bytes
04-build_abe-binutils/console.log.xz | Bin 66924 -> 66164 bytes
05-build_abe-bootstrap_O1/console.log.xz | Bin 470380 -> 472500 bytes
06-check_regression/console.log.xz | Bin 420 -> 416 bytes
07-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 12 ++++++------
7 files changed, 14 insertions(+), 14 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_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-Os
in repository toolchain/ci/base-artifacts.
discards c264291e1 0: update: binutils-gcc-newlib: 1
new 51c663bda 0: update: binutils-gcc-newlib: 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 (c264291e1)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_e [...]
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 1568 -> 1552 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes
03-build_abe-binutils/console.log.xz | Bin 43532 -> 43936 bytes
04-build_abe-stage1/console.log.xz | Bin 87868 -> 88848 bytes
06-build_abe-newlib/console.log.xz | Bin 32788 -> 32756 bytes
07-build_abe-stage2/console.log.xz | Bin 155460 -> 156564 bytes
09-benchmark/benchmark-start.log | 2 +-
09-benchmark/benchmark.log | 32 ++++++++++++++++---
09-benchmark/console.log.xz | Bin 2148 -> 2536 bytes
10-check_regression/console.log.xz | Bin 1612 -> 1616 bytes
10-check_regression/results-0.csv | 2 +-
10-check_regression/results-1.csv | 2 +-
10-check_regression/results-brief.csv | 2 +-
10-check_regression/results-full.csv | 2 +-
10-check_regression/results.csv | 2 +-
10-check_regression/results.log | 4 +--
11-update_baseline/console.log | 56 +++++++++++++++++-----------------
11-update_baseline/results-0.csv | 2 +-
11-update_baseline/results-1.csv | 2 +-
11-update_baseline/results-brief.csv | 2 +-
11-update_baseline/results-full.csv | 2 +-
11-update_baseline/results.csv | 2 +-
11-update_baseline/results.log | 4 +--
jenkins/manifest.sh | 14 ++++-----
results_id | 2 +-
25 files changed, 79 insertions(+), 55 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/release-aarch64-bootstrap_profiled
in repository toolchain/ci/binutils-gdb.
from 2e62356d25 Automatic date update in version.in
adds bd32538717 Automatic date update in version.in
adds 2e9122f7a6 Automatic date update in version.in
adds ea6e7e4e21 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_gcc_bootstrap/release-aarch64-bootstrap_profiled
in repository toolchain/ci/base-artifacts.
discards 86a70a921 0: update: binutils-gcc: 2
new 5889cd283 0: update: binutils-gcc: 2
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 (86a70a921)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/release-aa [...]
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 1552 -> 1536 bytes
02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes
04-build_abe-binutils/console.log.xz | Bin 49992 -> 50352 bytes
05-build_abe-bootstrap_profiled/console.log.xz | Bin 472128 -> 471140 bytes
06-check_regression/console.log.xz | Bin 416 -> 416 bytes
07-update_baseline/console.log | 18 +++++++++---------
jenkins/manifest.sh | 12 ++++++------
7 files changed, 15 insertions(+), 15 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 maskray/unnest
in repository glibc.
discards 08b717b3dd elf: Avoid nested functions in the loader (all ports) [BZ #27220]
new 73a2e87f41 elf: Avoid nested functions in the loader (all ports) [BZ #27220]
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 (08b717b3dd)
\
N -- N -- N refs/heads/maskray/unnest (73a2e87f41)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.