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 e72d823703 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 9b8dd5d846 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 9f43b1c387 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards a36232aac6 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 5407321c23 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 75097255d6 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 5267508352 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 15ce0e57b5 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 71d07113c2 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 09fe042c96 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards cfbd4e01ca 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 3ddb8bb29f 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards c943061150 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 3d650e185a 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards f4ab4d23fe 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 9ef684019f 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards dcedb82a53 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards c40d5fc424 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 5ea9461fb3 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 4d2250b5f9 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 6defcd6f13 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 66e13c534f 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards af94b0232c 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 6b551e3f41 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards eab081b713 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards b5d07d0c4e 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards e90c1f30f0 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards b4cac98a40 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards cbbb309ebc 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards d7151fe6eb 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 3dd673b46c 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 41da78e1ac 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 5598f385d0 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards e9742ccc3d 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards f45602563f 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 2a7bd8a633 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards e989bfb311 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 0a180dba83 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 3f98ebe893 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards bc1daf23f5 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 16f1682b7e 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 9bbc125237 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 7acff55f5b 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards bda20046f9 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards f6ab555f5f 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 1e3ec45e0f 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards afb071c678 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 110498dddc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 3eec4f5c54 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards e15ff293a1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 7ea00d9da7 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 37fc494d1a 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 5a0d8bc3f7 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards d01e877f98 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 705d02d085 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards ead396f025 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 0250195662 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 1668f43248 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 2291ef60fd 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards da76807097 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 536c0c963b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards df34838feb 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 1adfcbb8aa 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards aa80714e88 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 3a76e1089a 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards b4cf657e6f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards c9795d2883 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 6f61237c82 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 4434bf5c24 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5da9948820 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards d7fffb7947 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 953d07ddbc 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 72696cd870 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 3a855ef973 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 4a49b755b1 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 8a4be1566c 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 06dd488a14 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 9d9a69e7e4 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards ac80cee38b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards e23c78c8bf 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 030a2b788e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards f47d0847b1 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 9c27d2c049 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 4c47903d2d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 60db9102a2 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards e3cebc9302 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards a49ab59e4e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 27750abf2c 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 65ddfd427f 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards dfea6e0056 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 4540993ec1 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards c3aa972197 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards a29956f37f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards d07b94d0cf 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards c955636dfd 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards cb0ff9dfb5 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 7b4c7d6210 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards ee10980f78 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 171c3b13f3 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 02630d2c97 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 8ed3dfee80 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new d8d30a578a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new bbdaae19bc 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 196e2293ea 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 753e398cca 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 4915871be4 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 8304195712 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 96f8a9d0f3 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 45d3ba215f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 575b196e99 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new cb68aad868 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 9012f688bb 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new cc092618bb 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 9e09da0c7a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 4a850e0751 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 0a5cf2383a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 10c775f663 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new c7182d2810 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new ebf0842572 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new e3ca035058 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 61799662f3 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new b8c11fe55f 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 07728876d0 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 8da5bde4fb 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new aaf72e1492 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 196d6da4da 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 4ccad1a31f 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 15096a0671 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new e547d8895e 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 247eb0035a 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new fa00714639 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 4a6e8c5709 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 62a91678d4 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 96f56d363b 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 6388957310 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 7ed7e97d28 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 9bb049bfdb 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 2896b7914b 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 3f3a6c714d 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 1cbe279289 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 3bc8a5d20c 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 59d67617c7 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new d39ff16006 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new d74affe9e3 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 70dbeea2a1 384: onsuccess: #2205: 1: Success after gcc: 2 commits new ebba7f2c44 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 9960e98549 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new d356017f08 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 04fdce176b 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 7b248feb96 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new f03ac4c53c 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 9371ddbdb8 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new d0e012af68 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 07b2baf66d 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 82cb1a3e53 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 7726ce500d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new a832738828 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 6758d5c25d 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new b9d5c6fdfc 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 61b84a1ece 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 7b646cf59a 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 931787bd59 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new e5073eef3d 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new f4f38f6d94 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 0c7432005e 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new f02ebae8ff 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 2bc7d3bd51 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 709991c009 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 4da9d01ccb 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 9546c6ff5e 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 9d4bd0da37 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 9af101587e 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 69b17aec19 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new e026faac45 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new fef4308349 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new bdb0252987 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new d392ba2dda 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 9d6c165b1f 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 683a69c18d 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 52a430d3d3 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 968211dc89 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 066852cb98 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 02c8843d4a 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 5af4897eac 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 78ac38b3bb 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 52ec571e8a 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 7d668492cb 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new aa2ad1ae59 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 5c0a5e56f6 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new b9d10b8055 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 43bb180612 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 1e839baa45 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new e822b65c42 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 8c189fd989 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 9877114dae 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 09f53c3070 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 431fba11d5 436: onsuccess: #2260: 1: Success after gcc: 7 commits new b54e0a147e 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new f5e5a2c649 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new d00c8f9726 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 800da84100 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 43b428c246 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 1c770e82ba 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/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 (e72d823703) \ 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 1756 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30932 -> 31012 bytes 04-build_abe-stage1/console.log.xz | Bin 88676 -> 88744 bytes 06-build_abe-linux/console.log.xz | Bin 9156 -> 9184 bytes 07-build_abe-glibc/console.log.xz | Bin 235636 -> 235232 bytes 08-build_abe-stage2/console.log.xz | Bin 225776 -> 226548 bytes 09-build_abe-gdb/console.log.xz | Bin 38744 -> 38796 bytes 10-build_abe-qemu/console.log.xz | Bin 31084 -> 31076 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3788 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2704 -> 2872 bytes 13-check_regression/console.log.xz | Bin 6088 -> 7444 bytes 13-check_regression/mail-body.txt | 26 ------- 13-check_regression/results.compare | 39 ++++++++++ 13-check_regression/results.compare2 | 136 ++++++++++++++++++++++++++++++++-- 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/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +------ mail/mail-subject.txt | 2 +- manifest.sh | 44 +++++------ sumfiles/g++.log.xz | Bin 2672300 -> 2654960 bytes sumfiles/g++.sum | 61 ++++----------- sumfiles/gcc.log.xz | Bin 2215616 -> 2242244 bytes sumfiles/gcc.sum | 46 ++++-------- sumfiles/gfortran.log.xz | Bin 899164 -> 896724 bytes sumfiles/libatomic.log.xz | Bin 2280 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216860 -> 216932 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442056 -> 444444 bytes sumfiles/libstdc++.sum | 28 +++---- 39 files changed, 275 insertions(+), 221 deletions(-)