This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_tx1/gnu-release-aarch64-spec2k6-Os
in repository toolchain/ci/base-artifacts.
discards 6f50699 0: update: binutils-gcc-glibc: 1
new 40f5204 0: update: binutils-gcc-glibc: 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 (6f50699)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_tx1/gnu-release-aarc [...]
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 | 22 +-
02-prepare_abe/console.log | 440 +-
03-build_abe-binutils/console.log | 11594 +--
04-build_abe-stage1/console.log | 13758 ++--
05-build_abe-linux/console.log | 306 +-
06-build_abe-glibc/console.log | 39519 ++++++-----
07-build_abe-stage2/console.log | 36549 +++++-----
09-benchmark--Os/benchmark-start.log | 2 +-
09-benchmark--Os/benchmark.log | 26 +-
09-benchmark--Os/console.log | 150 +-
10-check_regression/console.log | 3897 +-
10-check_regression/results-0.csv | 3609 +-
10-check_regression/results-1.csv | 3617 +-
10-check_regression/results-brief.csv | 58 +-
10-check_regression/results-compare.csv | 7 +-
10-check_regression/results-full.csv | 3841 +-
10-check_regression/results.csv | 257 +-
10-check_regression/results.log | 4314 +-
11-update_baseline/console.log | 3907 +-
11-update_baseline/results-0.csv | 3609 +-
11-update_baseline/results-1.csv | 3617 +-
11-update_baseline/results-brief.csv | 58 +-
11-update_baseline/results-compare.csv | 7 +-
11-update_baseline/results-full.csv | 3841 +-
11-update_baseline/results.csv | 257 +-
11-update_baseline/results.log | 4352 +-
console.log | 110364 ++++++++++++++---------------
jenkins/manifest.sh | 10 +-
results_id | 2 +-
29 files changed, 125948 insertions(+), 126042 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 releases/gcc-8
in repository gcc.
from 0c1ead4ca67 Daily bump.
new 65e85d4d89d Daily bump.
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:
gcc/DATESTAMP | 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.
unknown user pushed a change to branch releases/gcc-9
in repository gcc.
from 5e1e8bb00b0 Daily bump.
new 7e9ce2ecfc6 Daily bump.
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:
gcc/DATESTAMP | 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.
unknown user pushed a change to branch releases/gcc-10
in repository gcc.
from 10d74b9be61 Regenerate gcc.pot.
new 3d4f68dcab7 Daily bump.
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:
gcc/DATESTAMP | 2 +-
gcc/po/ChangeLog | 4 ++++
2 files changed, 5 insertions(+), 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.
unknown user pushed a change to branch PR42399
in repository dejagnu.
at 89f58b2 Add regression test for PR42399
This branch includes the following new commits:
new cafd85d Combine inner testsuites used for testing runtest
new 89f58b2 Add regression test for PR42399
The 2 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.
--
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_tx1/gnu-release-aarch64-spec2k6-O3_LTO
in repository toolchain/ci/base-artifacts.
discards fa50b1d 2: update: binutils-gcc-glibc: 1
new eab4337 2: update: binutils-gcc-glibc: 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 (fa50b1d)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_tx1/gnu-release-aarc [...]
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 | 172 +-
02-prepare_abe/console.log | 180 +-
03-build_abe-binutils/console.log | 10995 +--
04-build_abe-stage1/console.log | 13097 ++--
05-build_abe-linux/console.log | 24 +-
06-build_abe-glibc/console.log | 39795 ++++++-----
07-build_abe-stage2/console.log | 36873 +++++-----
09-benchmark--O3_LTO/benchmark-start.log | 2 +-
09-benchmark--O3_LTO/benchmark.log | 24 +-
09-benchmark--O3_LTO/console.log | 154 +-
10-check_regression/console.log | 1124 +-
10-check_regression/results-0.csv | 154 +-
10-check_regression/results-1.csv | 161 +-
10-check_regression/results-brief.csv | 58 +-
10-check_regression/results-full.csv | 167 +-
10-check_regression/results.csv | 72 +-
10-check_regression/results.log | 3478 +-
11-update_baseline/console.log | 1292 +-
11-update_baseline/results-1.csv | 161 +-
11-update_baseline/results-brief.csv | 58 +-
11-update_baseline/results-full.csv | 161 +-
11-update_baseline/results.csv | 72 +-
11-update_baseline/results.log | 2438 +-
11-update_baseline/results.regressions | 2 +-
console.log | 103916 ++++++++++++++--------------
jenkins/manifest.sh | 10 +-
results_id | 2 +-
27 files changed, 107273 insertions(+), 107369 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_cross/gnu-master-aarch64-check_cross
in repository toolchain/ci/base-artifacts.
discards b659fb9 6: update: binutils-53752b85ac3a04c0a888d773b00149bc679e61d5: 1
new 18d275b 6: update: binutils-ed810cc7d3252bd8bfdb4303ee6b44293fe6214e: 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 (b659fb9)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_cross/gnu-master-aarch64 [...]
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 | 201 +-
02-prepare_abe/console.log | 316 +-
03-build_abe-binutils/console.log | 11305 +-
04-build_abe-stage1/console.log | 14809 +-
05-build_abe-linux/console.log | 48 +-
06-build_abe-glibc/console.log | 39911 +-
07-build_abe-stage2/console.log | 34780 +-
08-build_abe-qemu/console.log | 1770 +-
09-build_abe-dejagnu/console.log | 68 +-
10-build_abe-check_gcc/console.log | 30200 +-
11-check_regression/console.log | 329 +-
11-check_regression/results.regressions | 4 +-
12-update_baseline/console.log | 2296 +-
12-update_baseline/results.regressions | 4 +-
console.log | 136149 +--
jenkins/manifest.sh | 8 +-
sumfiles/g++.log | 1532150 ++++++++++++++--------------
sumfiles/g++.sum | 30 +-
sumfiles/gcc.log | 1525243 ++++++++++++++-------------
sumfiles/gcc.sum | 37 +-
sumfiles/gfortran.log | 228117 ++---
sumfiles/libatomic.log | 24 +-
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log | 1982 +-
sumfiles/libgomp.sum | 2 +-
sumfiles/libitm.log | 26 +-
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log | 109723 +-
28 files changed, 1836046 insertions(+), 1833490 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.