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 9ffae6ef7a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 5955e40629 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards e5313653bc 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 0ab635350d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 3c18d14d54 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 6f38262115 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards d18be013b5 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 8eedcb7b4a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards eb30ee5371 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards dabf98eebd 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 45728d1657 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 8e4539772a 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 6a63eced2c 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 4bbed26d81 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 5e84a3f12f 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 63c1abdd5b 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 7af0a0c916 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 9e6f72826d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards e9c48877ad 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 961ca1f8bb 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 357a696d73 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 81f1b8762b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 26f843c42f 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 05ad64d785 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 40c7b0097f 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 87c0fa8848 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 41c3a0d8b9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards fcf14fa59c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards ab6993079e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 52d949f1f6 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 73370bdde0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 7ff8dee039 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 8ea41eb7dc 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 63167d18ed 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards aa68006432 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 7f00efcd42 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards d50045b383 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 484044be39 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 452c4bedd4 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards d29ce4831c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 3d75f8f2f3 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 995b0784f8 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 59cb80676d 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 63bd8aeadb 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 13ad65a6bb 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 20b744e83f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a9b14cca65 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards ebe0515c86 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 331d1ff0c2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards ebd35086eb 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 4b85fbe7e4 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 254548b262 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 46d6cf77fe 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards da408541fc 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 5ffd4ad7dd 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards a23c4626a5 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 28663d243a 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards fa40cdbbe6 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards e356818cf0 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 23836d80fc 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 764d836122 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards f6e83f7425 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards b42f069df6 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 0c1158e3fb 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards cc4e611a1e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 5dd1ce55aa 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 2a68e1164a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards b61659ea68 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards f13da0bef1 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards a774fa0a1b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 2a1f5beb5a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 8de17d8286 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 57b6f77663 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 6db3b56b16 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards cd77a3dd81 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 2b98f4f64d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 9dc3b04625 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards c3db7dbfa6 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 2812c159b1 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards ebfff66aa4 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 10b813ba9e 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards b44c20fd68 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 8691656182 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 0d86d73a93 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 0958319a52 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards d9c83a9c70 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 9cc350bace 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards b1498f7966 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards c3f5a52e78 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards b65c378448 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 46d53dec66 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 5bb40a8c8a 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards db4b68b55f 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards c457627a2c 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 9341d44105 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 9087d5541c 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards bdcfe4c698 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards a04ed0f392 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 9bae38121c 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 6c0f18319b 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards f57f68a532 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new c50c652274 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 1eb0bbbe61 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new e3f106f1eb 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 912b43f4e8 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 6587830124 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 0411241b2c 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 3639023ef3 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new fb426c5271 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 897d36b909 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 875f9bfffc 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 37d7e1cb8a 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 8d12691a1a 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 62689e0d17 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new e89b4dc58e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new c9084a4821 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 663556afd9 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new f54c10f4ea 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new a2fb925b6c 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new acf937629c 301: onsuccess: #2118: 1: Success after linux: 16 commits new 6f195aa713 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 86fa7ada50 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new d54d49f07d 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 15b63f170c 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 03019fa6fa 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 03e3a440be 307: onsuccess: #2124: 1: Success after gcc: 2 commits new f1887431ba 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new e8b3b71c38 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new c0245c3271 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 0afd6512de 311: onsuccess: #2130: 1: Success after gcc: 4 commits new dd27a09f22 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 1088f0e449 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 8e2b01b8a7 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new c7c43c6a0a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 7ca193a2c4 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 939c7107b0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 9c820d9a86 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 487e3e7cb3 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new dd2e747123 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 1b2e953c79 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new daad9be35e 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 7cfe6ee3f0 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 8622b03be3 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new e253f88367 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 8fb368eb68 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 19e0a15a03 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 2976afc8ef 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 31bc439bf1 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 6d026cf08f 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new e6ac1fed1f 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new d8f4d5dfa7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 093d078679 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new b04780f961 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new f36255d2d4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 12cae726d4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 846f216f31 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new c4c7c9fd9b 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new a12b9ba3ee 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 0315e854e2 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new b6242e2082 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 3cf3db12ac 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 79be6f360a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 69364f8d77 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 1069e85975 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 1bd690006b 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 255f6c0013 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new dbac275ab7 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new ac1252f58e 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 5cbd576171 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new befb52311a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new b215f6bd4f 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 83eaf59629 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new b48197e986 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 3c4221c5bd 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 3d5392268d 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 54a42e3c0c 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 31d38d6d57 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 1bd254074c 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new bd8419e81e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 79aede5ced 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 7f4b4c53e9 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 03c0da3527 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 66cb6acade 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 3fb0e20a2d 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 2dffebb248 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new b49019a1b8 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 87723c1428 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new a3f97b85b8 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 7f55aaed70 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new be48d0ce30 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new d914567dee 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 9f57f574ca 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new cec445fffd 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 1c33d08aab 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 15e3f94044 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new b99f472648 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new d7f2c2fdc5 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 111b65dbab 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 712c184481 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 80a6c2084d 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new af4649a7ec 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 3a3a5f7b53 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 66d0d55d78 384: onsuccess: #2205: 1: Success after gcc: 2 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 (9ffae6ef7a) \ 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 1788 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31020 -> 31044 bytes 04-build_abe-stage1/console.log.xz | Bin 91756 -> 91760 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 236748 -> 236592 bytes 08-build_abe-stage2/console.log.xz | Bin 228180 -> 228256 bytes 09-build_abe-gdb/console.log.xz | Bin 38164 -> 38304 bytes 10-build_abe-qemu/console.log.xz | Bin 31976 -> 32120 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2968 bytes 13-check_regression/console.log.xz | Bin 6184 -> 5768 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 48 +- 13-check_regression/results.compare | 15 +- 13-check_regression/results.compare2 | 69 +- .../{mail-body.txt => results.regressions} | 49 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 50 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 + sumfiles/g++.log.xz | Bin 2632892 -> 2637628 bytes sumfiles/g++.sum | 33 +- sumfiles/gcc.log.xz | Bin 2201944 -> 2211280 bytes sumfiles/gcc.sum | 2221 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 895796 -> 891932 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214480 -> 214556 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435872 -> 435976 bytes sumfiles/libstdc++.sum | 29 +- 40 files changed, 1320 insertions(+), 1309 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy 13-check_regression/{mail-body.txt => results.regressions} (65%)