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 91ae1aff2b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 87f019930d 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 867243cd6e 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards bb39024f17 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards f4c7ff78a5 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 0ff8719aa4 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 30d4ac2167 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards fbbc0a6821 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards d028e86a7c 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 0117adc802 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 2b199382f2 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 5ebbff206c 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 5e17df47c1 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 7fe543fba6 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards aea3a03f57 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards ea99400976 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 3f93c63fe9 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 3cc851fcae 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 8daec7b0a2 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards c9d1324c05 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards dd2b96de0f 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards e73b2a625c 301: onsuccess: #2118: 1: Success after linux: 16 commits discards fa857af6b3 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards b059b7ad84 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards c572ac7621 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 580c8928ac 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 25ae88673a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards cb4134a4e6 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 4085630428 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 5bd3196ece 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards acd32e7009 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 0cca1805ff 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 9902958155 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 89e09127cf 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards a01062e640 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 6da383801a 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards f5233b90c6 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards c7189de568 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 229770a27b 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 5efc50abca 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards feac8e74d2 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 52ade4d529 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards e0ab592cb7 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 3252c0f345 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 359b07eb97 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards ecd72c19dd 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 5791fb2c34 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 62e1ea7d83 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 61f460b5f1 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 91fbfeb183 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 2a3240d769 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 10087a04da 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards ae0ab75417 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 644170c3cd 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards e86096bb51 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 1d6c50c03d 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 2de17482a0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards bc27ba61b2 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 166445a5b6 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards ca5e87c9ba 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 880cfecdca 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards b6c5878863 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 93643c16b1 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 0400ccd8d0 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 5891b98ea6 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 0cd1eca85a 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 064094bebc 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards ff8528c365 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 402d1334a4 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 72cd56ca9b 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 7fbb4a87f4 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards bc4ec52a39 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 90d2a8545a 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 302b1ec0ff 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 8bcc9703b0 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards c48f36106f 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards ed5ed80f32 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 8b9ec5ff6f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards d3b2b1f450 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 0df9256ac1 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 589741dc86 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 253698a53e 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 852dd78160 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 3c6809e392 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 40f62942be 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards a1c54212ea 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 8341d66213 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards a39b49cd40 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards bd096c89cc 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards aafef42af4 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards d83b98d4df 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards c20466ceca 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards cf3d42b69f 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 4bc37c33a7 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards ac3373d4df 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 373260a0c6 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 73b89145e0 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards ca2ece49a0 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 4dcdb85808 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 5a842df413 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 695b586830 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new f7865defbd 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 61871bc5f7 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new e40c8dd8b9 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 4a04510654 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 30433c734d 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 876ce54680 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 829bf14865 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new fe9a7eb6ea 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new e269f52bf4 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 71dd5b6b12 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 571ed43036 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 655aeb29b2 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new ed57bb2520 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new f9d4503e3d 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new c6346a3ac0 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 06e8e4f34a 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 0a311f38c6 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new f49f7e9391 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new e04a1afecf 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new bda719edf6 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 10713a5167 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 95a3d8b394 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new aa7ab63d9b 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 11ced676ec 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new ce46e07027 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new f8dc255834 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 460bbe6d3a 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new a22a2cf2f4 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 29bbd8e8ef 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 0b5bc76e38 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 790e305839 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 36f3f7b87a 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 1544e1da49 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new e53858b8b0 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new a43a278148 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new e8fe47639e 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 9c8dcfe1cf 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 542fed25cf 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 447ce5d4d7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 2fec75e37a 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new b96f4512c3 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new e1a0ce34c6 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new c423c4ff20 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 8aeccea50c 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 724905fe13 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 2502bcc75d 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new fa62c0f4f2 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new f0aa7b2cc0 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new a8f752fa62 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 82137033a3 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 7e3d2f9d53 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 9844c95a03 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 9be700a3a8 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 8891b6ff71 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 839820672c 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new b400ac84c2 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new e336c5ad48 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 90a179602e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 742b5c7295 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 4ecdead448 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new af1183ef7c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new ceecaa8d1c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 20224215b5 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 1b17bdba4e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 82d09c7bcb 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 2177a6bd36 287: onsuccess: #2103: 1: Success after gcc: 9 commits new e1916590f5 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new c3af85fb59 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 1476dd54f3 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 9b5838f092 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 96edf213e4 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new edbfa3748a 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new fffc28258d 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 1141fbe40e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 8f285816f5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 12c414bbb7 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 0e6d7d20dc 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 126e212d80 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new fb7abceb4b 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new c4b798bb27 301: onsuccess: #2118: 1: Success after linux: 16 commits new 1808135c47 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 26d65230ce 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 9721e90cd7 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 715463d37a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new d629423b4e 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 8952f7473d 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 1e72a28235 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 5e1999fa44 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 5b8977bc23 310: onsuccess: #2129: 1: Success after binutils: 4 commits new d28424f691 311: onsuccess: #2130: 1: Success after gcc: 4 commits new ced2de7686 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8a0a0989d5 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 4419f6f849 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 37c4b6ca2b 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new b320bbf42c 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new ca2dbb19fe 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 754d97b73d 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new e487a490f4 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 47361d7cca 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new b17c324163 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 70dcbc4181 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 00a51b8d00 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...]
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 (91ae1aff2b) \ 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 1736 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31860 -> 31760 bytes 04-build_abe-stage1/console.log.xz | Bin 91748 -> 91592 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 236664 -> 236260 bytes 08-build_abe-stage2/console.log.xz | Bin 228204 -> 227792 bytes 09-build_abe-gdb/console.log.xz | Bin 39272 -> 39320 bytes 10-build_abe-qemu/console.log.xz | Bin 30652 -> 31132 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2480 -> 2664 bytes 13-check_regression/console.log.xz | Bin 6080 -> 5296 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 52 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 36 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 - sumfiles/g++.log.xz | Bin 2670184 -> 2689948 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2277900 -> 2245012 bytes sumfiles/gcc.sum | 2504 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892992 -> 905160 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213988 -> 214156 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436644 -> 434412 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 1376 insertions(+), 1508 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