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 59b2fca441 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 0c450100d5 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] discards 02c0bbdbd6 194: force: #1853: 7: Success after gcc: 26 commits discards 4a6cddaf44 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards 4ed0672e07 192: onsuccess: #1848: 7: Success after linux: 213 commits discards f9394804ae 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 82c2845682 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards fb32d787a4 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards ae543da45f 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards 37dc3c2154 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards 04bbbd9b6d 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards f2b4007736 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] discards eb01ea05a4 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] discards f6a4d72bc4 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] discards c0dfee6e12 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits discards cac3aa725f 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] discards e2d73b5260 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] discards 65388c2450 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] discards ef7e527b1a 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] discards 6bfbf0e78a 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] discards ae00a1aaac 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] discards ea2529677c 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] discards de5ce5c021 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] discards 34b57a5a6b 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] discards 62d893866c 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards d342c9f0d1 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] discards bdd8c80399 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] discards 2a922bc5a5 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] discards d6e3306971 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards 0038f75b8d 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 10088170ad 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards 4d10c19a4a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards 0c4681c204 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards 3b08c13118 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards 7ec9a4a14c 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards c3a0802928 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards 5079fb0f93 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards 9f0db99aa1 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards 3a21763ca7 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards ad3f10ce96 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 6196c5337d 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 65e426c7c6 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards 08dd62c66b 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 0c5ff29de7 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards aa2f5309c5 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards 143369cc25 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 5d6f5b58bd 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 096780acc5 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 52e2bb46cb 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards d3f79da9c1 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 3accb3a201 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 342f2ccd84 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 2de125b66c 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards e74262a521 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 06a87af61b 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 07a5daa1fb 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards b19c2e6049 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 5fae420d7d 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 83cbcb29fa 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 080414fbcf 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 287f521f66 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards c56cf2746f 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 3dfe433e2e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 44f03966f3 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 9e0923fb20 132: onsuccess: #1645: 7: Success after linux: 23 commits discards af4c785411 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 8d214b9c74 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 38ce97e05b 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 9161ad8040 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards dfb6208db5 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards b7f64b908c 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 082b5f446f 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards eb39a24fd0 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 41e556a4e1 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards a246a434be 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 9e32067533 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 4b4f5e977b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards b289421e86 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards fb5ec03cd3 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 5f01c56cb8 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 88d052fb67 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 35af827aea 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 14667e3a37 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 5867a7e229 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards b3236611ca 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 9cfc7b1fd0 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards bb665730e6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards e6722e5b60 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards d90550b12b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 1e3ef25e7d 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards b1735755ee 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 374554ac16 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 6c41028305 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 4805b8a912 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 8c82dd99ca 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 8a6559c50c 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 3a97ef4c36 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 5eebb005c8 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 8a54a5cde5 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 5f7d709358 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards a24e4da003 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 3a840a696a 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 3106e56ce4 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 8acccadcb2 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 13b765a3ad 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new b6933c1782 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new c0a45da563 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 2b5b9da485 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new d9e40b5baa 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 447debf889 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new c73d260d2e 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new a496eff643 106: onsuccess: #1617: 7: Success after gcc: 2 commits new bd1ac62678 107: onsuccess: #1618: 7: Success after gcc: 2 commits new cec8fa4e51 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new f0e6647737 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 3ede723d31 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new a71f367356 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new d333678ea2 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 314cc0229f 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 3db832a292 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new a12b75a62f 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new a9d3046bbb 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 75e1d0004f 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new f0c9ee5560 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 4c55d745bc 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new b8b2ee3786 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 6cc3088167 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 2108829382 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 914d3e41c5 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 178e208a81 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new c42e42255d 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 80c3a0213f 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 41ae594758 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 9a6a9cc810 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new feb1073627 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 04f629b860 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 0545ecf8a4 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 76e9852da7 132: onsuccess: #1645: 7: Success after linux: 23 commits new 32842e4ad4 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 2956d10e82 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new bda9fe21c9 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 81e2d62a37 136: onsuccess: #1650: 7: Success after binutils: 2 commits new f2097962c0 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new b7295e9329 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 686a7d2d48 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 2689af2ed1 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 3d3679126f 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 31a550bc19 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 462a324b69 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new a194364fd1 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 4c5b33f079 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new c14919c3ff 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new d6a81de2c5 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 105b5b26c4 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 2c2880bef5 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 014cf914cd 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 83abd3201a 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 8150bbc68f 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new c3551d2ab2 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 5299591030 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 372c15f3f4 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 251506e4e1 156: onsuccess: #1671: 7: Success after gcc: 3 commits new dab9a3c9e6 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 8c45a821d9 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new c1c54fd263 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new c30fdb2ed2 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new c80a2f5805 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new cc4d2dacf6 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new 946224f2bc 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new 6974a3be6a 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new 5476dc2d9a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new 56a05e1325 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new c3625145d2 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 005dc069db 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new d3c8d78d1d 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] new 77fa9e55fc 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] new 8a83ac0f61 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] new fedfceb0c9 172: onsuccess: #1687: 7: Success after gcc: 11 commits new df3421eab5 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] new 3432ff2e19 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] new fbc65997bc 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] new e62f5b1f68 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] new 52c71b7cb4 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] new 662755a962 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] new 5f112ca778 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] new a0947a26f9 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] new 67eb56ed20 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new 227c8842bc 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits new 1cdf13c92e 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new 006cc1f769 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] new 030f9044e2 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new 0f9f6ac72f 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new 8bf8e9de39 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new 87fb6da03d 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new 384a3455d6 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new 7f97376a9a 190: onsuccess: #1834: 7: Success after binutils: 25 commits new af274f21d7 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 9826523b9a 192: onsuccess: #1848: 7: Success after linux: 213 commits new db75d51844 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new 655dd98356 194: force: #1853: 7: Success after gcc: 26 commits new 301ae6843f 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] new 309ec12528 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 1ba0dae38e 197: onsuccess: #1856: 4: 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 (59b2fca441) \ 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 -> 1896 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30364 -> 30268 bytes 05-build_abe-stage1/console.log.xz | Bin 90132 -> 91080 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8736 -> 8332 bytes 08-build_abe-glibc/console.log.xz | Bin 236564 -> 236244 bytes 09-build_abe-stage2/console.log.xz | Bin 202160 -> 220564 bytes 12-check_regression/console.log.xz | Bin 2940 -> 4136 bytes 12-check_regression/mail-body.txt | 9 ----- 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 11 +----- mail/mail-subject.txt | 2 +- manifest.sh | 35 ++++++++++-------- 20 files changed, 63 insertions(+), 76 deletions(-)