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 eaeedfbebf30 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 3a4db5ebe276 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 5159b1b0c2f8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 55ec197ad94b 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards c86b1900ca0f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 98a712bc39ca 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 71505b3ec30b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 4112211d6486 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards dc6ba2df11f6 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 6c0e6c73b775 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 6bda66723789 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards abc3da95ac35 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 126cc50ab855 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards db13e391df07 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 2275f99d0354 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 90411bd12935 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards ef19cfbd1781 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 54abd9287e52 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 224b233f1014 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 1f861ed957e9 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 4c462f998a29 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 3b82008b2b2d 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 645d8c65550f 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 15f8648282e1 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards e1c80f68fe05 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 20233b4c0729 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 5f81e15b1e04 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 799e63d83f9f 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards b8e144ee9797 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards e66cc9ba8d69 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards ce9b8469a680 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards df2abc4e8784 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards ae4213dabb0f 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 4ff7f9e2f2ea 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards f2bc3e2be599 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards a07e5e3ae7d0 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 1e95b74e9e9d 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 781344fec09c 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 528008091d90 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards f1d81d9b511b 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 9e9364f78ba5 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards f0734a56e498 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 7c22fd93211f 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 115e9172474f 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards a05f61935b8b 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 72307f6b89ed 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 606fd9c25776 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards cdcf2a8f58af 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards 021ee2c2dbcc 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 76f2299e6333 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards e2392cd547ff 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards b195bcb0d24e 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 24026346e972 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards a4c3485a4a57 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 6876672eb9c6 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards bb5a5e8fd782 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 8db23ad2b479 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 65317223f166 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards dabade18b2ea 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 78823e2dfed6 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 4a238c37499d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards 5e6f4e519108 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 22368e7d0887 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards e5fa9b49447f 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards d4b3883c3fce 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 503c14a0f551 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 0883cfa2928d 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards bc666eb2a392 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 6d572ee992ce 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards b7d75b15bb01 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 3eecbe042509 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 1d1fe3a1d0e6 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 141c954fa0e7 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 256ee551ab98 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 2514f5b434ff 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards e3e175073c0a 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 2debd64e695c 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 0b937ad92439 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards e6ad283a23ef 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 33ce5aba1d6a 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards ce52e91fe415 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 90cfdae9f8ea 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards d3c89b368eaf 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 7ba6c4c01da3 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 4a5500285401 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 1d4f901f7a73 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards badbe4f93842 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 29a89372d2bc 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards ee9454f19f42 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards 371ee65dbf0a 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards cb197cff5798 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards 4569335d7aec 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards 31efa9f1f629 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] discards ae02e60bc434 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards c6131f1c0450 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] discards 2d24995b97bc 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 1732c2e715b3 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards d730baf822fc 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] discards ea9c3eea2cbf 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint [...] discards b44f5c2224b5 150: onsuccess: #1749: 1: Success after binutils/gcc/linux [...] discards cebaca07e7d0 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: [...] new 446fdfe1dfc4 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: [...] new e37931a516f3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux [...] new 0af33cc6a538 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint [...] new 18686176b12c 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] new 7b2d9e4e5e58 153: onsuccess: #1754: 1: Success after gcc: 2 commits new c0ec92fdf39e 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new c670ebb8a605 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] new bcd9a15ad28b 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 24d5125e01c5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new 2ad389cdaa20 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 1718dc72d6a7 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new c4b40b5e0094 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new 1e14881db9d2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new ba9c0c3d82ac 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 67fb83e3dcf7 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 1f81a1a66d8a 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new bc22f8857cc2 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new a758d5a4d3ee 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new 8c749d625702 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 9014b4fd750c 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new ceb45f47bccb 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new c0fa322e178e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new c625c5654548 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 1e6703ff6cf1 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 45e8537e6603 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new d04a5cdde038 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 3a69ba2fda06 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 760262dd7481 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 6df9c490e484 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new d5dcc1780a8e 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 5ed8d7fb4dd8 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new 85712818fddf 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new 5dbb4b050e1f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new cffbb5020a80 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 08b01b9d1faf 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 858e0e726fb3 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 45dcdbb2bf3f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 8518edb64b85 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 65f690c25898 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new bc8825da9999 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 7635b66d604a 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 1671d359729b 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 52de999f5a6c 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new e4fd8ed5810f 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 1e1ce9c91ed4 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 9218f0891f32 194: onsuccess: #1995: 1: Success after linux: 517 commits new 800fcf8a7ccc 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 035c9dfd6c20 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 43a3d05cb86e 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new a55617534d66 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 54d945e69dfb 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 1421cb78fbe9 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new a2f2153e45d5 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 32e4e6d98f09 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 4e168576d641 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 905f772b17dd 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new b2fc45b788eb 205: onsuccess: #2006: 1: Success after gcc: 3 commits new d6cc7ef82e92 206: onsuccess: #2007: 1: Success after gcc: 2 commits new c16043f3c111 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 6000f3e7ed5e 208: onsuccess: #2012: 1: Success after linux: 12 commits new fe60b74d1fe4 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 49bf27a30e23 210: onsuccess: #2017: 1: Success after binutils: 6 commits new c24888e6d148 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 5982686cf0cb 212: onsuccess: #2022: 1: Success after linux: 3 commits new f839f0a4f425 213: onsuccess: #2024: 1: Success after binutils: 3 commits new d4ff1ebd9c7c 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 1940cd420dcd 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 6ae0e9f84665 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new 9fb34c2941e3 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 176fecbab806 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 5ae26f010f3a 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new f22a32930a4e 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 5f109e19fa21 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new c47b23af178a 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 37283eacbc5f 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 60806d72efda 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 47cf2a7a2778 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 62bcb20bb243 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 95b0d8a89e76 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 07923b19c020 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 8ef40a95f95d 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 7299d54234e1 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 139176510976 231: onsuccess: #2047: 1: Success after gcc: 4 commits new f1ceb4e05fab 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 13d029a6fdbd 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new c073e309f48f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new f27ca2705c9a 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 50c30b59653f 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 2a2873bed511 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new f35b8fef6a0b 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 1c52ec65ad2c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 1784b127d780 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 2b2994eef8ad 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 1285b4f91031 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 9061afb3199f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new f979389bf2a6 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new f9fbbfef2dff 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new ac0fd2d76ac0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 96525e2573fc 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 9ad4e6b78649 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new bd090c8567ee 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new d7ad7a397f72 250: onsuccess: #2066: 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 (eaeedfbebf30) \ 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 1800 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 32064 -> 31832 bytes 04-build_abe-stage1/console.log.xz | Bin 91772 -> 92060 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9772 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 234904 -> 236008 bytes 08-build_abe-stage2/console.log.xz | Bin 223724 -> 223876 bytes 09-build_abe-gdb/console.log.xz | Bin 39144 -> 39064 bytes 10-build_abe-qemu/console.log.xz | Bin 31256 -> 31544 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2528 bytes 13-check_regression/console.log.xz | Bin 7064 -> 6976 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 114 +- 13-check_regression/results.regressions | 30 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 30 - sumfiles/g++.log.xz | Bin 2661300 -> 2676612 bytes sumfiles/g++.sum | 111 +- sumfiles/gcc.log.xz | Bin 2262648 -> 2246304 bytes sumfiles/gcc.sum | 2660 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892240 -> 898060 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213820 -> 214104 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428264 -> 436908 bytes sumfiles/libstdc++.sum | 23 +- 45 files changed, 1582 insertions(+), 1706 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions