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 893faf52f5 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 7e7e9623c5 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards a0957cd0f7 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards cf642a6b51 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards c79be3063b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 69c99707c7 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 866e531469 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards dfbc50a407 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards ec73b950c5 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards fc30234be5 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards c42179ae27 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 1aa4cfa9c5 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards bbd18ea0a1 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 798448798f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 97d48f6c36 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 9bf6a96546 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards fd58d37824 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards af3b2dc991 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 92833f0e74 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 99c063d0d1 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 5b4c4f4308 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards f7c2b38037 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 94842d483a 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards f4ba078e48 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 367990c81e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards c7f8db1553 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards b63aed7494 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 95080b7445 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 7f1588bd34 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 8b26dfd980 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 0feacf361f 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards b5d565b204 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 414e5c3952 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards ae4d674a2a 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 2247701797 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 65a126644b 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards e1a7449fe0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 7e9fcc8833 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 37770bdd68 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards c0d42b85dc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 5f642dde2f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 5021b6f4c7 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 5c76793ffd 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 5f0f4d4399 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 309e23fdb3 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 878511a327 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards a74068a87a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 2c179f69ed 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards d3766ec202 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards ddf588b514 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 828a734e0c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards d79ed03ec9 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards f1439babed 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 36f86b9bb0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 951d14661d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 2ea59f84cc 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 3a556cc924 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1be303d636 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 7ee0b8c34a 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 3def0c1673 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards bd41bb309c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards e59ff2a9af 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 2352f426d3 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 96ff2fc922 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 1decbf53f8 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cfd6257bb0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 039e00047c 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 8169d75682 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 68cd2b4ae7 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards d56b44a6bd 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards a7b890c3b6 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 266f648350 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 53fa33e977 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards bd3ecf09df 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards f26c6622c2 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 0cc0d2ac30 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 660f7f5583 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 0391407153 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 10659dbc57 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards a904fdf953 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards f7d13f520c 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 1459c9d44c 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 8a02e8df40 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 6967774005 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 3a6b9b2e6c 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 784bbf1b0e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards a09ddc76ad 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 399c868675 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards a56d1d15e4 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 8e746b38d8 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 3dbf94f15e 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 896dbccf1b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 323de1cbd4 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards e0de2ad89c 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 86715c09a6 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 553e8fc57e 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 43d79e17b8 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 9ee0b8bbe0 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards b7b8dc2f96 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards f3199990a7 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 5dc5590134 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 02e9ae5933 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 2c273ca4ed 290: onsuccess: #2106: 1: Success after gcc: 2 commits new b178c5f1a0 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new e9fb507459 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new c3f15a92bb 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 6395f9c46b 294: onsuccess: #2110: 1: Success after gcc: 17 commits new df07cbb254 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 4e737cd98a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 65164c6525 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 5b1a825b41 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new b38a1fa887 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 05dcdff3d1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new d5314c6243 301: onsuccess: #2118: 1: Success after linux: 16 commits new 3558337646 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 933d8ae6cb 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 906d409373 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new a1a2339aeb 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new f4ad5a83e0 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 21f2d17c73 307: onsuccess: #2124: 1: Success after gcc: 2 commits new fac7ccc4e0 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new d723801a1f 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new fa4a21194d 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 92aaf19841 311: onsuccess: #2130: 1: Success after gcc: 4 commits new c5fb19e521 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new fc835152e1 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a1fdd3de07 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 9e8658bb7a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new b63cc6c574 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new f1319eda2c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 3f1976570b 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new b7cd0b630e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 9dd89e3872 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new ec52fd8c39 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new f7ba2af839 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 3859cc56ce 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new b816690c7a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 934316f585 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 185080b540 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 1b61871c2d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new d76dafecfb 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new a5c6981973 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 4601c1c947 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 0ad24e3722 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 3dc76a8235 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new f67d3c195d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new fdcaa1335e 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 2865f3b67a 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 17d762e1f1 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new d4533113c1 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new c8240a3feb 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 6f76e800ff 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 5475a56389 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new af444c4b36 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 937a456fde 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new c324147969 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 872de83128 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 354757efd2 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 29c2f5016f 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 02434267e4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new e916d6fc8b 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new f4fb619911 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 4ae6c9dfb1 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 765089562a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new e1f5f4bdae 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3c10f0c731 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 0f542687fa 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 2b7a2c3a87 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 9b5f273c4c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 0bc6bfa868 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 42d4f26873 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 33c72fe186 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new e42fea4d32 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 23b7bbf7ea 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 5f23e3d4e4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 099cf77e40 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new e57b7a8d3c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 6664641709 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 5d16823ccb 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 96c774a1c7 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new bdee9718cd 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new c87ccee328 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new b447940352 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new bb1427bc2a 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 7ccfa1a7fb 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 1916f8ff38 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new df0164933c 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new ab317131f5 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 03afff2f2a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 6d74511dd9 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 5a347838b0 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 33c1f96b25 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 6a9e44e1a7 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 635e6892ae 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 39d426f85b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new f165f30fa3 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new c721a4f98b 384: onsuccess: #2205: 1: Success after gcc: 2 commits new df4ffa4c63 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 9aa4826010 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 5ffec53997 387: onsuccess: #2208: 1: Success after gcc: 2 commits new bada1aed8a 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 18e479e57d 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new ce0570c277 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...]

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 (893faf52f5) \ 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 1812 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32560 -> 30952 bytes 04-build_abe-stage1/console.log.xz | Bin 92952 -> 91040 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 237400 -> 236580 bytes 08-build_abe-stage2/console.log.xz | Bin 230544 -> 228480 bytes 09-build_abe-gdb/console.log.xz | Bin 39660 -> 38308 bytes 10-build_abe-qemu/console.log.xz | Bin 32820 -> 32504 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3368 -> 2624 bytes 13-check_regression/console.log.xz | Bin 7168 -> 5720 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 37 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 2649380 -> 2635596 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2237304 -> 2215612 bytes sumfiles/gcc.sum | 2422 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 896584 -> 890736 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214624 -> 214512 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439956 -> 438808 bytes sumfiles/libstdc++.sum | 20 +- 43 files changed, 1354 insertions(+), 1443 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