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 e06387473 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] discards 67bdc669e 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] discards aa17272bc 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] discards b62027b36 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] discards ca0bce85e 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] discards 19c6dae63 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 1df320347 102: force: #1551: 1: Failure after gcc: 306 commits discards f5b67e43e 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 14062187a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 0841973b9 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 244998b91 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards 1f4a9566e 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 13b85dfbd 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 28dd1f087 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9b9ebd7ee 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards cb6a18997 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 8cad46a71 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards c4f350a81 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 9ce4f6716 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 56908092e 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 7c8e2324a 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards a4bdb483b 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 054a35fd4 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards dee94b357 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards d7ba8c65e 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 25d691faf 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2e9c0c4b6 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards a1af447ee 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 16e77af5a 80: onsuccess: 7: Successful build after linux: 44 commits discards 6ad1aaeab 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 565d641a5 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 1ce270d51 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a153f132c 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards d3a8a6c51 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 89682783b 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards e9890e41b 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8b7c1ef7b 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7f36a6fa6 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 786089e62 70: onsuccess: 7: Successful build after gcc: 4 commits discards 8b978108c 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 76876e7c6 68: onsuccess: 7: Successful build after linux: 6 commits discards 2e13951b3 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards b7ef565cc 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards b9067ef98 65: onsuccess: 7: Successful build after binutils: 3 commits discards 5b3ebf5c2 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards ca24cb1ae 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 916a59e6a 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 5686e0ef6 61: onsuccess: 4: Successful build after gcc: 5 commits discards 1244d1769 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards ed2bd8170 59: force: 7: Successful build after gcc: 3 commits discards 52b04a780 58: onsuccess: 7: Successful build after glibc: 2 commits discards 75984671d 57: onsuccess: 7: Successful build after gcc: 7 commits discards a728721dd 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 92df09d7c 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5a98966eb 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 64d080f50 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards 63c02f064 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards b81887172 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards faa8b7afc 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 910c8a1ed 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards dd6f7ab3e 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards a274875be 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards dcf418daf 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards bf9ee48d8 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 847164261 44: onsuccess: 7: Successful build after linux: 34 commits discards 2fa1a9ab5 43: onsuccess: 7: Successful build after gcc: 2 commits discards ba7f4fe3d 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 5377e7daa 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c488ba1b6 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a87437bba 39: onsuccess: 7: Successful build after gcc: 2 commits discards d8ea6fbed 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b04e18a3a 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 8df38f74a 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4562f7a1d 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7c491d34c 34: onsuccess: 7: Successful build after gcc: 3 commits discards 8bf338019 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards aa75cadca 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 8287f9df8 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 31d6f0b29 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards 62c12002e 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 821c74885 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 3c8bf10c6 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a03cfe447 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6b0f81f3a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d3544de19 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2eb6bdde2 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a2a63d392 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dc62c11a6 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0574bee0e 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 82075a5dd 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 654a69a72 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4427dd2a7 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dda36c9d9 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a486e40b5 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 09cc2ac0d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 002a0f24c 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 20fc98d9f 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d8ed44e28 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 68507901a 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b47a33ad5 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c63739d32 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9bee4cbf7 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1bfc1d98f 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 680910ebd 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cc71ce503 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dabbec2eb 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 90a94e2d3 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 54a83190f 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 14291b58a 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cc3d06ab9 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5d43904a2 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 759f11b7d 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4e799fb87 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 04214bbde 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5e35bb71f 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dbbaf6263 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 32f839dd9 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new beb502f9b 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3e56e8e60 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a58bd6d3e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d7e956c1a 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new bad877eeb 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new f8f4a3317 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c18d8eb05 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new f57ad6d3c 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 437147d81 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 76182b157 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7afaeecfa 34: onsuccess: 7: Successful build after gcc: 3 commits new a80cde56a 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 8e16909be 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 16a3c8ac5 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 99bc56a4a 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 77fe266c2 39: onsuccess: 7: Successful build after gcc: 2 commits new ac83a4167 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5b10492d4 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 65afd7e59 42: onsuccess: 7: Successful build after baseline build: no n [...] new 349c94247 43: onsuccess: 7: Successful build after gcc: 2 commits new 56a12911e 44: onsuccess: 7: Successful build after linux: 34 commits new 003bd20b3 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d02273b01 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new df79197b3 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ef4e365a3 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new b1c455a54 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 6bdcec836 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ed8e95763 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b9ba60ad4 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new 6d17fb792 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 79f0854f6 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 3217ddded 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 32fc3de44 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new fcb7546aa 57: onsuccess: 7: Successful build after gcc: 7 commits new 580b27f55 58: onsuccess: 7: Successful build after glibc: 2 commits new 45e5ae678 59: force: 7: Successful build after gcc: 3 commits new 896f5ca46 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 009846821 61: onsuccess: 4: Successful build after gcc: 5 commits new fb0366f35 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new beffe2768 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 3133a4864 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 0f3b94132 65: onsuccess: 7: Successful build after binutils: 3 commits new 8990aad9c 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new 208d81dfe 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new 5b78343e5 68: onsuccess: 7: Successful build after linux: 6 commits new 8627cc70c 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 03027de73 70: onsuccess: 7: Successful build after gcc: 4 commits new 6ad2e3831 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new acedbf70e 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 97fe101d9 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 66ab8a3c7 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new e5f4f4c6b 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 57dfd693b 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 59c650525 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b613f5eb2 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new 8212919a5 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new d5a8832a4 80: onsuccess: 7: Successful build after linux: 44 commits new 5141bcb1f 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7c4693029 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new fbae6215c 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 620629933 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 6f6168130 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new ff673d424 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new f37ea4622 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new c410f2780 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new ade0d8c38 89: onsuccess: 7: Success after gcc/glibc: 8 commits new b13c45c3a 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 2e22e3815 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 6ec52b65a 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 458b1a5b0 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 59e52b74c 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new b1bc775d8 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b522affbe 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 71d76618d 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new c7112967c 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new 84358c735 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 564b51afd 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new 3caade25f 101: onsuccess: #1547: 7: Success after binutils: 82 commits new ad862e248 102: force: #1551: 1: Failure after gcc: 306 commits new f0935da92 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 9a41f4b78 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] new e50f6cac7 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] new c0e13678c 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] new 760930ca1 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] new 65a64e3dd 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] new 7de316031 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 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 (e06387473) \ 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 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30356 -> 30184 bytes 05-build_abe-stage1/console.log.xz | Bin 72044 -> 72108 bytes 07-build_abe-linux/console.log.xz | Bin 8284 -> 8280 bytes 08-build_abe-glibc/console.log.xz | Bin 239464 -> 239356 bytes 09-build_abe-stage2/console.log.xz | Bin 202628 -> 201968 bytes 10-build_abe-gdb/console.log.xz | Bin 37524 -> 37432 bytes 11-build_abe-qemu/console.log.xz | Bin 31652 -> 31684 bytes 12-check_regression/console.log.xz | Bin 2132 -> 2412 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++-------- 19 files changed, 55 insertions(+), 55 deletions(-)