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 39eeb86 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 7941f79 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 1bf3852 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...] discards 8ce50a8 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...] discards de0bfd4 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits discards 78409b5 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits discards 6415142 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...] discards 3cd170e 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...] discards 6ea7843 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...] discards f97f36b 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits discards 0d0c3c2 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...] discards 7be7ba5 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...] discards 8a01f2a 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...] discards 4578f5b 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...] discards 458eb90 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...] discards 983469d 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...] discards 7fa6d45 7: onsuccess: #368: 1: [TCWG CI] 483.xalancbmk speeds up by - [...] new 37246c8 onsuccess: #368: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 06bee52 8: onsuccess: #369: 1: [TCWG CI] No change after binutils/gcc [...] new 8b800d2 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...] new 81ce9ad 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...] new 5ef22f8 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...] new 0f95b35 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...] new 443d6a2 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...] new f96cdd8 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits new 656f2dc 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...] new 13f81a6 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...] new c9f82bc 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...] new 2dc8fea 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits new e1a35fc 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits new c44e6bc 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...] new c3b4762 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...] new 5fdf6e6 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 241fe7a 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 (39eeb86) \ 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 17 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: