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 705027a25d3 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 4199a67ece5 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 4c076ffd5d0 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards b13f1b859f6 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards abcd300fa3a 208: onsuccess: #2012: 1: Success after linux: 12 commits discards bdaacb27c49 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 55756871ae6 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 5ed4587f356 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards a95a3307f2e 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 628939c85ae 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 5acc2192fa3 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards cfc4889f7a8 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards b7f6930b6b4 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards c1c207781a4 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards be722c82ad1 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 6995bbbc5c8 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 8bca49aa67b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 0083fdf6c5d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 331a40d7ad1 194: onsuccess: #1995: 1: Success after linux: 517 commits discards b6b37bc9bd9 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 81766c7c50a 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 5c0d843568a 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 2e7dda6dca2 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 1b7ec68d45d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 368ad50a5ff 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 87e04a1ff77 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 7fbe6bc05ad 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 8b327978242 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 53d9b440956 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 23bc68479f0 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards f8236457821 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards fbac3fd058e 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards d837bb76acb 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards b9c5313d4ec 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 4e9bdf680ad 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 3f0aa0414e4 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards fdf138bb0ca 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 952ffb49c31 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards f52e4dcc9dd 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 3f01197b176 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 075bd39ecb7 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 712fd879fee 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 6f8d2e23f55 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 1bdd33f6438 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 0fe09f1fca6 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards c7b2b8917d4 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 40459f70692 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 8257627461e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 99de173533f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards ad3fd8549ca 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 54f99ae3823 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards c4c5cef2d49 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards f6a934e2214 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 4219cdcfd49 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 112cbe0c0f3 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 348e24e4726 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 7a1e2ce374f 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 7125b7a4ad2 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards d38fb7e3faa 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 05e8b6d7fe0 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 5a72cb4cbd6 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards ebbf64821ef 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 8fb59b48b85 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 6cd54830d27 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards fcbba4921e7 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 99993f77443 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 83279c225f2 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 5138e64ef12 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards cab760f6bf0 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards fad72cbd845 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 71f7b4da119 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 6c929b09ce1 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 9dc072c7567 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 78d67571593 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 1bbaf895473 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards a851c0d5d56 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 830bb0b8656 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 8e825e6367d 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 678667a0170 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards fd4269c3154 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 106b4a421e6 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards db4ea052bfa 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 538c30f303b 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 34d2a48e61d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards bd1b4ed92da 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 80363965cce 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards b03f93af2bf 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 0aa6e690a4e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards b42a3529a86 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards df6154f3f28 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards ef0d70689f0 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards fa8bb6dfcd4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards d4c6bcc1243 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 56813a168d1 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards af35af6d411 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 0ba15f9c4c0 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 93aa3a17446 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards bde1d9cadac 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 5c4645eb529 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 6a5675e8af1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards e257484f5fe 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new fb3eda9cabd 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 166693fb527 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new ffbbe376248 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new a8a68f301e8 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new 807e3ba8ada 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new e8626250af5 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new f285520d6ad 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 602c88719a6 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 75f91099968 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 77e14b6460b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 22ec2d784f0 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 65870ccb71d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 3bb8cdffc72 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 31f8777bf72 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new e33e2f5dd98 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new d5cfc85afd8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 9ef035f434f 128: onsuccess: #1723: 1: Success after linux: 12 commits new af23b03c7e5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 29ef8e75f59 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new c0c733bff8b 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new a02e63fbce7 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 7a1496811a5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 90ae89d5b72 134: onsuccess: #1730: 1: Success after binutils: 2 commits new a2d90e676a0 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 8c5692c455d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new aeecab173a3 137: onsuccess: #1736: 1: Success after gcc: 5 commits new df2f36faf57 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new e30c6c656d1 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 121b2c8742a 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 369ff03144e 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 4e10a672345 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 30625542840 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 3dc8f2e186f 144: onsuccess: #1743: 1: Success after glibc: 2 commits new fbc75855005 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new ece49fe7f94 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 80c11907366 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new ac93173e88f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new eae6288f305 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 4cec6b48cbb 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 8f5dec2f10e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 6eb50e67abe 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 649fcd802f8 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 94ec4d3115f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new f6773ee1395 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new fc759c56afd 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 8e55659970c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 64b16b2dfcd 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new d23b1df8573 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 8383c918cc6 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 8f4fd4792e0 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 6c62dba2d4d 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new dc5f849d06a 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 37df0f7b210 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 73de395171b 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 4c731dd0983 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 6b4fb514a7a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new a2aa5ebc370 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 76066821b0e 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 323de939d95 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 6f3f2ffca95 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 9679d0ad49a 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 03b31a5523b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new ff6e45c651d 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 90790cc401d 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new dca590f987a 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new f4146a8150b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 6265fb8bc44 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 05217933436 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 05aae23d47e 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 29b5089822d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 21c325e5137 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 0ffd53fda50 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new c872b835726 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new e75e4e10f4c 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new e2223774c79 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new a436a788157 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 27a6e822d8b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 5ca621569f5 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new c303c37b312 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 0e6de209f71 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new dd170886744 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 01c10b32e43 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 2eb0249bcd9 194: onsuccess: #1995: 1: Success after linux: 517 commits new f380aebdbda 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new b7a71475eb8 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 7d474f436f4 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new b417d3c46c9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new a4d02bcd817 199: onsuccess: #2000: 1: Success after gcc: 5 commits new ae4cc1c7e9f 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 1b95a55b814 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 29ab552051b 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new afd2b9bb6c1 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 083c6514b3a 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 898d0dea9be 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 2d4a1507bfe 206: onsuccess: #2007: 1: Success after gcc: 2 commits new e858b1c32c4 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 41485d27953 208: onsuccess: #2012: 1: Success after linux: 12 commits new bd0490200df 209: onsuccess: #2014: 1: Success after binutils: 12 commits new de93a56c606 210: onsuccess: #2017: 1: Success after binutils: 6 commits new bb3116eeff6 211: onsuccess: #2020: 1: Success after binutils: 10 commits new abf8be904e5 212: onsuccess: #2022: 1: Success after linux: 3 commits new 08d1bcaeb16 213: onsuccess: #2024: 1: Success after binutils: 3 commits

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 (705027a25d3) \ 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 1792 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31584 -> 31812 bytes 04-build_abe-stage1/console.log.xz | Bin 91152 -> 91684 bytes 06-build_abe-linux/console.log.xz | Bin 8772 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 238520 -> 236872 bytes 08-build_abe-stage2/console.log.xz | Bin 226796 -> 225376 bytes 09-build_abe-gdb/console.log.xz | Bin 39260 -> 38880 bytes 10-build_abe-qemu/console.log.xz | Bin 31216 -> 30832 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2468 -> 2440 bytes 13-check_regression/console.log.xz | Bin 4908 -> 4920 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 4 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2712628 -> 2736348 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2305704 -> 2280328 bytes sumfiles/gcc.sum | 2272 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 891512 -> 891636 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213104 -> 213236 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436304 -> 429620 bytes sumfiles/libstdc++.sum | 2 +- 36 files changed, 1207 insertions(+), 1259 deletions(-)