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 ca36886d84 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 3858b0ab63 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 81ce79c054 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 4084a4b8b5 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 3192377497 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards f225445b6f 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 199859fc21 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 4b4a29f708 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 8e833cc976 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards d055369ee8 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 710c94f519 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 1e24b699eb 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 1e665acee8 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards f39c3238b8 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 4aeeaf9d5d 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 906c534f92 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards a80c0f303f 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards af1087cc0b 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 8870eb1100 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 89edd7e665 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 9295205bb1 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 096be92b48 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards fe2ef245ac 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 1cd923df48 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards be67cf8d8c 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 4cafef3cfa 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards f782fc078a 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards e4a551a457 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 4d82dce842 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 2de79bc300 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 6f882fb951 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 71d27f7475 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards acfe8a619f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards cccfee0ff3 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards ec5e9b96dd 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 597bf10627 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 06c0b3c5d0 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards de0da5fa36 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 6d023a0fd7 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 7e7f7a515b 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 9301d8df77 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 7438614779 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards d2766f8c65 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 4b82511133 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 9016e4b5d0 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 729bf50095 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 7d7cb4a3d2 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards c7c94ee6af 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards e1898d87fd 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 890ef6d285 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards c5e6a27034 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards f7a0de936b 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards cc28fb9cca 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards e527db9310 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 8bdbf921c4 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards a92af0babd 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 2e98de4482 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 7e5a1d967a 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 4e163cadbd 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 72b5b74d1d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards bc6d28bd44 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 9ca2435bd9 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards f6d95ef2e7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 51031aee17 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 0b43daf649 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 138ab19bec 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards ca0c275bfd 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 3a785f69ed 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 1d5aba030d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards a6905bc5df 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards eddcf7c93a 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards bd0700029d 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 310da26839 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 2c8f6a1183 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 5c87ecbf91 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 9bb222045e 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 667bfc232e 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 27284c465a 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards e986a7e4fe 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 15c98beec4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards aeddd858d8 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 38da302376 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards bde0293683 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards dc7d54f7c2 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards f69c770382 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 3106f70169 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards e27bd0074f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 3f2cf4a583 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 47aa5f9976 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 8815287ec8 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 4761796cf0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards f3a38152b2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards a8d434b994 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 661f57f352 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards a17cd100d7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 3be3db99f9 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f841ce8c1a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 5e64353637 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 1220891fab 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 82bcc05dfd 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 2c7c1916ae 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new ac0d1f7fb3 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 4232eba27f 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 3418d9655c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 9478e9e440 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new fd348e88e5 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 8b68acb420 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 51806a06ff 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new ab60f959e9 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 6ea30ee067 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new aab67a70ef 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 5e0ea3e833 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5553a73710 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 5b12cf99f6 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 4f44842512 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new a609ff637e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 9b20a01fbf 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new b147861759 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 5c7e84d1c6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3c8f61725f 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 962022df09 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 1c1e18b8c1 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new bfa57252da 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 15e7523b06 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 9289d77205 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 9034b80852 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 5b8996a6e0 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 72c0062f93 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new af9f8c5050 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new d6dc2155cc 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 0690aec9fd 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new f413adf802 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 389d30bdd9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new bfd03db8e2 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 97ccc2b46e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new d758d6fcfb 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new cc8df7897e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 54ed244aab 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 2cb1c56b3b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new c83369e737 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 34847a7460 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 87fa8ebfe9 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 3c404f5bdf 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new f7eb2e492b 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 32a3fc3036 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 2e827b0f49 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new c87d5dbc94 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new e483d6c700 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 8ba0df1370 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 932a4b25d2 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new a148fee59c 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new cf7d83cef1 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 8ca7fe31cb 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new d2bcbc9e64 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 1a51dd44d5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new c215786a79 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new b0dd8a5a05 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 610667e4cb 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 75218691ac 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new ea884d4687 384: onsuccess: #2205: 1: Success after gcc: 2 commits new d7111f3da4 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new a97a3bbba5 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 5eaa13f25f 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 4f28059d78 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new e6649edbef 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 5dc3c9097e 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 1e03c005a3 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 1462017b1c 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 5ce086d5d6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 07c66844fb 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new b83b1815ab 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 33591268f7 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 2e292fcbc3 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 339ceafe74 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 2fad72807e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 9d997f617a 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 42826521a2 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 65f73d3184 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 4395a91675 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 674a211f33 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 227198fda1 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 355ad79297 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new db0d74e36e 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 4bb25cdc8b 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new e69e2052c7 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new d86bef0fb5 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 091823fe4c 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 2f54888e80 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 2f4a54d3e5 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 1e6397cfe2 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new f11d292374 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new d3ad529295 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 648699fa2f 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new a521170cc4 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new fee23fe151 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 9580b81949 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 227aa04eb9 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 68cbf638c3 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 240e3b7c82 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new a2bf8cc8cd 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 96c70e9df3 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new f537c2af48 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 3fdda773d3 427: onsuccess: #2251: 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 (ca36886d84) \ 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 1752 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30696 -> 30716 bytes 04-build_abe-stage1/console.log.xz | Bin 88484 -> 88560 bytes 06-build_abe-linux/console.log.xz | Bin 8676 -> 8344 bytes 07-build_abe-glibc/console.log.xz | Bin 235496 -> 236132 bytes 08-build_abe-stage2/console.log.xz | Bin 225368 -> 225080 bytes 09-build_abe-gdb/console.log.xz | Bin 38424 -> 38524 bytes 10-build_abe-qemu/console.log.xz | Bin 31380 -> 31532 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3816 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2584 bytes 13-check_regression/console.log.xz | Bin 5716 -> 6320 bytes 13-check_regression/results.compare | 16 ++++----- 13-check_regression/results.compare2 | 33 ++++++++--------- 14-update_baseline/console.log | 66 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +++++++++++----------- sumfiles/g++.log.xz | Bin 2673144 -> 2653540 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2197560 -> 2220584 bytes sumfiles/gcc.sum | 2 +- sumfiles/gfortran.log.xz | Bin 892940 -> 895152 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216920 -> 217024 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440472 -> 444092 bytes sumfiles/libstdc++.sum | 22 +++++++----- 39 files changed, 107 insertions(+), 102 deletions(-)