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 3146450b6431 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] discards 56c0fe8bd9e1 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards bf129ae37c69 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards 12d513da9c1d 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards cd7cd416712b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards 3d3e598312b3 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 7433c6610080 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards f38fd0970a18 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 861cacdccb6f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards b4b75960a531 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards c615f2c397c3 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 535788e9d5b5 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 613450ab4243 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 0a9bb2faec4c 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 7d06a378f6bb 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 1a66e7ebb2fc 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 6ab1ef930e54 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards d24d463593aa 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 3dc8a461b74d 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 10f47fff2d55 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards cd33da2f8add 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 838a4133ac21 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards f30d4b9fe132 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards da7b43a10495 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 5c62ae000689 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 33f7ac9ba207 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 5a71fc9c7e31 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards fffd326994c8 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 83348d72b927 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards f32b5dd01c63 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 3ec5033ee66c 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 1d2f9926dc09 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 526484112acc 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards e8a0f0df7189 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 178173f20338 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 43133af570a4 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards f9cef64f4442 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 90a4e28a5a39 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 6e6b847c755f 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 3fdb84c767dc 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 9b91c9838ed8 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 663550804432 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards d6cb50bcffc6 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards d321b11441ae 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards c98992d7920f 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 406147b9b86e 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards cd7f88a97e2c 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards e4561eb122c8 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 5fdb1cd6734a 212: onsuccess: #2022: 1: Success after linux: 3 commits discards aaae9592a652 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 714a8bfa0641 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 5ebfa07684cb 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 8418f3b06747 208: onsuccess: #2012: 1: Success after linux: 12 commits discards f6865834fda3 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 918be15d06c7 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards cc13adb43ddc 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 9b3887f2e815 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards cb379073cce2 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards fcf3130c068e 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards 235357c8df95 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 97d4c342705a 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 7fa028d5135f 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 5e39c01b5bad 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 1adae27a4930 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 7d8c795f4e33 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards b9519588db13 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 2f44548d7cf3 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 7b63b0055e24 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards fad208035308 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 88a7938830cf 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards d77ea89c90d9 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 3cc9b1a5b5b0 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards c191a0a960e1 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards fd3e56ea7b18 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards a7598fe5edd9 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards a0b40388c70f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards e384ed5e948e 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 2c0d1a161167 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 5fdcfee4f3a2 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 2e2a5d33a626 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards ec43f53f6a9b 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 9213196d6672 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 947ce9a55b24 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards aa03f4ac9261 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 1d2b12af5bb2 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards e50ee3a154f4 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 3d50e5feb1b0 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards e0f6c14fedcf 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards d0d0d6cedeff 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 5df77aeab9d8 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 600216b82b4c 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 623778448723 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 49570f4b0eca 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards ef6061f4285a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards a5f5c7d30f54 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards ac6f1397c855 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 3d95e02efb84 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards ab2c4288dadd 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 2450d418af68 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards b81aedecd77b 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards 52e0444996ad 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new a7362c7a2ddb 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new f6fa2e2fb3a0 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new ec7dcaa2216e 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 4885f82f9f1a 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 5cc5967bd0ed 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 823f441995fa 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new b3384e43c2b5 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new 6b7a42ea6bd7 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 3d167143eb91 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new a387265b4188 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 041dc2cc5c67 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 708fc0e74193 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 6a9b0359a42c 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new d61ac0fe74f9 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new fa3411f15b04 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new ca3595e4139a 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new c60a83343933 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 46dc89d8e7fc 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 03b0bb30a53b 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 8a1143be3b4a 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new 2ae2c391b1e3 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new a2ad958c2fcf 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new f6d65d6e7e31 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new c760d3593a8f 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 0bc1ace7823f 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 62d91eae5df6 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 91402b182c40 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 129cbea481d3 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new e6c2ad83e01b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new b5dbdc705ccc 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new fc41c655ef6f 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 7a220411744f 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new c7c6dc6ebb13 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 618717e9bd8e 193: onsuccess: #1992: 1: Success after binutils: 151 commits new c35b70b4eeec 194: onsuccess: #1995: 1: Success after linux: 517 commits new b621456b2161 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 90400f0aca65 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 4b8fcd151fa0 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new a6f6f0dfcc8f 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new a870f9c010ee 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 3d4741fa84a0 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new e197a434d42f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 669e15b61ef4 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 17815a91cf7f 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 69ea1ec6affb 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 19f9ac962381 205: onsuccess: #2006: 1: Success after gcc: 3 commits new e29eaa683023 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 257cc1738602 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 4cc762d2ea9d 208: onsuccess: #2012: 1: Success after linux: 12 commits new a77f4b38e9cd 209: onsuccess: #2014: 1: Success after binutils: 12 commits new b15e87a84a5c 210: onsuccess: #2017: 1: Success after binutils: 6 commits new b848561a5248 211: onsuccess: #2020: 1: Success after binutils: 10 commits new a83b6954e04c 212: onsuccess: #2022: 1: Success after linux: 3 commits new 0ce3839e6374 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 2bbf289b2c65 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new e1b009d28297 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new e74d18688f5b 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new fce5dbaac1d2 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 354fe2836072 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 06030a68611a 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 318733b08bd0 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new ecc7f4288873 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 1bdd9b1a05e7 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 12325ae74877 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 1e5f5abc5f9d 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new a6e922237ec9 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 3b279a6cc531 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new c8c15f980d3b 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new d6014e6a1b37 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 8128e06fbea4 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new e8e8a6385bde 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 5ddb9defbc09 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 9e07131254d7 232: onsuccess: #2048: 1: Success after glibc: 2 commits new cf4d2d688a09 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 29db875d3252 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 19071ae2d1da 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 688fcc4114c7 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new fbffccf70524 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 805f7c8aef07 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 39dfeb956392 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new e60b617267cf 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new d5f9cf6662e1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new b71dd483e9bd 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 5e02df157dd4 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new e13563abd46e 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 6eda6ff11d8b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 5baecaaf1b49 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 67249ea8ce48 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 37cc4615b712 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 5c0abf44d0d9 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 51f9887b1d5d 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 6526909b14c8 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 4747a06490b7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new ce4a7844483f 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new da6481e14865 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new d9b20a98b3c5 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new 7824cc0f05af 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new 5dd836af8f96 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new 8eb69c506f63 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new 7cb14634c3ff 259: onsuccess: #2075: 1: Success after glibc: 2 commits new ddf26ab6b79f 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] new 380b07f17e30 261: onsuccess: #2077: 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 (3146450b6431) \ 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 1780 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 32036 -> 32200 bytes 04-build_abe-stage1/console.log.xz | Bin 91496 -> 92332 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8632 -> 9260 bytes 07-build_abe-glibc/console.log.xz | Bin 235064 -> 238992 bytes 08-build_abe-stage2/console.log.xz | Bin 223876 -> 225352 bytes 09-build_abe-gdb/console.log.xz | Bin 39144 -> 39420 bytes 10-build_abe-qemu/console.log.xz | Bin 31676 -> 31284 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3936 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2780 -> 2692 bytes 13-check_regression/console.log.xz | Bin 6860 -> 7576 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 10 + 13-check_regression/mail-body.txt | 30 + 13-check_regression/results.compare | 44 +- 13-check_regression/results.compare2 | 56 +- 13-check_regression/results.regressions | 30 + 14-update_baseline/console.log | 70 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 32 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- results | 30 + sumfiles/g++.log.xz | Bin 2685532 -> 2671360 bytes sumfiles/g++.sum | 132 +- sumfiles/gcc.log.xz | Bin 2245748 -> 2278348 bytes sumfiles/gcc.sum | 2839 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 891304 -> 901248 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214040 -> 214148 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 430424 -> 441480 bytes sumfiles/libstdc++.sum | 10 +- 46 files changed, 1782 insertions(+), 1632 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions