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 04b6801f9 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 5757e1e9d 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards ea62c7123 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 10cb6e544 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 451bf4ba6 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards fee1edc81 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards c374b1db9 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 6aa2034b6 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards b3852eb93 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards 9022b346e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 3ddedaa82 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 4d3d663be 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards 8ee42dff9 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards e7cc0186f 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 488391772 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards dd0d7ce11 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards fec155ae5 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards bd4c466cc 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards d0e8f23e6 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6c1a46d82 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 5286a9ae8 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 978cd5b6a 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 830cc3b46 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards e36bb7d40 85: onsuccess: 7: Success after gcc: 9 commits discards ad819e31c 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 03531c426 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 5a6111ac5 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 3e38ed108 81: onsuccess: 7: Successful build after gcc: 2 commits discards 03a01dccf 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards cfd38d608 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards fbeb5e629 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 05bb13472 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 3282187f0 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3ff4e0653 75: onsuccess: 7: Successful build after linux: 44 commits discards d86067227 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards d026dc34a 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8ee68758b 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 09df4e51b 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards ff0b4942d 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 7912da988 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 77f0ba9b6 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 563d17811 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 237552bef 66: onsuccess: 7: Successful build after gcc: 3 commits discards 95adce5e4 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 70165a7ea 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0698d5f61 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards b333e2fda 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards dd0961ce0 61: onsuccess: 4: Successful build after gcc: 15 commits discards f984f7ad8 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 169506537 59: force: 7: Successful build after gcc: 2 commits discards 0bde18d9b 58: onsuccess: 7: Successful build after glibc: 2 commits discards 8fcb7d424 57: onsuccess: 7: Successful build after gcc: 7 commits discards 28229e292 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6b7c1b1f5 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 211dbf48f 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 42dd03b21 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards 9c2cdea2b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 3066a416c 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5c4b3d0bf 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c5b366004 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ebeb715f5 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards e27ae96c1 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d75ff0081 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 605603cbd 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5cbe4386c 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards f13c88c67 43: onsuccess: 7: Successful build after gcc: 2 commits discards 134cdc262 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 45c5011a1 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e01028825 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 28986ee55 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards d55655b7a 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 563e11974 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 2a994227c 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0bd61d968 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7d983b2ec 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7425ebb26 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 16c0577b9 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 1737cd1c9 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 8c7b8a013 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards bfa703dbc 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 27f280c88 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8a7c9e0e7 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a6085133c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 08b3b99ec 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0844e9f4a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 969910196 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f0b6a82d2 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 172a9a5ba 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6afe6e6d7 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 58452bcdd 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8597778a9 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1820ebf08 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards faf8fed1c 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d015985fb 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f22bfe65d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ca929676c 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6db2ca82f 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e498a68cb 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e373159b3 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 65f681604 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1e7f1bc66 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1ae139362 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c3c64b226 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d4ca95ed8 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6479d85aa 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3843c3b43 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 45e0f5c25 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fc1491857 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 99d7c834f 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2a2abf74e 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8e1c71e06 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a5446a30b 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7ae8ec1ff 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 022af0278 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 041e202b2 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 84fae595a 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 732815c6a 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fdd91fb13 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4275bac40 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 607d25ecc 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cd4585977 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a61b994cc 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4856b2c48 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new f60b8aae4 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 5fc0e14a0 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new acf8dfab9 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new cbfedde46 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7bc561f95 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 77b30d5f1 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ff0a489d1 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2dd22db9b 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new c024811b6 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 338e03928 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new 57c8eb425 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2e6408952 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a40a66c2a 42: onsuccess: 7: Successful build after baseline build: no n [...] new 83a581875 43: onsuccess: 7: Successful build after gcc: 2 commits new bd9f696a6 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 8e7911360 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5e63cfe06 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 42b3de2bd 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 795fbc104 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new e6a8be295 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e3171bb92 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ed8bebfbb 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 97ecccb06 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 23d49f0b8 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 2280cdece 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 0734d7961 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4f87930e8 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c4aa7807d 57: onsuccess: 7: Successful build after gcc: 7 commits new 1b013e8eb 58: onsuccess: 7: Successful build after glibc: 2 commits new bc4b3449a 59: force: 7: Successful build after gcc: 2 commits new b79ef45bc 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new f97f478ae 61: onsuccess: 4: Successful build after gcc: 15 commits new addf298b2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new ca4aa96ea 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 3ff9cd38a 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b28286d61 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 1186dfba2 66: onsuccess: 7: Successful build after gcc: 3 commits new 7a7c6290f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 732821831 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3c1db9c2f 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new bd70d72ec 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new c71e6cad3 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 858997e14 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 2d00c0c4c 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 7aa96f6c4 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 23a257327 75: onsuccess: 7: Successful build after linux: 44 commits new 34e94d5fa 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ef92cee0e 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 062c93c1d 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 497ec6233 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a1f92afb0 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new b62d7372e 81: onsuccess: 7: Successful build after gcc: 2 commits new 32e211287 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 63302332c 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new e8d925d38 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 0822b650a 85: onsuccess: 7: Success after gcc: 9 commits new 184e03588 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 59d84f563 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 42073c882 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 8f4855f10 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 6a18492c5 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new e0e01b817 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 6317cb428 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 46cd8c12e 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new e26323daf 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 587904de6 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new dba7a9c16 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 5419b4f1f 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new 2d3ce6250 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 99bed98f3 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new 6db799019 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new a06c5a2eb 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 103a8a1c4 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 379ec0de0 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new 4397cc878 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new e9a3b76ed 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new f58658e5d 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 397265f8d 107: onsuccess: #1618: 7: Success after gcc: 2 commits new a6c9d0abd 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddeed [...] new 88883432c 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/gd [...]
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 (04b6801f9) \ 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 1624 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 29840 -> 29644 bytes 05-build_abe-stage1/console.log.xz | Bin 90672 -> 90536 bytes 07-build_abe-linux/console.log.xz | Bin 8672 -> 8304 bytes 08-build_abe-glibc/console.log.xz | Bin 233540 -> 233184 bytes 09-build_abe-stage2/console.log.xz | Bin 226552 -> 222884 bytes 10-build_abe-gdb/console.log.xz | Bin 37112 -> 37232 bytes 11-build_abe-qemu/console.log.xz | Bin 31664 -> 31572 bytes 12-check_regression/console.log.xz | Bin 2148 -> 2704 bytes 13-update_baseline/console.log | 36 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++------------------ 20 files changed, 44 insertions(+), 44 deletions(-)