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 b38cd900c1 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 4953706ba1 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 6cb24004e6 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 70e3f2d5d0 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards b682391f6c 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 2768e1964c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 762c9953e7 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 06ed717f3a 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards d6efe7b817 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 38e6a924e3 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards a4e0a9a8f4 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards fd3a548c4c 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards ea75c8757a 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards db76e88697 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 3069ae22a8 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards ffa9fdf20a 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 34d3d3ca9b 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards f8b2275618 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 1c456d37ff 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 95c431991c 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 48e03fef17 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 2ced01e739 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 85d2e1de60 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 8fee9a8aff 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 9e737c55d1 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards b2a642647e 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 581733dcae 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards c91d245792 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards d6625f7caa 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards f614cac966 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards a4413ef885 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 208c581217 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 9ec544647b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards c78a4202ec 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 6c3c00a9e1 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 8886cc6e80 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 8f8e7cb634 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 4dffba4ff1 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards d870ff4f19 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 559ab16e67 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 70ed6df42d 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 4c379b1d0a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 0a8325f9ca 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 374ac8e177 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards ad1797eb55 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 7423e99178 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 310b72bcea 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards ab5a9c632e 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 3b0b52b9ff 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards c2f489b09d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards daeb890aa3 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards fd2d92cf25 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 4d56219d64 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 7206f2c743 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2f3af50b5e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 66ffd8fff2 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards cad9e7ef11 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 294fdab160 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 95efaf990c 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards f29e40c6cb 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 2eaaabe34d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 28c0ebff31 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 2b4f2527e4 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 46a3f5dcf2 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 7c274e877c 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 7dda12e759 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards bd95de5c66 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 672019d509 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 436ce91ff0 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 28a2073b94 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 24c4218345 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0fd57fcd4d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 643f33ce35 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards ada56dbba2 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 4d3b3611a8 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards a2a1547882 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 5c14ce10f4 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards abca6117ab 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 12f4d07c1d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 04845a9b00 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards e461a6fd7e 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 3081f76b0f 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards bfe88d6b43 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards f52888808b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards f63ce5325d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 43eb55a786 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 239738bf5d 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards a2591c2de2 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 3b7c369e98 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 47d4a873c2 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 2b066d4e03 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards ece643567a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 358a42cb82 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8398a56381 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 33e1e439eb 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 57d2585a18 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 6b3fadbe02 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards c7a58edcf0 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards ec8b6e9a39 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards e7511841d7 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards e8c0449d89 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 57a87cc80f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new ea1404c521 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 364b047d38 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 2c48f3ab37 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 699edd5ecd 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 60ca485452 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 2883728061 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 438c4d0a06 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new b94152a645 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 653321eb32 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 7b2f84f495 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new e9e19e03ec 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 43a0a56f49 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 95f74b33e6 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new fed2c5951f 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new c339429b20 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 4875dd39c3 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 15e18fbacf 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 84d115d94d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 5dadeaf4b0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a00d7b37d4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 03068d827f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 3db76ddf71 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 40a2400cb6 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new b01e77a4bb 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new dc03f8cc8a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new cbc2206f4f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new e2961bb399 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new bd2c7b5902 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new e92a3aa2da 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new fec1a4293a 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 98aa41c4c6 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 42207d26d9 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new e63e92f7cc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new d910cf8d84 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 98dc1cb1bd 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 4758f700b1 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 46a1fb973b 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 90f93b0fd8 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 7765c8a085 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 153d049f64 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 4451f22a03 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 40e41292dc 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 45c9c5b0e6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new a6478b6dfa 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new c76a9efc94 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new ad2ff64883 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new d5252ae098 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 1347cfd6b5 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new bd7c468915 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 42f74fdb65 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 3a048e8abb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 365b0bb60c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 5d367f2e6b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 2222610dbc 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 8f1c7d85fe 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 6c935e3d59 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 8be1a1410d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 20e81f4b43 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 10d066c25e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 1fe5a5d902 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new ff6709633c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new a24f0268e9 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 61b1dad153 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 12926d93da 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 5ce3cc8a75 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new b78ee4a22a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new f43b5e0614 384: onsuccess: #2205: 1: Success after gcc: 2 commits new db7a3f1210 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 8a9866c86b 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 5c521c4c64 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 938449341b 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new d7cabcf3be 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 436eca2a8e 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 9268bec60d 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new d2d8280934 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new a91dbddbb6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 608c880703 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new f61b4915b0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 0329798736 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 2f8ff60d36 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 90f64881cb 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new ae92d746be 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 8354945187 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 102685aa3d 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 8c19aecb5f 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new f444f8e115 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 19c35eb713 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 421c10ef28 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 4ba2134d65 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new efdedb6b3a 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 11ec42187c 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new a45a6527e2 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 833b590a0c 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 895bf61fa3 411: onsuccess: #2232: 1: Success after gcc: 3 commits new c8e975843c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new ee79018f54 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 14d00bebf0 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 6831eca453 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 383de783b8 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new d434881d5a 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new d7a5aab069 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 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 (b38cd900c1) \ 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 1816 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31020 -> 30956 bytes 04-build_abe-stage1/console.log.xz | Bin 92040 -> 92748 bytes 06-build_abe-linux/console.log.xz | Bin 8516 -> 8552 bytes 07-build_abe-glibc/console.log.xz | Bin 236656 -> 236416 bytes 08-build_abe-stage2/console.log.xz | Bin 228260 -> 228884 bytes 09-build_abe-gdb/console.log.xz | Bin 38608 -> 38448 bytes 10-build_abe-qemu/console.log.xz | Bin 32548 -> 32028 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2872 -> 3560 bytes 13-check_regression/console.log.xz | Bin 6876 -> 5568 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 18 +- 13-check_regression/results.compare2 | 51 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2637492 -> 2633104 bytes sumfiles/g++.sum | 14 +- sumfiles/gcc.log.xz | Bin 2193160 -> 2188636 bytes sumfiles/gcc.sum | 2274 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 889312 -> 891304 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216948 -> 217032 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437868 -> 437016 bytes sumfiles/libstdc++.sum | 33 +- 38 files changed, 1239 insertions(+), 1327 deletions(-)