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 c218800cad 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards b44aaf960a 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards ff88fe2982 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 93ab5d89a8 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards f4cf2d9165 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 74f83678c8 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards b6841b162b 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 3c6552954c 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 70295e0f77 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards b7833975fc 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards c846f80c94 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 8e9c6e038c 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 8ada07e285 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 7e39731737 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards de33bd1585 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 46fce7aa2d 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 3d893b1a9e 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 39098f4c0e 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards dcb2b703e9 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 7ff8d950d2 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards bd773bab36 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards dfaf9cd83f 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards d01937e838 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards b3e3bfa14d 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 2af7029616 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards c4c60cec8e 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 8feced2d76 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 3aba7e2ea5 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards c73e3b8e42 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 525e4bbc8b 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 0d278eb4b1 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 5b72472426 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 2325b645d3 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 0d24e6a12e 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 00b67238ce 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 08fcfbd5e5 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards a7ac1ceea3 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 4aa173cb6f 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards b7aa8cf5ee 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 6329e530ee 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards e5ab095f26 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards e09223c559 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards fef3da6d81 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 73f19a68a3 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 70a2f58202 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards b3cf8de319 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards ef47ecb683 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 0f41b58030 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 5bb8a8dda8 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards c9de631357 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 7fa5700034 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards e92b382ffc 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards dc9c596464 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 06433bc8d4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards ba91d8233f 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 847d22cf7f 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 9ddcf44242 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards f455661c8c 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 5d7fd275d2 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards e6ac248024 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 6282e13376 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards d644ecac81 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards e7b4a3d27b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 615557457c 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 51d158a6ea 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards f0a37f8116 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards aea7fc1869 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards ce60b63aa8 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 84722dd5e0 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 2f2c868e1b 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 1b33a49f4d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 852e7ebf16 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 69b41e7e72 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 7b5c9ca3cf 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 4d26c95c16 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 06451b26b6 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 10792ac471 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 90b110bd72 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 0722485316 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 04535b9ba7 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 5729ec0eed 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards ee21358808 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 330253eb4c 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 2b38d09df5 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 1af3e7233c 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards b649f03d61 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 0f7cc300e0 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 01a5016557 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 61905423dd 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 1fdb0a7e50 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards f8da88b374 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 0279ed05cf 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards b429f02744 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d5ca849c9f 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 0862b9cc09 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 4a6cd4f844 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards ac11ec14dd 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards bfb0a43101 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards c5d99b45b1 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 8d0768132e 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 1ebfd3200b 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new b30822c2a0 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 78422885d5 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0daf192ebf 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 36795c4340 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new b8f8d66765 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new e1543d1bb2 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 27596e0449 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 3a586d7810 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new e099e98279 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5bf65139da 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new d7e786f871 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 63c4040a8e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 375fe44b6f 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new f959016128 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 311273df3d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 72eb440e3e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new b75733dc8d 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 429031aff0 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 4b53a6920d 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new c32a6fffe3 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new a599829817 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 7f980ade7f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new c55700adfd 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 46fe0f856c 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new c6f5bd49e1 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new b93683b608 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 8469280a8a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 82e37c1d0f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 40e0b31b05 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new aa2386884f 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new a66781039c 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 79f7ed0be5 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new ba39c30d62 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 7f8849f1a9 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 9a7bd88f31 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new c995c7b75c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new e0577814e1 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new f4f4d5f85e 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new fadcdeb26e 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new c92f1f68da 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new b6b2df8cd8 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 26df19995b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 4e72ba4720 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new b4b4c803c5 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 80109004ee 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 5b27df3c43 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new a34393fe78 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new ec0a4e1fd2 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 958a945629 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new d91f9e6e7c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new cc395d778f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 3c43a4b16b 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new d632fa644a 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 630f61d6ef 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 534df50b3c 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 950e61c800 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 9f8047ac46 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 591f649f94 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new a2008dd789 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new c645be0fea 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new deee0b6db1 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new ae9ae8e725 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 3af15b70cf 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new df79151e82 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new af0759cfe9 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 45f900ffd2 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new b1380db516 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 22e75d5261 411: onsuccess: #2232: 1: Success after gcc: 3 commits new ab84c72246 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 29654ba876 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new edafb26aaa 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new d2137864d0 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new ad2217d31e 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new a630238472 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 1736a56865 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new b1f6814199 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new ad85111aeb 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new c392af3859 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 57f8bbcd04 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 9d2d05fca6 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 83700f91f3 424: onsuccess: #2248: 1: Success after gcc: 6 commits new d688cfc38f 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 196844eee8 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 88611c550d 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 72e05fbb32 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new e6ba70f3eb 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 787b8c7b9a 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 9c82bc66b4 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new bac7a42507 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 2401fc3425 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new ba79e50df1 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new e54b36e8b1 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 83a7ec5f35 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 81a03e9163 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 37073c7a66 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 2f2aa6a2cd 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new c24e39d9aa 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 4b803444e1 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new e78b3da941 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 349ba56a2a 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new cf5e8a2c8e 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 8598e89efd 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...]
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 (c218800cad) \ 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 1764 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30620 -> 30564 bytes 04-build_abe-stage1/console.log.xz | Bin 89112 -> 88992 bytes 06-build_abe-linux/console.log.xz | Bin 9200 -> 8508 bytes 07-build_abe-glibc/console.log.xz | Bin 235732 -> 235684 bytes 08-build_abe-stage2/console.log.xz | Bin 225304 -> 225412 bytes 09-build_abe-gdb/console.log.xz | Bin 38452 -> 38464 bytes 10-build_abe-qemu/console.log.xz | Bin 31456 -> 31420 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3792 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2688 -> 2584 bytes 13-check_regression/console.log.xz | Bin 7388 -> 5984 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 11 ++---- 13-check_regression/mail-body.txt | 58 ++++++++++++++++++++-------- 13-check_regression/results.compare | 27 ++++++------- 13-check_regression/results.compare2 | 40 ++++++------------- 13-check_regression/results.regressions | 27 ++++++------- 14-update_baseline/console.log | 66 ++++++++++++++++---------------- 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 | 60 +++++++++++++++++++++-------- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++--------- results | 27 ++++++------- sumfiles/g++.log.xz | Bin 2690188 -> 2683044 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2210980 -> 2222356 bytes sumfiles/gcc.sum | 8 ++-- sumfiles/gfortran.log.xz | Bin 900180 -> 898236 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2280 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216840 -> 216904 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443276 -> 443392 bytes 42 files changed, 202 insertions(+), 186 deletions(-)