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 021cf5bda4d 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards 3bc8422ea5e 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards f02adac25ec 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/ [...] discards e931d10d191 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/ [...] discards 4942700595a 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qe [...] discards e3ac41c9d2f 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] discards f1f940cd095 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-4 [...] discards 3342d36d81e 221: force: #1949: 3: Failure after basepoints/gcc-13-4492- [...] discards 22227c81d01 220: force: #1948: 5: Success after gcc: 4 commits discards 8d1ef1710b4 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards 5eae67dab61 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards bec4180bff8 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] discards 5e076abcd37 216: onsuccess: #1940: 7: Success after linux: 12 commits discards ef9e2beb811 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards 7e553d65c5c 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards 31e8b6f4764 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards aa5dbd5b3e0 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards 692aa61e471 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] discards 9398133cd32 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] discards f6d169dafa1 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] discards ed3cc2c9472 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 470f2cfbdf9 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] discards 57985ea9a38 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] discards ef56b03c830 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] discards 082bcea33fb 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] discards c52437ede41 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] discards c63ba0ba1be 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] discards d4b1a22f9e7 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] discards 97ee7ef44b0 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] discards c005ad1a81b 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] discards 3049c137f40 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] discards 03418625648 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] discards 137bbf07d58 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards f96c5ae9649 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] discards 87a86fb0393 194: force: #1853: 7: Success after gcc: 26 commits discards 19fb1d336de 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] discards ec5937354bd 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 92132eac88b 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 4889405e916 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 9414b89e98d 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] discards 8e633e1b2a5 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] discards 8d4de579c10 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] discards 2558000ec23 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] discards bfcaa8b1ca3 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] discards a1b87ebbc5d 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] discards 3f19557ef19 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] discards 1a58f229a36 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] discards 2f883a7aaf3 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] discards 621fbca58bd 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] discards d1e7847d220 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] discards c74668de3f7 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] discards 2e7d6cc30ca 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] discards fab831c64c5 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] discards 0f62069126e 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] discards b78453f3e69 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] discards d32a0307819 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] discards 5bfe02ad1b8 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 68e483bb6d6 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] discards 0406f7ed017 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] discards 1b5c5c3ae69 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] discards 00a327fe07b 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] discards 4176d2b3345 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards dbae7240ddf 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] discards 118bdec40fe 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] discards 82223d0b6d5 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] discards 7063869cf68 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] discards ac09b5cffe9 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] discards 5e1274b2610 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] discards 9873a3948bb 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] discards 2cb73b00ce9 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] discards ffc1c5c91a0 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards d4f4d9e234a 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 87aa0c22f6e 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 31dbce070fd 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] discards 2160cbaad8b 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] discards 0e91ab35285 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] discards 03318f74355 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] discards 98ae79de254 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] discards de9c1c131f2 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] discards eec39eca55c 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] discards d7fd1bc4f2e 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 30550cb3729 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] discards 624c690ffe1 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] discards 30e6eef10aa 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] discards 9042566d7d7 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] discards 795b85aa454 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] discards ea41ec5dd78 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] discards 8e616ed9503 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 88922b1ab79 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] discards e7ed7ab5391 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards eaf1787f2ec 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] discards 49ebdfadf36 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] discards 9b6240b8108 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 2f461d86d06 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] discards 46f21f5e812 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] discards 7f34785c0f5 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] discards 7748e7704f6 132: onsuccess: #1645: 7: Success after linux: 23 commits discards bf71ea1c3ef 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards a63a7f1d274 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] discards 9d2e9a17ad2 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 1a51818869b 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] new 59848a45128 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] new 7611a7a2815 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new cb957e234b1 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] new da347e538f6 131: onsuccess: #1644: 7: Success after gcc: 10 commits new c0533b3c06a 132: onsuccess: #1645: 7: Success after linux: 23 commits new 1bbc4f443a5 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] new 1950a4fda7d 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] new 97692dee55e 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] new a0e939cba3d 136: onsuccess: #1650: 7: Success after binutils: 2 commits new e8a3cfefda8 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] new c0b697e96cf 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] new 9ddf1b04f30 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 7d2a8f96129 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] new f8007e1313d 141: onsuccess: #1656: 7: Success after gcc: 7 commits new f745f0b0e17 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] new a0d79e97de2 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] new 7523e4a8881 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] new f72ffc1a465 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] new 266f206dfaa 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] new b9cc47001f1 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] new d66a3e68b47 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 0f1587e58a8 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] new 411e36468e0 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] new 4bbd8caf4b0 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] new a27d7800085 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] new 630e52a0463 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] new 4cc9e9846e0 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] new e6aa7e3cda3 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] new 91384182396 156: onsuccess: #1671: 7: Success after gcc: 3 commits new e8f9907cf98 157: onsuccess: #1672: 7: Success after gcc: 2 commits new fbe7016b064 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 36078e23cf9 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] new 7b5dc6a81e3 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] new e9026b9d45d 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] new bec3a3e9883 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] new e76b43eedeb 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] new 820d26c0087 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] new dab80a84408 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] new 471445cc181 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] new 35d95a8d3e9 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new d9766808e53 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] new 590af7ce293 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] new fb9298e0c85 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] new 59a35f2ce44 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] new 52b2d1d0eba 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 94e0e45be9f 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] new 9072c64ed44 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] new 82d78ca74d9 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] new e371dc1f8d8 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] new 3759718b4d8 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] new b8a23c28604 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] new fab10753465 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] new 2787ecd9961 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] new 57fc4b982f5 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] new fba7b2e1608 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] new 98e4c8d745f 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] new 1629030409c 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] new 9fdfc2b86c1 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] new 98ced017966 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] new 7c29bc70602 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] new 389d34c51c0 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] new ed074860085 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] new c56cf4d2751 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 48109113e40 191: onsuccess: #1846: 7: Success after binutils: 4 commits new f243799fc8c 192: onsuccess: #1848: 7: Success after linux: 213 commits new 6e15dc7ad7d 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] new 23801eda410 194: force: #1853: 7: Success after gcc: 26 commits new 75b85cda06f 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] new 2be9364f678 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 948d7f84869 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] new 9c0eeae93ce 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] new a2726344d19 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] new 2eea1efdb70 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] new ec205a521db 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] new 26e02dc0bb3 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] new d9a0cb9d37c 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] new f57d3366109 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] new d85547a8808 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] new 73604b0377f 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] new 3ddbccc2332 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] new bf6481df901 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new 0613b5963b5 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] new 0931d8c6399 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] new bf191222038 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] new 3bb8fa81a68 212: onsuccess: #1934: 7: Success after gcc: 3 commits new 6086e9fb022 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 7b1f766828e 214: onsuccess: #1937: 7: Success after binutils: 4 commits new f5257ae55b7 215: onsuccess: #1938: 7: Success after gcc: 4 commits new ef25c49db1c 216: onsuccess: #1940: 7: Success after linux: 12 commits new 465ec422da0 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] new 427bdeed69c 218: onsuccess: #1943: 5: Success after gdb: 3 commits new 444b6c843fb 219: onsuccess: #1945: 5: Success after binutils: 8 commits new a09b6ae8719 220: force: #1948: 5: Success after gcc: 4 commits new ed58e529987 221: force: #1949: 3: Failure after basepoints/gcc-13-4492- [...] new 3c2650f2051 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-4 [...] new edcae4c89f3 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] new ab577298ec6 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qe [...] new 994b0ae37eb 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/ [...] new 41a2d5546c7 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/ [...] new 54cf66bf60f 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new bc3b5b79a85 228: onsuccess: #1956: 7: Success after gcc: 5 commits new 1385adeb5c3 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/ [...]
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 (021cf5bda4d) \ 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 1784 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2796 bytes 04-build_abe-binutils/console.log.xz | Bin 31816 -> 31764 bytes 05-build_abe-stage1/console.log.xz | Bin 91860 -> 91524 bytes 07-build_abe-linux/console.log.xz | Bin 8632 -> 8600 bytes 08-build_abe-glibc/console.log.xz | Bin 236656 -> 235940 bytes 09-build_abe-stage2/console.log.xz | Bin 227592 -> 224280 bytes 10-build_abe-gdb/console.log.xz | Bin 39712 -> 38976 bytes 11-build_abe-qemu/console.log.xz | Bin 30672 -> 30364 bytes 12-check_regression/console.log.xz | Bin 3568 -> 4172 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/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++------------------ 20 files changed, 45 insertions(+), 45 deletions(-)