This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
discards 43921630 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 1c94b2ab 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards b96efacb 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards 5a1348e7 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards 07c9f75e 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards fcb4570e 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 98816daf 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards eb20598e 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards 91dd6877 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
discards e0f46052 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
discards a40affbc 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
discards 86eef772 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
discards b5d1cfeb 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
discards 049c88ce 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
discards c9ba1f64 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
discards d66a1127 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
discards 95d6ff1e 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards 80110e2c 5: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards e3413cf0 4: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards a61fccf1 3: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 3557f7a1 onsuccess: #364: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]
new 94557c62 4: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 9c604a1b 5: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 222c6ea9 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 7ff4e6b9 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
new 5f128c92 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
new 292e2b7f 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
new 143c364e 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
new 552f78f4 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
new a8339a5e 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
new abcda171 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new 5dc672b7 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new ef71310a 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 2e772c56 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new f7277014 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new ef9b13af 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new 147d80e6 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new bbff9427 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new 650a5ce3 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new f8cf256d onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
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 (43921630)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
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 20 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.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
discards db6ebe51 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 79c373ce 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards 805e0e21 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards f835cad7 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards 76752042 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards a8ab5a9d 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 9d2beaee 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards 0acd6006 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards 2834fd75 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
discards 2ecfecd4 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
discards 82d1b688 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
discards 8a25b0e4 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
discards 1b3d8558 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
discards 2a098b4f 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
discards b5304607 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
discards 3ca0a5fd 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
discards c85edd9d 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards 8c607b6d 5: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards ff5fefaa 4: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards 097cd365 3: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards 519b8b0b 2: onsuccess: binutils-gcc-linux-glibc: 1
discards 406dd14d Initial empty repository
new c410750a init: #362: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk_c [...]
new a61fccf1 3: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new e3413cf0 4: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 80110e2c 5: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 95d6ff1e 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new d66a1127 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
new c9ba1f64 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
new 049c88ce 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
new b5d1cfeb 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
new 86eef772 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
new a40affbc 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
new e0f46052 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new 91dd6877 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new eb20598e 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 98816daf 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new fcb4570e 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 07c9f75e 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new 5a1348e7 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new b96efacb 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new 1c94b2ab 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new 43921630 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
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 (db6ebe51)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
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 21 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.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
omits c65d66ee onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
omits 037ec37a 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
omits 5df5b6ae 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
omits 18c1120a 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
omits 99938c54 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
omits be8c182f 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
omits bf2fbcc1 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
omits 88fe061e 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
omits 3ed71a9a 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
omits ae9ef148 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
omits 341593f0 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
omits ae050a35 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
omits 06940740 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
omits 65128368 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
omits 1f4e1dcf 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
omits 1fa2f373 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
omits 9d23900b 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
omits 38ecf8e8 5: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
omits 3da09b7c 4: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
omits e74cc6da 3: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
omits 7d6f6f08 2: onsuccess: binutils-gcc-linux-glibc: 1
omits 7a0a3fac 1: onsuccess: binutils-gcc-linux-glibc: 1
omits e58da728 0: update: binutils-gcc-linux-glibc: 1
new 406dd14d Initial empty repository
new 519b8b0b 2: onsuccess: binutils-gcc-linux-glibc: 1
new 097cd365 3: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new ff5fefaa 4: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 8c607b6d 5: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new c85edd9d 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 3ca0a5fd 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
new b5304607 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
new 2a098b4f 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
new 1b3d8558 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
new 8a25b0e4 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
new 82d1b688 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
new 2ecfecd4 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new 2834fd75 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new 0acd6006 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 9d2beaee 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new a8ab5a9d 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 76752042 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new f835cad7 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new 805e0e21 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new 79c373ce 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new db6ebe51 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
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 (c65d66ee)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
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 22 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.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/v0.0_to_v0.1-76/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
at c65d66ee onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
No new revisions were added by this update.
--
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 master
in repository toolchain/ci/interesting-commits.
from c2a3c1d4 Add entry 2656572d485127cc30b8fe9752024d2a0f1c50db from https [...]
new 88f6764b Add entry 572a757fa78722fddeb9b651120607f8eee5d13f from https [...]
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:
.../commit-log.txt | 11 +++++++++++
.../jira/components | 0
.../jira/description | 19 +++++++++++++++++++
.../jira/startdate | 1 +
.../jira/summary | 1 +
.../status.txt | 5 +++++
.../llvm-arm-master-O2/details.txt | 2 +-
.../reproduction_instructions.txt | 8 ++++----
.../llvm-arm-master-O2/status.txt | 3 +++
.../llvm-arm-master-O2/summary.txt | 7 -------
.../tcwg_bmk-code_speed-spec2k6/status.txt | 21 ++-------------------
11 files changed, 47 insertions(+), 31 deletions(-)
create mode 100644 llvm/sha1/572a757fa78722fddeb9b651120607f8eee5d13f/commit-log.txt
copy llvm/sha1/{05b4310c8aec7a050574277ced08a0ab86b27681 => 572a757fa78722fddeb9b6 [...]
create mode 100644 llvm/sha1/572a757fa78722fddeb9b651120607f8eee5d13f/jira/description
create mode 100644 llvm/sha1/572a757fa78722fddeb9b651120607f8eee5d13f/jira/startdate
create mode 100644 llvm/sha1/572a757fa78722fddeb9b651120607f8eee5d13f/jira/summary
create mode 100644 llvm/sha1/572a757fa78722fddeb9b651120607f8eee5d13f/status.txt
copy llvm/sha1/{2656572d485127cc30b8fe9752024d2a0f1c50db => 572a757fa78722fddeb9b6 [...]
copy {gcc/sha1/822a11a1e642e0abe92a996e7033a5066905a447/tcwg_bmk-code_speed-spec2k [...]
create mode 100644 llvm/sha1/572a757fa78722fddeb9b651120607f8eee5d13f/tcwg_bmk-cod [...]
delete mode 100644 llvm/sha1/572a757fa78722fddeb9b651120607f8eee5d13f/tcwg_bmk-cod [...]
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.