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 241fe7a onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 5fdf6e6 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards c3b4762 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...] discards c44e6bc 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...] discards e1a35fc 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits discards 2dc8fea 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits discards c9f82bc 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...] discards 13f81a6 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...] discards 656f2dc 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...] discards f96cdd8 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits discards 443d6a2 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...] discards 0f95b35 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...] discards 5ef22f8 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...] discards 81ce9ad 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...] discards 8b800d2 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...] discards 06bee52 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...] new 1bd6005 onsuccess: #369: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new c7f425f 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...] new e69f13f 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...] new b5166c2 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...] new 06053b7 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...] new 90d893f 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...] new 3ca1daf 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits new 2e715fd 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...] new d497344 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...] new 1fd30dd 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...] new c5d1f8b 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits new 86a6de3 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits new d238d20 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...] new d072500 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...] new 4463e00 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 78700bb onsuccess: #77: 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 (241fe7a) \ 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 16 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: