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 8ad0d886af 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 94814ddc37 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards a95058ad65 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards df7c1f4ef4 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards cb2c89c180 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 9030b568c9 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 896e0e9806 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 4d97d3c366 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 1178934c04 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards ab59596297 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards a82ad6aef1 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards d04ec4a0a3 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 09dec48261 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 7133afa250 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards af6c68b4d2 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 7899e6d30a 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards fd7f89026c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 3a8ef6fb2b 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 151ddf6895 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards e530286237 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 2804536738 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 0c45c513c0 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 0bdb35e85f 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 278e209ce9 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 3643128fb8 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards ae1c5021be 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 93593eac67 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 185e13509b 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 4f275e855f 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 60b6422638 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 535db93f4b 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 6d8d56b54f 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 6b625f96c2 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 25bb97ffc2 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 804cb28004 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards f5306d75a7 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 05b1936327 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards db4f1fb9e3 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 2055011388 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 7d92fdd148 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 4b07a761ae 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 1d2d32f955 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards ac1f394486 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 473f1b2286 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 9afbfab4b5 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards c5b6cbc10b 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 6682a6305a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 76262ab3f1 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards e2f881b33b 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards c8215aa813 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards fbadd89aac 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 8e40a735a0 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 153d4fc40d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 5e1f690802 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards c418179055 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards b26e9cb019 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 1a7d54c7f9 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 9f9e0c46f1 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 68b9f2b83f 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards e3b53d5e58 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards d6d75ef033 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards c9842de56e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 151549750a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 6f9fb9ff99 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards e2f4965e7d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 45f9ebe3cd 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 2231baa3bf 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 7c95834cb8 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 23db66c7bd 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 3f58f1b517 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards c8aeee86c2 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 73595a9850 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 234ed5191d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 473e062948 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 135d44fdc6 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards a55253f92a 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 44763e529d 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 2172492269 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards ccb92d3a1c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 8a5b853dd5 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards e9e465c4d2 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 36e2a744a4 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 4d082bdb92 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 22dfced7e8 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 1b072142b8 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards f10f69dc6e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5223086ea6 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards a1e25963e1 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 563583a4e0 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards dc88c27dce 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 9750bcadf1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 4ffe13ef64 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards dfbc0414ae 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 64ef45a9b8 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards b2a62e0bd3 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards df706fae42 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 7868d64665 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cdf24946e6 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards a6de1b25e5 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards e337774987 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards a940669207 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 9477037b5e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new aa398f547a 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 30c566f47a 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 8655909fa4 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 446b92ba56 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d4dfd88f32 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 139e253da7 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new f8d7a27d68 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 45743fc075 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new ffb4592499 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 2b7fda3491 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 4d601875f0 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 0b1441dcbe 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 00293731bd 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 7c311b69b0 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 80be1d6918 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 98f13f55df 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f4297ab681 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new ef691fd153 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 9586fc9b96 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new c7b398c045 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 44a9d9dc2d 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 99479a272c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 4f306eceb4 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 379a20ba97 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 8c2729b5aa 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new ba12791d82 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 68435baa05 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new e9f0465f84 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 673974baa0 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 9c41ee914e 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new e578a9d7fa 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 781836c168 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 9c1e02f2c1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 5216d61645 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 1f359b001d 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 3101b39233 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new aca8895890 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 6ffdb24527 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new cf67850ff5 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 98486002db 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 625253c58b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 10ca2fde33 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 180e134a6f 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 54896c9cc4 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new e2f4191609 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new f6f1522894 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new c9e715e8b9 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 117aa01e13 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 324f91db30 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 2af0d86fe0 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 270e4cc4d4 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new fa933bc450 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e7c305bd09 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new f5521a20eb 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 247f7df857 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 9f066cd843 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new b9fc32a8cd 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 106d7349e9 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 457c482cec 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 22e58e109b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 09017c6abf 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 9e4cfc895f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new ab56472673 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 03dc08e944 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new d17c0d4ea3 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 0f598b1033 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 5d523058aa 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 5c01795b9b 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 42f9a79bd5 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 243b037d05 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new e05f42125d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 4445c7cd5e 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 31061bf342 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new c7565169f2 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new eb7bd4afbf 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 0d2432b1be 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 9128295305 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new d960c8ed42 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 322dd76f05 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new d48768e8a3 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 6e653d7f58 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 6533283adb 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new e1248d0f7b 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 2933f75077 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 92ceea43d1 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new b7103de881 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 5160820c7a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 1cdc666697 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new c07d9184f6 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new ac2bd9bd01 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 320c149db3 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new ed685f53ee 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 160dd554cc 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 9991ae45af 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 2ce7444312 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 9c380b2366 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new aeaa0494a0 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 9329d11cbc 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new e1825d97c6 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new a5559dbfe9 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 8f4733f768 422: onsuccess: #2246: 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 (8ad0d886af) \ 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 1736 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31256 -> 30864 bytes 04-build_abe-stage1/console.log.xz | Bin 89276 -> 88968 bytes 06-build_abe-linux/console.log.xz | Bin 9064 -> 8500 bytes 07-build_abe-glibc/console.log.xz | Bin 235500 -> 236016 bytes 08-build_abe-stage2/console.log.xz | Bin 225596 -> 225744 bytes 09-build_abe-gdb/console.log.xz | Bin 39244 -> 38520 bytes 10-build_abe-qemu/console.log.xz | Bin 31428 -> 31240 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3828 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3100 -> 2748 bytes 13-check_regression/console.log.xz | Bin 5964 -> 7024 bytes 13-check_regression/mail-body.txt | 26 ----------- 13-check_regression/results.compare | 16 +++---- 13-check_regression/results.compare2 | 83 ++++++++++++++++++++++++++-------- 14-update_baseline/console.log | 62 ++++++++++++------------- 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 | 28 +----------- mail/mail-subject.txt | 2 +- manifest.sh | 42 ++++++++--------- sumfiles/g++.log.xz | Bin 2646416 -> 2651492 bytes sumfiles/g++.sum | 32 ++++++++++--- sumfiles/gcc.log.xz | Bin 2225980 -> 2224628 bytes sumfiles/gcc.sum | 2 +- sumfiles/gfortran.log.xz | Bin 896184 -> 891740 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217160 -> 217000 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440368 -> 441640 bytes sumfiles/libstdc++.sum | 22 +++++---- 40 files changed, 175 insertions(+), 162 deletions(-)