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 88883432ca 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards a6c9d0abdc 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 397265f8df 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards f58658e5db 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards e9a3b76ed7 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 4397cc878c 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 379ec0de0e 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 103a8a1c41 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards a06c5a2eba 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 6db799019e 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 99bed98f34 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 2d3ce6250e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 5419b4f1ff 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards dba7a9c16e 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 587904de66 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards e26323dafe 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 46cd8c12e3 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 6317cb428c 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards e0e01b817f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6a18492c5a 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8f4855f106 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 42073c882c 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 59d84f563c 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 184e03588f 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 0822b650a3 85: onsuccess: 7: Success after gcc: 9 commits discards e8d925d388 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 63302332cb 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 32e2112876 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards b62d7372e8 81: onsuccess: 7: Successful build after gcc: 2 commits discards a1f92afb08 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 497ec6233b 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 062c93c1dd 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ef92cee0e6 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 34e94d5fa8 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 23a2573271 75: onsuccess: 7: Successful build after linux: 44 commits discards 7aa96f6c43 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 2d00c0c4c0 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 858997e148 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards c71e6cad3b 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards bd70d72ecb 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 3c1db9c2f1 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7328218313 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7a7c6290fc 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 1186dfba27 66: onsuccess: 7: Successful build after gcc: 3 commits discards b28286d61d 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3ff9cd38ae 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ca4aa96ea1 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards addf298b22 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards f97f478ae4 61: onsuccess: 4: Successful build after gcc: 15 commits discards b79ef45bc5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards bc4b3449a0 59: force: 7: Successful build after gcc: 2 commits discards 1b013e8ebf 58: onsuccess: 7: Successful build after glibc: 2 commits discards c4aa7807d9 57: onsuccess: 7: Successful build after gcc: 7 commits discards 4f87930e8c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0734d79611 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2280cdeceb 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 23d49f0b84 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 97ecccb06f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ed8bebfbbb 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e3171bb92d 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e6a8be2956 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 795fbc1045 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 42b3de2bde 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5e63cfe068 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 8e79113605 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bd9f696a64 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 83a5818750 43: onsuccess: 7: Successful build after gcc: 2 commits discards a40a66c2a8 42: onsuccess: 7: Successful build after baseline build: no [...] discards 2e64089527 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 57c8eb4259 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 338e03928e 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards c024811b6b 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 2dd22db9be 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards ff0a489d1f 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 77b30d5f1c 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7bc561f950 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards cbfedde467 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards acf8dfab9f 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 5fc0e14a0c 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f60b8aae47 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4856b2c483 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards a61b994cc7 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cd45859779 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 607d25ecc0 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4275bac40c 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fdd91fb13f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 732815c6a1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 84fae595a6 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 041e202b25 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 022af02786 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7ae8ec1ffb 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a5446a30b4 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8e1c71e06a 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2a2abf74ec 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 99d7c834f4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fc14918575 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 45e0f5c252 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3843c3b43d 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6479d85aa0 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d4ca95ed82 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c3c64b226e 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2fd7203f28 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5174d44d25 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f996a6f47e 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 939eed6e9d 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e7dab826e2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 85d2a92b4a 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 991a729361 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7ef6e6baa2 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 84ab4b046b 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 62ca1d3a0c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 570a03155f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6c63635af5 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a02cc254a7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 847ef84346 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 87d17978a0 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0169b68e34 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cd6fd675b2 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8194144daf 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new bdd5604543 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new fca4a2f227 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5daa69de2a 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 993b60017b 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 9fe063e469 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 6d5a80fcac 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new c0a8642efe 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bb37ef83f2 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e6f05f43b6 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new ed5a06c12a 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 84e3cad055 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3eab0f107d 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 17af356876 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new ea2631d7f1 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8a6e62a6b7 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5d0f06376c 42: onsuccess: 7: Successful build after baseline build: no [...] new 9fa0a3f523 43: onsuccess: 7: Successful build after gcc: 2 commits new acf93d6840 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 85908e7902 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 22434522c8 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new c2d73951c2 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2a4a386cd4 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new cc332a705d 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b39dd7a77f 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a4bd75a8e4 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 936e4316f5 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 271b9b2896 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 687cd2472f 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 24c4d21a1a 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 76a2285f5c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1c0e9be129 57: onsuccess: 7: Successful build after gcc: 7 commits new 3de990cd02 58: onsuccess: 7: Successful build after glibc: 2 commits new 36a8940d5e 59: force: 7: Successful build after gcc: 2 commits new b63d1a926f 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new dc890bbf5b 61: onsuccess: 4: Successful build after gcc: 15 commits new 5a454856ed 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new a6787642af 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new d9563e16b6 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7bf9466502 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4e43b6ce88 66: onsuccess: 7: Successful build after gcc: 3 commits new 7af80d88b8 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 28333c1a37 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 261865bb27 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a68a512de2 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 5dd20c0eef 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 82cd4d6b8c 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 0236b1863d 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b99cb1212d 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new d0c1527752 75: onsuccess: 7: Successful build after linux: 44 commits new a7e3a6e084 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b5e99dfa8d 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 3717cc0f0d 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5a6fdb29f1 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 903f3cd15b 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 297e1cf04e 81: onsuccess: 7: Successful build after gcc: 2 commits new 7302bee703 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new f65dea1e5c 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new ca5d1f2d42 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 7db50040bc 85: onsuccess: 7: Success after gcc: 9 commits new f025ce448b 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new cda37812bd 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 7aa2a35cec 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2b5d739fd6 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new c2fde2634b 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new fa93f73520 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new c75486ca22 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 8ce688d90d 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 982b1150e6 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new f232efbca8 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new ac3c28b677 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 584db62d30 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new a9495eb7ee 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 93942c1bff 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new d25afb7056 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 1b68590f63 101: onsuccess: #1609: 7: Success after binutils: 78 commits new d41d0125d8 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 821279c40d 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 2a6d182ed2 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new c4d4ec1ce2 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new cdfe277e65 106: onsuccess: #1617: 7: Success after gcc: 2 commits new fd42eac8ea 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 1c5c05d4da 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 417500e155 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 7188413ffe 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...]
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 (88883432ca) \ 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 1676 -> 1628 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 29644 -> 29928 bytes 05-build_abe-stage1/console.log.xz | Bin 90536 -> 90788 bytes 07-build_abe-linux/console.log.xz | Bin 8304 -> 8296 bytes 08-build_abe-glibc/console.log.xz | Bin 233184 -> 232900 bytes 09-build_abe-stage2/console.log.xz | Bin 222884 -> 223152 bytes 10-build_abe-gdb/console.log.xz | Bin 37232 -> 37332 bytes 11-build_abe-qemu/console.log.xz | Bin 31572 -> 31632 bytes 12-check_regression/console.log.xz | Bin 2704 -> 2580 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++---------- 20 files changed, 60 insertions(+), 60 deletions(-)