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 d9c0c9901ae 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 340c01d1b2d 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards b9c483d3596 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards 078b24547e3 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 1769b9a06b3 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] discards fbf35da07c5 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] discards 87c853a8d04 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards d9a4eeb3118 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] discards 8eaadee9f53 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards 771787aaaab 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] discards 0e64e715edb 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 0d6d09e3d81 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] discards 357a2ab7f18 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] discards d7716e84d4c 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] discards 50d62d34518 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] discards 50481f0105c 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] discards fd2bc9856bc 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] discards 72f6d1bf26a 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] discards 546c15215ed 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 912ebb18b86 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] discards 3077168dc04 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] discards 670f9384898 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] discards a672f2486fa 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] discards 9bc7ce81baf 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 5866d29b45e 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] discards ef9ad526cb4 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] discards 27bd7d7ddd9 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] discards a25b5538af8 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] discards 239144ed2c0 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards c203093336b 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards 05ac5fadfbb 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] discards 2a799632401 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards 8970738c167 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] discards 63d3dd6aba2 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] discards 00ed5235400 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] discards f7b315d4a09 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards 3850bbbac62 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] discards 49ca22f838c 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] discards ae1e9d5f110 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] discards 7001bc48662 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] discards f0cc8d46ebd 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] discards a447b3f27e7 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] discards e5a2451b064 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards bb64ce4245a 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] discards 7e9b60c2565 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] discards 9e6debc60ca 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] discards d2f6017a514 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] discards 0fd3ab8ebf4 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] discards edd51655fed 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] discards cbc0c9e868b 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 0b7e9066abc 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] discards abbddaa52ab 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 6125f68443f 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards b47bff8b8a7 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] discards 24243562f60 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards c6658f9e4b3 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] discards 1ebc2f818d9 152: force: #1605: 7: Success after gcc: 9 commits discards d6bf92a4082 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] discards db66e06bbcc 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] discards 7db83d78df7 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] discards f392acdf9bf 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] discards f10552c4796 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] discards a434bc3b4ef 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] discards 5bc9d9c5880 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] discards 78d2418b25f 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 586ba3ac282 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] discards 93b34d8a390 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] discards 36cc7bf629e 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] discards 2ee8eeebdec 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] discards 031b62822a5 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] discards 8cb804143ce 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] discards d2817c2f323 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 8e30f76a9aa 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] discards 7c7521aca90 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] discards a40c55e2bba 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] discards 50a9bce961d 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] discards fdc43f3cedd 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] discards 8aff2f83867 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] discards 62671ab2ace 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 0636dd94173 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] discards c09d22d1a75 128: onsuccess: #1579: 7: Success after linux: 12 commits discards da5a77a2115 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] discards f08b9c95e7f 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards fddecff5b8e 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] discards 59d77e0ea7b 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards c75e08c9fe3 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] discards 6bca1822b4c 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] discards 348290f4348 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] discards 0affaab47ac 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] discards f8c68aec2fa 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] discards f7257b575a1 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 [...] discards 70d18839796 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qe [...] discards 6d933d817cd 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/ [...] discards 4a3c059b8ca 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 1 [...] discards 9224a1c40bf 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards d40dde3e3f4 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/ [...] discards e9aae0816bb 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/ [...] discards 197b6301854 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/ [...] discards 752044dd5ef 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 81eb02e5ab2 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 [...] discards d55d8eb3978 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-2 [...] new d4da16eb82c 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-2 [...] new 0fc90189541 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 [...] new d9e2b5e1ec8 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 0d0a74b2fac 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/ [...] new 097101f880c 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/ [...] new a53870dabeb 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/ [...] new 4a2acc945c9 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 9b4bc9e4fdc 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 1 [...] new 14f060de973 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/ [...] new a13ff23a6dc 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qe [...] new c0ee26e9e16 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 [...] new 679b32af912 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] new 5dd5f787b9e 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] new 1ed17ebcf66 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] new 2542b7e38b0 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] new bb198f9f37a 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] new 802e1c98566 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new e7aca2473af 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] new 9e0eb8710e8 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 3aa725e3bd8 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] new 20e29101173 128: onsuccess: #1579: 7: Success after linux: 12 commits new 93d0dd047c5 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] new 8ed0a409cc0 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 2a9bbf148a0 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] new 1c0704bab87 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] new 18bc09bfb30 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] new 3133251a27f 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] new 94cf0ab373e 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] new 6461bbb2f91 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] new 98952ffd36a 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 8701766a811 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] new e041e57dab1 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] new af6a7ba867b 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] new 4543b1eedc7 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] new c319536cd5a 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] new 999f31cf436 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] new a829c222026 144: onsuccess: #1595: 7: Success after glibc: 2 commits new b902c1ed5b1 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] new 879c6dc41a5 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] new e6b402fcdb7 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] new e67f2ecd317 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] new 9db2e6122ec 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] new 025df71d0ea 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] new 95dad315cf0 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] new 9595a57f46a 152: force: #1605: 7: Success after gcc: 9 commits new 62e947f0d1a 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] new 7e99d5db110 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 56b02c4f5fb 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] new ee667128f6f 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 8ab7ff0f1f1 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new d426676c1b6 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] new f64df8d3e3a 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 6717efebee6 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] new e8ee703a7b3 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] new 7a9c9a7f9d0 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] new 0e94113760b 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] new 91f2a459da8 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] new 5cf0029678b 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] new fc4a5f701c1 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 71a1e15bac0 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] new 7c3eea44e14 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] new 23180475fb8 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] new a3b2d32c91f 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] new d4b1567c0a4 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] new 4d68a7ea5ce 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] new 5a88b66b357 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new 9ce6e899bda 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] new 1a83b6e862d 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] new 58f2bbeaa02 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] new 0bf5d0ca57e 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new c3c76d7b64a 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] new 184a61c15ab 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new 49be2109125 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 10aa2c4e676 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] new ba91a535b49 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] new f94807a8819 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] new f0de081f3fc 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] new 334daee4273 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new 62c5d4e7b07 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] new ee369400c4b 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] new 59d0005ca3f 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] new 07df2ee1408 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] new 8d391a09e0c 190: onsuccess: #1774: 7: Success after binutils: 10 commits new db4653ecedc 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] new eb603075449 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] new c9d71344533 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] new 4be5b486a56 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] new e833813b9f4 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] new e8f22246ba1 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] new e98d45c90fa 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] new 4751639449d 198: onsuccess: #1852: 7: Success after gcc: 5 commits new df5a9daba94 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] new 4464beeedf2 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new 080300d20b4 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] new 6a332540bd2 202: onsuccess: #1856: 7: Success after gcc: 2 commits new 61a6708624a 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] new 45a85c67bae 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] new a1c5042c216 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 9ae40c2a106 206: onsuccess: #1860: 7: Success after gcc: 2 commits new ddeae3a4d7b 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 2b88d54ef62 208: onsuccess: #1865: 7: Success after linux: 12 commits new 98db174d44b 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qe [...]
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 (d9c0c9901ae) \ 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 31848 -> 31976 bytes 05-build_abe-stage1/console.log.xz | Bin 73548 -> 73304 bytes 07-build_abe-linux/console.log.xz | Bin 8332 -> 8324 bytes 08-build_abe-glibc/console.log.xz | Bin 244892 -> 245412 bytes 09-build_abe-stage2/console.log.xz | Bin 205584 -> 204656 bytes 10-build_abe-gdb/console.log.xz | Bin 39144 -> 38900 bytes 11-build_abe-qemu/console.log.xz | Bin 31068 -> 31696 bytes 12-check_regression/console.log.xz | Bin 3104 -> 4188 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 ++++++++++-------- 20 files changed, 63 insertions(+), 58 deletions(-)