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 e157a4e4 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 8e21a997 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards 6055d7af 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards b16ed4b0 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards f3c60027 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards 4f7c18bd 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 0702ecb7 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards a7b3d9ca 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards 5be83b48 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
discards 0d4868c6 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
discards e08c0fb9 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
discards 130d7d6e 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
discards d80d9be2 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
discards 9536df8d 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
discards d4dc7764 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
discards 40d5b9ab 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
discards 9ab80b4f 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards 0625bd67 5: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new bc7e20be onsuccess: #366: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]
new eb95e0de 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 485a18ae 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
new 54b47129 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
new 71178e55 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
new 053d9bff 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
new b0c165da 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
new b24bfedf 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
new af0a7b82 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new d72cd9f8 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new c48bf87d 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 0c4d7f8c 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new c9ed6144 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 98e2f31c 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new 4960e981 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new 2d1e46b4 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new 9d5b2860 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new 1b07874f 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 (e157a4e4)
\
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 18 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 f8cf256d onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 650a5ce3 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards bbff9427 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards 147d80e6 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards ef9b13af 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards f7277014 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 2e772c56 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards ef71310a 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards 5dc672b7 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
discards abcda171 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
discards a8339a5e 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
discards 552f78f4 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
discards 143c364e 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
discards 292e2b7f 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
discards 5f128c92 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
discards 7ff4e6b9 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
discards 222c6ea9 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards 9c604a1b 5: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
discards 94557c62 4: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 63bfd555 onsuccess: #365: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]
new 0625bd67 5: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 9ab80b4f 6: onsuccess: 1: [TCWG CI] No change after binutils/gcc/linux [...]
new 40d5b9ab 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...]
new d4dc7764 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...]
new 9536df8d 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
new d80d9be2 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
new 130d7d6e 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
new e08c0fb9 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
new 0d4868c6 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new 5be83b48 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new a7b3d9ca 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 0702ecb7 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new 4f7c18bd 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new f3c60027 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new b16ed4b0 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new 6055d7af 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new 8e21a997 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new e157a4e4 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 (f8cf256d)
\
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 19 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.