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-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 894c9d64d 0: update: binutils-gcc-linux: all
new ba094f892 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 (894c9d64d)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-lt [...]
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 | 182 +-
02-prepare_abe/console.log | 298 +-
03-build_abe-binutils/console.log | 11732 +++++------
04-build_abe-stage1/console.log | 20162 +++++++++----------
05-build_linux/console.log | 5588 +++---
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 12 +-
08-update_baseline/console.log | 20 +-
console.log | 38052 ++++++++++++++++++------------------
jenkins/manifest.sh | 12 +-
regressions.txt | 3 +-
11 files changed, 38046 insertions(+), 38017 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 tested
in repository toolchain/abe.
from ff58985a latest-rel: upgrade to glibc-2.31 again
adds ffd9bbea latest-rel: use glibc-2.31 release branch instead of tag
No new revisions were added by this update.
Summary of changes:
config/latest-rel/glibc.conf | 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.
"Christophe Lyon pushed a change to branch master
in repository toolchain/abe.
from ff58985a latest-rel: upgrade to glibc-2.31 again
new ffd9bbea latest-rel: use glibc-2.31 release branch instead of tag
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:
config/latest-rel/glibc.conf | 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_bmk_tk1/llvm-release-arm-spec2k6-Os
in repository toolchain/ci/glibc.
from 74d9b0811e riscv: Avoid clobbering register parameters in syscall
adds d53f5cac50 malloc/tst-mallocfork2: Kill lingering process for unexpecte [...]
No new revisions were added by this update.
Summary of changes:
malloc/tst-mallocfork2.c | 39 ++++++++++++++++++++++++++++-----------
1 file changed, 28 insertions(+), 11 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_tk1/llvm-release-arm-spec2k6-Os
in repository toolchain/ci/base-artifacts.
discards 8c9be66db 1: update: llvm-1f6c9becd57af14ee71fb7c1e56b55f556be98fa: 1
new b5d9ea73a 1: update: binutils-gcc-glibc-llvm: 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 (8c9be66db)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_tk1/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 | 215 +-
02-prepare_abe/console.log | 428 +-
03-build_abe-binutils/console.log | 11174 +-
04-build_abe-stage1/console.log | 18070 ++--
05-build_abe-linux/console.log | 290 +-
06-build_abe-glibc/console.log | 37866 +++----
07-build_abe-stage2/console.log | 44339 ++++----
08-build_llvm-true/console.log | 12572 +--
10-benchmark--Os_mthumb/benchmark-start.log | 2 +-
10-benchmark--Os_mthumb/benchmark.log | 64 +-
10-benchmark--Os_mthumb/console.log | 232 +-
11-check_regression/console.log | 3094 +-
11-check_regression/results-0.csv | 2227 +-
11-check_regression/results-1.csv | 2204 +-
11-check_regression/results-brief.csv | 38 +-
11-check_regression/results-compare.csv | 18 +-
11-check_regression/results-full.csv | 2393 +-
11-check_regression/results.csv | 168 +-
11-check_regression/results.log | 2400 +-
12-update_baseline/console.log | 6365 +-
12-update_baseline/results-1.csv | 2204 +-
12-update_baseline/results-brief.csv | 38 +-
12-update_baseline/results-compare.csv | 18 +-
12-update_baseline/results-full.csv | 2203 +-
12-update_baseline/results.csv | 164 +-
12-update_baseline/results.log | 1658 +-
console.log | 134645 +++++++++++++------------
jenkins/manifest.sh | 19 +-
results | 2 +-
results_id | 2 +-
30 files changed, 143651 insertions(+), 141461 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-arm-bootstrap_debug
in repository toolchain/ci/base-artifacts.
discards 6e753973b 0: update: gcc-a51a546c1704cd572c35c11e539568c04d99e7d1: 1
new 533a05e59 0: update: gcc-649e174102a8ae2d570616d09aa336b712e1baae: 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 (6e753973b)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu/gnu-master-arm-boots [...]
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 | 138 +-
02-prepare_abe/console.log | 419 +-
03-build_abe-bootstrap_debug/console.log | 95369 ++++++++++++++--------------
05-check_regression/console.log | 20 +-
06-update_baseline/console.log | 2 +-
console.log | 95948 +++++++++++++++--------------
jenkins/manifest.sh | 8 +-
regressions.txt | 6 +-
8 files changed, 95961 insertions(+), 95949 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.