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-aarch64 in repository toolchain/ci/base-artifacts.

discards f814cac4f 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards f6ef0429b 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards db5e8f0e0 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 96473f55f 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 7104c5275 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/gd [...] discards f360b622e 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/gl [...] discards aa38018f8 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/gl [...] discards da37ad327 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/gd [...] discards a8304f62f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/gd [...] discards 5c545d626 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 1ef4ead52 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qemu [...] discards 110eacf7a 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/gl [...] discards d8b6c0d53 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 commits discards 0a136f1c0 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: 1 [...] discards 29c44d027 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/gd [...] discards 000ba8411 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] discards 3a7c926f2 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] discards 9097c3122 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 197e72fd5 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 1c0e4f13d 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] discards 9ca66960d 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] discards 00e0f12df 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] discards 8c897ab29 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 1c4517fea 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] discards a5b8a67e9 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 1e8c367fe 102: force: #1551: 1: Failure after gcc: 306 commits discards b0302b341 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 5a28e6ba1 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 113afb1ab 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 0c31b09c5 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards 0a128a8df 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 7105424c1 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9038bc39e 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards b6c54812f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 908eed94b 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards f089ab07f 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 3a469d209 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards faf463152 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 8b10caefb 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards ce9d8259e 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards ec130d37c 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 2bd568a8a 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards ba26cb8f8 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards eaa28a09b 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 4e7bb782b 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7ceb22613 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 3f10d3fb9 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 75827db55 80: onsuccess: 7: Successful build after linux: 44 commits discards 141d25b46 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 2bdb884ac 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 79cff6a15 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8528903ec 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 390ffec6a 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 2837a2166 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 04521d0fb 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b8fcb0cfa 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards bdc1f1a65 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards e74059658 70: onsuccess: 7: Successful build after gcc: 4 commits discards 071e59c02 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 000747f14 68: onsuccess: 7: Successful build after linux: 6 commits discards 74847e38c 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards 2e3c5387c 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards 9e905e570 65: onsuccess: 7: Successful build after binutils: 3 commits discards af34ecb48 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards b64aff1fd 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 236273610 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 9be9634a7 61: onsuccess: 4: Successful build after gcc: 5 commits discards 5d2cefedb 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 9e745f325 59: force: 7: Successful build after gcc: 3 commits discards dcb6341b3 58: onsuccess: 7: Successful build after glibc: 2 commits discards f13c3bfa3 57: onsuccess: 7: Successful build after gcc: 7 commits discards 08655c02d 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 845e79419 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2a592e63e 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards d94727521 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards 635e24faa 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards 1bc6d9650 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2544d65fb 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 64a5f7e46 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 94c77ae4f 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 371f99e4a 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7f832c024 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards c06814e26 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c15d7db1d 44: onsuccess: 7: Successful build after linux: 34 commits discards 23c2b103a 43: onsuccess: 7: Successful build after gcc: 2 commits discards 4d144701d 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 93de5123f 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5612ac7e9 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards aa6c15e02 39: onsuccess: 7: Successful build after gcc: 2 commits discards 5e5851bba 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0d68fd371 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 278a3403a 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 86350b878 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 87eb21a63 34: onsuccess: 7: Successful build after gcc: 3 commits discards e11889faa 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d5840cb28 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards a8f3f0265 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 840b5144c 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards b1ab6af42 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b3269b51a 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards ab50f88e4 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 19861d0f1 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new f40536a05 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 51c1b7b10 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new fd7c8609d 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 5dafa82cf 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b5a243faf 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new fe616a910 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0202adb88 34: onsuccess: 7: Successful build after gcc: 3 commits new 0ae8ec12d 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new d11fe8d15 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8025da807 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 765cdb81c 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d739cfd2b 39: onsuccess: 7: Successful build after gcc: 2 commits new da6f8f290 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8183ac159 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 97ba4d8fe 42: onsuccess: 7: Successful build after baseline build: no n [...] new 6768f5939 43: onsuccess: 7: Successful build after gcc: 2 commits new 5edea25a5 44: onsuccess: 7: Successful build after linux: 34 commits new d540c29a9 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 377b6d738 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 81c8caac9 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c24d70ac6 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 0c343a96d 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 461067f3c 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 186e8a99f 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b08878633 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new 7ba4c1c9c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new ac8a632bf 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 1eb269322 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new aa1449e14 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 36087ee4c 57: onsuccess: 7: Successful build after gcc: 7 commits new 91790c185 58: onsuccess: 7: Successful build after glibc: 2 commits new 5345fade0 59: force: 7: Successful build after gcc: 3 commits new b7b929baf 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 299779bc4 61: onsuccess: 4: Successful build after gcc: 5 commits new 7c85e6f84 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 27fe076de 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 900925efd 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new b27a9d6c5 65: onsuccess: 7: Successful build after binutils: 3 commits new af166dcda 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new 6af0b033a 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new 45dd3679a 68: onsuccess: 7: Successful build after linux: 6 commits new c09b91b69 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 1a613c3dc 70: onsuccess: 7: Successful build after gcc: 4 commits new 942925e36 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new c7e23ccdd 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a4dfdfa28 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 074a7fce5 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 620794794 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new df34a10de 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 820008639 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f317006cb 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new 5e150d264 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new a0d9d1650 80: onsuccess: 7: Successful build after linux: 44 commits new 09440bdee 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 246d8c5b7 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new e2765fff6 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new de2f9cce7 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a996d1dbe 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 83ca9fe1d 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new c05344c47 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 7862f3fa7 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new c42e170ff 89: onsuccess: 7: Success after gcc/glibc: 8 commits new bbbfbf0f7 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new ac74e5c3e 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 5b09d97ac 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 7b5f27fd8 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new c4ebecb36 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new a11120507 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new dc5a2c622 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 961141b49 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 85bc4c940 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new caf407d24 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 40cfb2b10 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new 918407a6e 101: onsuccess: #1547: 7: Success after binutils: 82 commits new b25bb6305 102: force: #1551: 1: Failure after gcc: 306 commits new e3120cc6e 103: onsuccess: #1552: 1: Success after gcc: 5 commits new e90ad43ac 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] new b9b81590d 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] new b107429fe 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] new 207dac4f6 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] new acfa5aec5 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] new 2ee80e4ed 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new c7f7d11ce 110: onsuccess: #1559: 7: Success after gcc: 4 commits new e69c08385 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] new bdea128f5 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] new 009e64ff5 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/gd [...] new 48a99dbf4 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: 1 [...] new db045e698 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 commits new 800b3ee5c 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/gl [...] new ba167c833 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qemu [...] new 485ad4fea 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 71e888742 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/gd [...] new 8e6bf4eca 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/gd [...] new e5be7010b 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/gl [...] new 071334368 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/gl [...] new f8a8a85fa 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/gd [...] new 9f0ca6bf5 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 90a70b197 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new d40751153 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 0d6f3b342 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new e012b164c 128: onsuccess: #1579: 7: Success after linux: 12 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 (f814cac4f) \ 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 1712 -> 1632 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30188 -> 30776 bytes 05-build_abe-stage1/console.log.xz | Bin 72172 -> 73132 bytes 07-build_abe-linux/console.log.xz | Bin 8744 -> 8764 bytes 08-build_abe-glibc/console.log.xz | Bin 240224 -> 242192 bytes 09-build_abe-stage2/console.log.xz | Bin 202880 -> 205320 bytes 10-build_abe-gdb/console.log.xz | Bin 37432 -> 37584 bytes 11-build_abe-qemu/console.log.xz | Bin 31348 -> 32068 bytes 12-check_regression/console.log.xz | Bin 3312 -> 3668 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++------- 17 files changed, 51 insertions(+), 51 deletions(-)