This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts.

discards 41d31b635 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 13986491e 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards d5d09a8dc 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards dcadd47b5 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards c13d7468f 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 2294bbe0b 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 52d73af54 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards a82c3e358 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards f03f178c0 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards 57622faf6 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards fbaa0583c 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 04d44a072 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 9d883ff27 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards 44398c713 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards fff10a8d1 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9249e429f 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards b88797d72 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 24449e352 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards d7627a86b 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 8ba4913d0 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 6efb034e5 85: onsuccess: 7: Success after gcc: 9 commits discards 290ff7886 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards d7bb8a2f7 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards f0f67ee8d 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 0f1fcb807 81: onsuccess: 7: Successful build after gcc: 2 commits discards 53fc33733 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 8dbd144b9 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ac0782e99 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f32d7a003 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 3d90437c8 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5af753f6b 75: onsuccess: 7: Successful build after linux: 44 commits discards e9c21300f 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 66ebead03 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1c314314a 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards bd0658f5b 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 967aaccec 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards cb74f06fb 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9d0346d67 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 680208587 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 50d0dc70f 66: onsuccess: 7: Successful build after gcc: 3 commits discards 4a3a5d51a 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7caf189b8 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0a90f29f3 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards cc9efabd1 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 3419dea37 61: onsuccess: 4: Successful build after gcc: 15 commits discards ad71a8475 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 8770cdb3e 59: force: 7: Successful build after gcc: 2 commits discards 5276868ca 58: onsuccess: 7: Successful build after glibc: 2 commits discards 8b6213b7b 57: onsuccess: 7: Successful build after gcc: 7 commits discards 77790b6e7 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cea63ad8a 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ec40ec2db 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards a85b3a7f9 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards e85b38b65 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 36cc20c6a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 20f38bab4 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4fb0fd04a 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7721daa49 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards d00a37ffd 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d0aed12b4 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 6dc1273b0 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 39130dffc 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards be00a48a9 43: onsuccess: 7: Successful build after gcc: 2 commits discards 871361c24 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 0c4f95be4 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards eb26b3c63 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 63c017413 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards 20bc7d07e 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards bc61c349c 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 166afeecd 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards eb7dc2835 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 63f907220 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 77a824950 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 019c0155d 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 88ac57897 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3b3653b3e 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 27febcb7e 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 0b11c2810 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e8ba87e82 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5333a3747 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 70e2c8978 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 90ea719ec 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e82a5b5ac 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e5c4957d9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4aafdc89f 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 44ab862b4 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2e1cefd82 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a9c86a7f8 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b554b8da1 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 260c2f1c1 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dd331f4fe 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f18138d4e 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d89a9ecfa 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 459a93879 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dfafced03 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b8aa3abe6 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b8ac956aa 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 31bb0edff 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e5f65f494 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a549abe11 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c11b441d7 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dbf8d76bb 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f28b3b495 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9948bbd4e 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9f258e127 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fbf653606 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 51343f027 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e768eafbf 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b77cde2b3 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4266f9c09 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 37b4f9cee 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 616f1b2a0 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b7852f535 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7796c943a 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7d0a54e08 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9b254a859 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8143210f9 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2a97f37c4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3c947d902 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 841b3de2d 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 29dcf2782 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new be0e7a661 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 997bd8301 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a745c928a 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 94e5195e7 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c84056e17 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new f6fe8b0e7 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 02c9f221b 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 6e0c51cd1 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 1cd53dcdc 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7db600b22 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 09b1dc3a1 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 96b9b29e2 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new aefa9fa2d 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new cd633df01 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 72147d516 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 7369d9cf6 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d7ad67ce0 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 74da085dd 42: onsuccess: 7: Successful build after baseline build: no n [...] new cdec483d2 43: onsuccess: 7: Successful build after gcc: 2 commits new 6b9a7897c 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new f53c0c856 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 43bbe622b 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 017159daa 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c1b201c31 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 2f7841333 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ddb930b27 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new fad2f9fb4 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a3a98627a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 4ec5a8644 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new fefe1e24e 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 046f05da8 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 34cd050cf 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ff8b1d990 57: onsuccess: 7: Successful build after gcc: 7 commits new e9bcdd716 58: onsuccess: 7: Successful build after glibc: 2 commits new e4591db78 59: force: 7: Successful build after gcc: 2 commits new fea118aed 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new b76197842 61: onsuccess: 4: Successful build after gcc: 15 commits new d8ecc6513 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 0266e0112 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new cf09a29ef 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a80b9c313 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4500c19f6 66: onsuccess: 7: Successful build after gcc: 3 commits new dd9e8afbe 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e776ee3b1 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 87da99bfa 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ffcf00cc2 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 7404fbea2 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 911c9b605 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new be70ca262 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 53a49df8f 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 3782c315b 75: onsuccess: 7: Successful build after linux: 44 commits new c574024b2 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b12415009 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 5d9375a37 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new efe644422 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 1f3f28be7 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new ab6f268e4 81: onsuccess: 7: Successful build after gcc: 2 commits new a67f336a8 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 148fbf2b7 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new c6a87faab 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 617829898 85: onsuccess: 7: Success after gcc: 9 commits new 091ef3a83 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 64b73de20 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 73d49b73e 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 203c8b245 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 59d12b55e 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 32c351e54 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new c54b0204e 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 134d5141c 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 690d81d38 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 07a88ea27 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new b231ce17c 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 682cbce2b 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 6a7a0d6a9 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new b5e828028 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 326ab9537 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 64ef07bab 101: onsuccess: #1609: 7: Success after binutils: 78 commits new df1183769 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 2edc6e9d0 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 2bb875f97 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new ac52c14e8 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new b71b12c9c 106: onsuccess: #1617: 7: Success after gcc: 2 commits

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 (41d31b635) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]

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 102 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: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 29944 -> 29852 bytes 05-build_abe-stage1/console.log.xz | Bin 90364 -> 91456 bytes 07-build_abe-linux/console.log.xz | Bin 8644 -> 8628 bytes 08-build_abe-glibc/console.log.xz | Bin 234132 -> 233860 bytes 09-build_abe-stage2/console.log.xz | Bin 222860 -> 224132 bytes 10-build_abe-gdb/console.log.xz | Bin 36936 -> 37152 bytes 11-build_abe-qemu/console.log.xz | Bin 31728 -> 31192 bytes 12-check_regression/console.log.xz | Bin 2696 -> 2324 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++------- 17 files changed, 49 insertions(+), 49 deletions(-)