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_check_gcc/master-arm in repository toolchain/ci/base-artifacts.

discards 8dccaf458a3 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] discards 45a855bc815 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 145d6f1eded 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards a139333be94 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards 0dd827eeb69 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards 3a1ff115a3e 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards d934942053f 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards b55b72c9071 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 02a3ec31df7 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 67620617c87 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards f1b0bb4159d 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards cd04edb778c 208: onsuccess: #2012: 1: Success after linux: 12 commits discards b9811a963c3 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 73a230eb90a 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 9d825286068 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards b8e588017b3 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards d2761d4a7a3 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 9d35409abfa 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards d5c0317d3e8 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 8cefc7ed3e2 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 3f2ec02fe59 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards a34352e4cbc 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 1861244a616 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 1d008e4d25d 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards aa7e2e55dd1 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 1b52dbc472b 194: onsuccess: #1995: 1: Success after linux: 517 commits discards e337f0d7e38 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 227cbec0214 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 967c9e808ca 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 9e6e4ee35fa 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards d76a289f906 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 8cd0647ce25 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 2cac5bea53d 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 3babc9650e8 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 7d024921928 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards cbe6f2247e9 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards b0845e73c10 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 06e124397ab 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards b6bd9c07155 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 712e65ce794 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards beab6eee269 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 3d987988f9c 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards d00e11942f3 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 176deafd8b8 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards c592aac72e0 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards b9fc0fb95d2 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 4e882d342d4 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards ce527eea45b 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 766600578d5 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 92519576b35 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 5f16cdf5e21 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards fe1687ceefd 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards ca767de3b18 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards c145ba8d99b 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 34078e43f52 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 2a890f62b2e 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards fee87cd5a8c 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 43f24a538cb 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 0e162c58219 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards a3374d2817f 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 1b851364f00 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards e8d9e39999d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards d604e0e73f8 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards de1a7d93693 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 7d5cc6912bb 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 8ff8349a0d1 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards f080d0f562f 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards dc00abdc0a8 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards a2966e8eba0 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 9f44b7cc0c9 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 360c344a1cb 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards d723722b208 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards ea91c4e8a79 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards df5b2e0ff17 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 20f9cb56643 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards f5f1d994e06 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 1b9a8f9f7fe 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards c3b8b0c5a4b 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 42c8bc25309 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards ecaa360e26c 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 592406c80fd 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards e42376f147a 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 137405849a0 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 9532ad0f9b4 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 994a24ad4d1 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 9f1866e1b0f 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 727897aed29 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 839957dad6b 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 09c02a92fe0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards b4e1f563a30 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 36b68e73698 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards cd1387becfa 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 88bb0a897a6 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 0e9bd01959b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards a3daeb1b2b9 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 68fe1ac4d16 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards e9b95191f3f 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 17b8b3b6027 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards a57b9ae2662 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards ecb3dd09545 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards e9abb7cf274 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new c32dc01cc2c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 3ce6c5608f8 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 8077e8e821d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 70e16ead027 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new dfc3016e4c7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new ad5b1888005 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 5abeed55a4a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 4e5aa76abd4 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new fe12e878c86 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new f3afbb85601 128: onsuccess: #1723: 1: Success after linux: 12 commits new 3d4fb30adb2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 60081ed32d8 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 2e2b2358f01 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new b81b4c789c4 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 4261df96d9c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 852203b66dd 134: onsuccess: #1730: 1: Success after binutils: 2 commits new eccc223b95a 135: onsuccess: #1733: 1: Success after binutils: 5 commits new bc6299575ee 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 8bfa80f01e2 137: onsuccess: #1736: 1: Success after gcc: 5 commits new e61fe561c68 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new cc66e678389 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 3175e92cb4d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 9a9258f22c4 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 6c513739b23 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new e9c2186f3b5 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 92a63725c1a 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 7e8f362ca9e 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 01041203429 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 27b6aee0659 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 6bf2049ec91 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 7f7b54ba8e4 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 124510e8131 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new dc4347afbb8 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new d7b58671bdf 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 88744078a8b 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f2e80dab0a0 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new ff56fa2a299 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 1225f36a404 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 58eac5f4f5c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 37a56359c95 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 5d3c269528c 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new e18e751bae0 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 06aaaa289fa 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 2668b0319c1 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new c19f6ab7013 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 9545d88cace 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new e57533ef443 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new ef1275f088c 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 9db1dcc32e2 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 3ae8e3b8b22 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new c11fa492770 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new eea8f985123 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 4043fb0aaed 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new ce994361496 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new c70f565d1c2 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 81c79e12d45 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new c080dbe8311 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 43840eeb6f7 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new a5be5b7dd49 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 2fde0061bb0 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new b4369d22e99 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 161a17a717a 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 16b7fb454a2 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 9880d4ff578 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new caee53c7c1a 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new a1802759052 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new cb43cf6a050 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 411455a874c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 6693f4a8c8f 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 104a2a93a5c 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new fb79b28f5af 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 07f0171a7f5 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 0c3986d9711 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new ea092a86e23 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 930b355e5e6 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 17979e28b19 194: onsuccess: #1995: 1: Success after linux: 517 commits new 33ccfea5c3a 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new ebd54a7876e 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new e4f541b52df 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 454495fed4e 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 4e98d3ec3ac 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 9bcedb01d95 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new db8bc8df7a1 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 6b2e6b81d91 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 395e898d114 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 00ee491825b 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new d157d94d309 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 7ca4cd08545 206: onsuccess: #2007: 1: Success after gcc: 2 commits new beddc81521d 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 9d3059b81f2 208: onsuccess: #2012: 1: Success after linux: 12 commits new a559eae6cc1 209: onsuccess: #2014: 1: Success after binutils: 12 commits new ea424bad2e0 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 530203adae0 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 48967df27c5 212: onsuccess: #2022: 1: Success after linux: 3 commits new 4258a1420b6 213: onsuccess: #2024: 1: Success after binutils: 3 commits new a4d4897695b 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new 57cdfc5e76f 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new 30f9d335128 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new d0e35827f9c 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new fb1f6ae6383 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 953aa33427a 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] new 0a2b6eafb59 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...]

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 (8dccaf458a3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]

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 1760 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31668 -> 31952 bytes 04-build_abe-stage1/console.log.xz | Bin 91428 -> 92432 bytes 06-build_abe-linux/console.log.xz | Bin 8644 -> 8620 bytes 07-build_abe-glibc/console.log.xz | Bin 237620 -> 237552 bytes 08-build_abe-stage2/console.log.xz | Bin 224856 -> 225044 bytes 09-build_abe-gdb/console.log.xz | Bin 38708 -> 38716 bytes 10-build_abe-qemu/console.log.xz | Bin 30276 -> 30588 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2684 -> 3120 bytes 13-check_regression/console.log.xz | Bin 5876 -> 6904 bytes 13-check_regression/results.compare2 | 41 +- 14-update_baseline/console.log | 64 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 2710160 -> 2749848 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2303288 -> 2282668 bytes sumfiles/gcc.sum | 2324 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 888500 -> 894668 bytes sumfiles/gfortran.sum | 18 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213264 -> 213168 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427160 -> 432108 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1293 insertions(+), 1240 deletions(-)