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 41653a090 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] discards b03f2de2f 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] discards a2cceafcf 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] discards ecdc22230 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] discards a93abbe48 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 020ea2b33 102: force: #1551: 1: Failure after gcc: 306 commits discards 1f6550e3f 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards d853e4600 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 18fdf10cc 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 639772bf1 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards d0e02947c 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 999adcea7 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4987e49bb 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 649b480ac 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards b2fcc6f89 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 35ccecf9f 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 27b29ad0f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 002074760 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards a03d9c9d1 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 56bab9677 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 01f86985d 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 968a0c1c1 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 54be0a69d 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards 89b682a85 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 285d8a49c 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d5e21aa54 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards d8b9ba1f5 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e13e8db2b 80: onsuccess: 7: Successful build after linux: 44 commits discards ec6e93033 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 5bdf306d4 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards e9b0a9d74 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0b50d2a96 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 3f0722d83 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards af3afb5fb 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 975f38246 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7df4d10fb 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards afee20204 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards b8b878300 70: onsuccess: 7: Successful build after gcc: 4 commits discards 5b8f3280a 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f27abb88c 68: onsuccess: 7: Successful build after linux: 6 commits discards 8bc670579 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards 65a49219f 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards b8eb6d94f 65: onsuccess: 7: Successful build after binutils: 3 commits discards dea75590c 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards e6a502b85 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 8f04ab40a 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 9928c7c69 61: onsuccess: 4: Successful build after gcc: 5 commits discards b6b537a75 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 8b8ab1f1d 59: force: 7: Successful build after gcc: 3 commits discards 538bb9fa5 58: onsuccess: 7: Successful build after glibc: 2 commits discards 58db60996 57: onsuccess: 7: Successful build after gcc: 7 commits discards 824f7fc88 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fbca687aa 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b630ddbba 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 1f464f880 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards 68352136c 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards 24fba1894 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 84c788883 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b0a7e65b8 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3d3e7cd49 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards ac1acb34f 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 082e4a1c9 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards a921343b7 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9745ea63b 44: onsuccess: 7: Successful build after linux: 34 commits discards 6bd285bba 43: onsuccess: 7: Successful build after gcc: 2 commits discards dd6eeace5 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 33dc958a6 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 763935dee 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e6012edf3 39: onsuccess: 7: Successful build after gcc: 2 commits discards 1a7c1e2b8 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7f3769e82 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c1468d4e5 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 84ff586b8 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 459226a28 34: onsuccess: 7: Successful build after gcc: 3 commits discards 67cde4e67 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards dcc490af8 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 7d246b189 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2f20232e9 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards a31424961 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f65b1f85d 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards d97ccd11a 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5f6b78909 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 85fc29c33 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4a77ea7f5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d1c483441 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3243ee46c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c81bd7a36 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f8641aae7 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 606a21d39 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 596168d86 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e6a1a28d0 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 811eb7855 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 320c51b59 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 49936d631 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0a2931b5d 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards acbc32c97 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 34063d027 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 61b485603 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6de130394 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4f5e7ca04 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e6a076803 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 32dc54abb 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c63739d32 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b47a33ad5 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 68507901a 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d8ed44e28 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 20fc98d9f 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 002a0f24c 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 09cc2ac0d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a486e40b5 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dda36c9d9 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4427dd2a7 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 654a69a72 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 82075a5dd 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0574bee0e 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dc62c11a6 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a2a63d392 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2eb6bdde2 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d3544de19 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6b0f81f3a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a03cfe447 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3c8bf10c6 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 821c74885 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 62c12002e 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 31d6f0b29 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 8287f9df8 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new aa75cadca 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 8bf338019 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7c491d34c 34: onsuccess: 7: Successful build after gcc: 3 commits new 4562f7a1d 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 8df38f74a 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b04e18a3a 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new d8ea6fbed 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a87437bba 39: onsuccess: 7: Successful build after gcc: 2 commits new c488ba1b6 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5377e7daa 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ba7f4fe3d 42: onsuccess: 7: Successful build after baseline build: no n [...] new 2fa1a9ab5 43: onsuccess: 7: Successful build after gcc: 2 commits new 847164261 44: onsuccess: 7: Successful build after linux: 34 commits new bf9ee48d8 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new dcf418daf 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new a274875be 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new dd6f7ab3e 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 910c8a1ed 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new faa8b7afc 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b81887172 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 63c02f064 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new 64d080f50 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 5a98966eb 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 92df09d7c 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a728721dd 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 75984671d 57: onsuccess: 7: Successful build after gcc: 7 commits new 52b04a780 58: onsuccess: 7: Successful build after glibc: 2 commits new ed2bd8170 59: force: 7: Successful build after gcc: 3 commits new 1244d1769 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 5686e0ef6 61: onsuccess: 4: Successful build after gcc: 5 commits new 916a59e6a 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new ca24cb1ae 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 5b3ebf5c2 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new b9067ef98 65: onsuccess: 7: Successful build after binutils: 3 commits new b7ef565cc 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new 2e13951b3 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new 76876e7c6 68: onsuccess: 7: Successful build after linux: 6 commits new 8b978108c 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 786089e62 70: onsuccess: 7: Successful build after gcc: 4 commits new 7f36a6fa6 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 8b7c1ef7b 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e9890e41b 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 89682783b 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new d3a8a6c51 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new a153f132c 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 1ce270d51 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 565d641a5 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new 6ad1aaeab 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 16e77af5a 80: onsuccess: 7: Successful build after linux: 44 commits new a1af447ee 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2e9c0c4b6 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 25d691faf 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d7ba8c65e 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new dee94b357 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 054a35fd4 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new a4bdb483b 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 7c8e2324a 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 56908092e 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 9ce4f6716 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new c4f350a81 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 8cad46a71 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new cb6a18997 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 9b9ebd7ee 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 28dd1f087 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 13b85dfbd 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 1f4a9566e 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 244998b91 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new 0841973b9 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 14062187a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new f5b67e43e 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 1df320347 102: force: #1551: 1: Failure after gcc: 306 commits new 19c6dae63 103: onsuccess: #1552: 1: Success after gcc: 5 commits new ca0bce85e 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] new b62027b36 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] new aa17272bc 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] new 67bdc669e 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] new e06387473 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...]

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 (41653a090) \ 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 1688 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 30348 -> 30356 bytes 05-build_abe-stage1/console.log.xz | Bin 72700 -> 72044 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8296 -> 8284 bytes 08-build_abe-glibc/console.log.xz | Bin 239488 -> 239464 bytes 09-build_abe-stage2/console.log.xz | Bin 203332 -> 202628 bytes 10-build_abe-gdb/console.log.xz | Bin 37592 -> 37524 bytes 11-build_abe-qemu/console.log.xz | Bin 31640 -> 31652 bytes 12-check_regression/console.log.xz | Bin 2580 -> 2132 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ 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 ++++++------- 18 files changed, 51 insertions(+), 51 deletions(-)