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 2e1b1453c8 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/g [...] discards 7240c625ed 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/g [...] discards a31ec5071e 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] discards 2e1b9904ae 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 598d4cb1c2 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] discards a4779a1702 194: force: #1853: 7: Success after gcc: 26 commits discards 2ba3771d2b 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards 03470bc171 192: onsuccess: #1848: 7: Success after linux: 213 commits discards fd90c1ae47 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 68ffe909e6 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 41b906ea24 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards 15d5e78735 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards 5c1af243c7 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards ff62b5303b 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards 1b8d84a287 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] discards d3fbd3168f 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] discards 76f810e645 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] discards bda776bba3 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits discards 6566942003 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] discards 3e96eb3c19 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] discards 4ef603055a 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] discards f4b6223233 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] discards 48e8d5ead9 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] discards 55e1035100 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] discards dcb58c4d74 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] discards da096d8c68 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] discards d5e9a75b32 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] discards 5361775c1b 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 47d6b216c1 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] discards 4e6e0d9966 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] discards 617555dfad 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] discards fe43e6de83 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards add206a158 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 6a9a804caa 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards 9990c49e81 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards ea85d0c49e 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards 99e13676da 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards c1e1b73d0f 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards 23cf7795fb 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards df5e09493c 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards 4d59539748 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards c7b7c494f1 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 09aa0245af 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards d9498211d0 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards be5bcc9c68 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards 4b763d4d29 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 009965076d 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 8441aa9541 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards ad2e30bf2d 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 2c0cab5109 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 2da9726108 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards c703086991 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 588518cba4 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 3307a4ff89 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 3d6928ca38 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards b60ad10118 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 8c4d0d7e4e 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 8a1c215117 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 890e508e0b 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 22de1f0e56 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards f3820438a8 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards ae6039639a 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 2c670f5aba 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards c4a5ea76c8 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 6887443311 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 500170464b 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 8c8ab1ad11 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 8abfc333e6 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 534bf9c91d 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 70bc4c27e4 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards dd867e4876 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 2007ccaf20 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 1e6aec3993 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 1e4255153c 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 5cf64548b7 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 71c4050d1c 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards cef95694c2 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards f359aedc33 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 006b89c357 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 51ee776fb5 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 80f7ec939b 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 537636402c 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards df889570fc 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 793407972a 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards c771f74701 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 19e6872289 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards f8caafa270 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 006b905053 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 9063246d92 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 512dec6f0f 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards acd7573688 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 5126e08a1b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards e3ca9f0684 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 1168dc7da2 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards b209348b77 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 881454e59b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards e453a170d6 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards b259b081de 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 723cfc0fe2 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards df0eecaf77 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 1a8fc6c306 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 2d8ed20d56 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new dde89de611 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 8cc60ca942 101: onsuccess: #1609: 7: Success after binutils: 78 commits new fc37eda50c 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new fc2d3040dc 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 62f11c9ce8 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 93a616bd96 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 61495d5d98 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 55f8121dd7 107: onsuccess: #1618: 7: Success after gcc: 2 commits new e2c94cafa7 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 51f56a5694 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 9a275fa6c8 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new bfc5e230cb 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 272fe097df 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new fb6fa0696f 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 7a90df8893 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 471dbbd0a2 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 8c807a0525 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new d4997e9960 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 7f4e7e06c8 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 54eb76ddfb 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 5ca57250ee 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 8f21ee3e09 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 0fa0c8d5c3 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new c6ea493887 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 60ac657699 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new c7735de5b1 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 43aecb4e59 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 4a998e1e91 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 0e4c09e3bc 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 9403e37970 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new ade71fb046 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 9137ea5e32 131: onsuccess: #1644: 7: Success after gcc: 10 commits new fc8acd8754 132: onsuccess: #1645: 7: Success after linux: 23 commits new de36f4349b 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 5199cb966f 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 4216ff1b64 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 7979b6a3d0 136: onsuccess: #1650: 7: Success after binutils: 2 commits new c3272395b0 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new de54203996 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new bab642771c 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 364b4bab20 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new ad47ebb9ee 141: onsuccess: #1656: 7: Success after gcc: 7 commits new f86ec8ae14 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 38534ed68c 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 2d593b2202 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 64adc0c374 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 14049f155f 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 2123fe340f 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 353ac04e06 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 62ba400b5e 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new adf671302f 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 60cf5b143c 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 3ff837fb9e 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new d4258f8adb 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 5c19fe815d 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 6494ecff30 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 5ff035cdf9 156: onsuccess: #1671: 7: Success after gcc: 3 commits new ba3026057b 157: onsuccess: #1672: 7: Success after gcc: 2 commits new fb1c1568f0 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 11310f3066 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new baa2222a9d 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new b7c505689e 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new 1b910e7641 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new f5ce6071ab 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new 7a5aa52b59 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new 0d7436e07f 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new 900406ffee 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new 28f913f6d1 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new a9497dcdea 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new d6f3dd5e18 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] new 9cedd493e2 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] new 96920531dd 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] new 46cc8c63bd 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 63c78898ef 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] new 23dfbeb55f 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] new a6cc3197ea 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] new e7422f7a1c 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] new 1925e1833e 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] new 3ca09b71c3 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] new d22e44ff3e 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] new 885d3bd159 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] new 93c4e19a83 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new de39f783c2 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits new 69d3fdb437 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new f72d743cea 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] new a2d5813415 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new a6b96e1526 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new a2269eb3d8 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new 5936bbb1a1 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new e645951333 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new 075ffd96be 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 255c527bcf 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 19ebf9b4b9 192: onsuccess: #1848: 7: Success after linux: 213 commits new c9eff69c9a 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new 851b1b222f 194: force: #1853: 7: Success after gcc: 26 commits new 3dedd01a46 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] new f84abce755 196: onsuccess: #1855: 4: Success after gcc: 30 commits new f84c18fd00 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] new 954442fb09 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/g [...] new 6d5b725d25 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/g [...] new 23ec8a4d60 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/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 (2e1b1453c8) \ 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 1668 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 31432 -> 31452 bytes 05-build_abe-stage1/console.log.xz | Bin 91348 -> 91488 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8624 -> 9468 bytes 08-build_abe-glibc/console.log.xz | Bin 235232 -> 234644 bytes 09-build_abe-stage2/console.log.xz | Bin 224484 -> 223728 bytes 10-build_abe-gdb/console.log.xz | Bin 38668 -> 38536 bytes 11-build_abe-qemu/console.log.xz | Bin 30976 -> 31568 bytes 12-check_regression/console.log.xz | Bin 3872 -> 4976 bytes 13-update_baseline/console.log | 42 +++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +++++++++++++++++------------------ 23 files changed, 55 insertions(+), 55 deletions(-)