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: