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 030fa5da86 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards fa4e534be0 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards dabcc1324f 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards d2c17b665e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards c39e896297 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 9e4f2f5476 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 71b04ca90c 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 312b43480c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 9b51c1cf7a 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards fe8c9c29ea 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 60b13d6d3f 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 51ad2e0f80 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 489fda3bfc 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards c49bd644a8 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards c9aa3d6402 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 6d2141e2fd 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards d7f7e8a781 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards fb74962b64 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards d116d702b8 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 7bd6326a8f 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 89e26fb08c 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 86f1c55168 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards a395938b89 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 91448c9a3b 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 45f4068a3c 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 5e59d37cb1 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e6ccdbea91 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards caad44631a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 22eda6175e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 9e41d486c8 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 6ecf3962df 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards dea9e9d38b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards ee37bd3427 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 6855c2b1c8 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards f342f1c6b5 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards e4264eaacb 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards c7ebadd6bd 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 5ae64d721e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards c7a928b329 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 4f976a8dbb 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards fe482b4bb1 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards f6473155b7 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 707eb03c94 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards f8a3492602 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards b578387d6c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards d5094cf559 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards df17ce66ad 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards b45f1d2965 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards c27e5d978e 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 70a409d286 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards ef80e4ac9c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 5f19698b37 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 036864b453 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 22b0690750 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 3c89e2f1a1 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards ab1f7baeaa 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards a4400e4c7a 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards e58b925bc2 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 57ee8eeada 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 6a478892ac 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 1c52732976 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 1de1896869 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards dede05f3eb 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a19e9cb390 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 456c9dae86 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 68b17709d6 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 5db7fb9cf3 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards da6b9b5e9b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1a286398af 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards eec296dc1e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards fb9a3b9286 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards da39d1e6e7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards d37c8f4a91 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 2a17bfb74a 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 64e615669c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards adfac042c5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards f2cf771547 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 988317adcc 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 390c1c92d5 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards ba1236d5bd 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 7bd3ae4357 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 1f80fe9d5c 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 65036bf302 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 54dd7f65f8 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 10330302fc 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 6a6a018c16 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 12d6dc4fa3 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 09be2e3a07 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 94120d32d8 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 24ff816ef8 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 6acfe58367 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 69b587c424 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 480fef0e93 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 06ef77ff63 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 38efe3ab7c 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c97ebf29b5 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards f954da3388 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 2fde9ca4f0 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 3472377c27 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 0de8e6cd56 301: onsuccess: #2118: 1: Success after linux: 16 commits discards e7028cee05 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 1822c3c048 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 883dbeeffb 301: onsuccess: #2118: 1: Success after linux: 16 commits new 1f9fa48c46 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new b99bfb77c0 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 6d9571027c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 3b99ad3f29 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 5e913be280 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new e478b3e9e8 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 45b0ffc5b5 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 43fbfbeb20 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 82e6cd1660 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 4ab63c3883 311: onsuccess: #2130: 1: Success after gcc: 4 commits new a3ef1c33c8 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 4f49043abd 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new e49a95df5f 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 7a502cfd5d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new c0a0ca2c10 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new fa0bf5ce39 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 7fdafefdb8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6384730c85 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new ba054116a5 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 548fbd8e7e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 4fcd049065 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new b9ae571470 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 4ba5bacc9c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 556eebe40b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new b6fc63f452 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 86baaa0fbc 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 9ac8986940 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 490e340270 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new ecc9ec7041 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 82af91c9fa 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 9eaca46cd6 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 1b3d258880 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 94ada4ee3f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new e77183d773 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new c127bfcd7f 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e4eae75d0f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 03a6a42ab1 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 6c2a50619d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 89bf080abc 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 38216abecf 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new c9f0941737 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 3a3de64bf5 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 905f794c7c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new e875973e91 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 543f253a80 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 4dd5277e5b 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new c5565a64f9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 10a10f04dc 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 4c65ff4d3d 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 05f346151a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new b2b3cdf853 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 8a67a7d2bf 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new ac8b8741a3 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 5f4493111f 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new b4e86010db 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 1cfc6770d3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 471a46cf6f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 0e0cb01d49 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new c950f9a14a 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 93cfac5e8d 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 2448e39848 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new f37c2f63de 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new b5036c4368 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 3c46bb665f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new bd1d573fb6 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new d5e2397407 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 603f2f2ce5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 877c197a66 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 7c87c86442 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 334d5ea8ac 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 7556a39bc2 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 80947b1f93 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e6615d460d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 8f8ccc3ea2 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new c8e19fa665 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new b984179c27 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 75e42f1a19 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new b45b181a22 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 058b4d7e92 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 33e6e61055 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 02f82bbf15 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 0f06c36570 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 6ba8cf8d74 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 69a8e3a0c7 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new fb6e9b1ed4 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new b3e88f0c73 387: onsuccess: #2208: 1: Success after gcc: 2 commits new b2ba1032cf 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new bde1dd38d1 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e75d6b04e9 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 63ed5dd5c9 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 362b531089 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 4d1f24dff6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 1b74efcc73 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 7740306d8d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 847218eb42 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 5be34860ae 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 07d3cc149d 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 10b45ba136 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 6db31ac8cb 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new f9d08db32f 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...]
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 (030fa5da86) \ 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 1784 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31300 -> 31748 bytes 04-build_abe-stage1/console.log.xz | Bin 91264 -> 91584 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8700 bytes 07-build_abe-glibc/console.log.xz | Bin 236544 -> 237012 bytes 08-build_abe-stage2/console.log.xz | Bin 228376 -> 228148 bytes 09-build_abe-gdb/console.log.xz | Bin 38612 -> 38936 bytes 10-build_abe-qemu/console.log.xz | Bin 31776 -> 31720 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2628 -> 2700 bytes 13-check_regression/console.log.xz | Bin 6584 -> 6004 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 40 + 13-check_regression/results.compare | 14 + 13-check_regression/results.compare2 | 33 +- 13-check_regression/results.regressions | 14 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 14 + sumfiles/g++.log.xz | Bin 2636260 -> 2674916 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2184044 -> 2212024 bytes sumfiles/gcc.sum | 1894 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 886396 -> 893512 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216976 -> 216904 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435244 -> 444656 bytes sumfiles/libstdc++.sum | 35 +- 41 files changed, 1166 insertions(+), 1058 deletions(-)