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 8f4733f768 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards a5559dbfe9 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards e1825d97c6 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 9329d11cbc 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards aeaa0494a0 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 9c380b2366 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 2ce7444312 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 9991ae45af 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 160dd554cc 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards ed685f53ee 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 320c149db3 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards ac2bd9bd01 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards c07d9184f6 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 1cdc666697 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 5160820c7a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards b7103de881 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 92ceea43d1 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 2933f75077 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards e1248d0f7b 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 6533283adb 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 6e653d7f58 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards d48768e8a3 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 322dd76f05 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards d960c8ed42 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 9128295305 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 0d2432b1be 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards eb7bd4afbf 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards c7565169f2 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 31061bf342 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 4445c7cd5e 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards e05f42125d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 243b037d05 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 42f9a79bd5 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 5c01795b9b 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 5d523058aa 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 0f598b1033 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards d17c0d4ea3 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 03dc08e944 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards ab56472673 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 9e4cfc895f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 09017c6abf 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 22e58e109b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 457c482cec 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 106d7349e9 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards b9fc32a8cd 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 9f066cd843 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 247f7df857 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards f5521a20eb 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e7c305bd09 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards fa933bc450 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 270e4cc4d4 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 2af0d86fe0 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 324f91db30 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 117aa01e13 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards c9e715e8b9 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards f6f1522894 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards e2f4191609 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 54896c9cc4 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 180e134a6f 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 10ca2fde33 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 625253c58b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 98486002db 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards cf67850ff5 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 6ffdb24527 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards aca8895890 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 3101b39233 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 1f359b001d 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 5216d61645 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 9c1e02f2c1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 781836c168 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards e578a9d7fa 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 9c41ee914e 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 673974baa0 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards e9f0465f84 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 68435baa05 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards ba12791d82 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 8c2729b5aa 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 379a20ba97 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 4f306eceb4 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 99479a272c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 44a9d9dc2d 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards c7b398c045 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 9586fc9b96 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards ef691fd153 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f4297ab681 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 98f13f55df 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 80be1d6918 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 7c311b69b0 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 00293731bd 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 0b1441dcbe 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 4d601875f0 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 2b7fda3491 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ffb4592499 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 45743fc075 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards f8d7a27d68 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 139e253da7 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards d4dfd88f32 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 446b92ba56 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8655909fa4 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 30c566f47a 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards aa398f547a 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new edd7d321c8 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 330bfd8aee 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new de119468d0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 0d80668a09 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new aab7b0a544 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new ab34105c35 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 6c9a6a98c1 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 43434fa445 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 08b906abe2 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 5b38ad7844 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 84d0762c22 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 5531fa081e 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 9d212e178c 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new c70e2e5f2f 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new fd825d4ce1 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new ee5eec3d90 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 99290eb2f7 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 542f87335a 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new b86d537283 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new dbf2cb0cf1 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new fae56356d8 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 26951b6c5b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 593999f2cc 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 3b545b8f73 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 7e90a4fc26 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 43cab14ef4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 52e4f1f257 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new ee54b0f2af 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new cae530f5cb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new b7777f3990 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 4ee388a376 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new ae66052c26 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 84beba3168 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new d9c3d4489a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 64181f75b1 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new b60d2fda2b 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 8fa938d69b 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new a611ff72b3 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 44995109f1 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 270086e057 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 125494add0 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 8f39c53bc1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 558b94e5a3 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new bc10f13ce8 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 1c35ba2caf 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new a90cd72b88 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 67c9ed3f4c 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 7aaa0a0556 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 26e4872d9b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new f59158bf8b 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 12a8dfaf91 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new a295d91c7b 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new a3e757cd71 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new dbf24ea1ca 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new d0bae5395f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 3059c65c56 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new eac6cc9f8e 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 57823d2647 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new cf39573304 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new e1245a177b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new ba09026320 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new a732679554 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new d50fef421d 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 417222a869 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 0aa80bde40 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 85c785af73 387: onsuccess: #2208: 1: Success after gcc: 2 commits new ddb04c387c 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 52c0146cea 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new a132ddc667 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 214f627c91 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 24dcf8ef01 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new c17fa89192 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new e2972879b8 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 04efeebfd4 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 357fb40c14 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 180d929fc7 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 5c38447f45 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new cc3fbaaedd 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new cbd1c82e3d 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 2be38235ff 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new c4d4642073 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 072dee5d81 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new a84b5311e1 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 2969a13de1 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 6686c544bc 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new c7bea5bd9e 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 8f243c1936 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new f04d0b1c5f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 8e61524e49 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 21b266ee91 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 05b521bda3 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 61d03201d6 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new a0fabdffb0 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new d7a52989ed 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 72d27a5b04 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 289b4af259 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 55b4f7c0f6 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new a43ea83183 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 0260af5139 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 9c094787ae 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 18b32a2eae 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new c30464c1ac 423: onsuccess: #2247: 1: Success after gcc/linux: 8 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 (8f4733f768) \ 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 1776 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30864 -> 30720 bytes 04-build_abe-stage1/console.log.xz | Bin 88968 -> 89584 bytes 06-build_abe-linux/console.log.xz | Bin 8500 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 236016 -> 235544 bytes 08-build_abe-stage2/console.log.xz | Bin 225744 -> 225832 bytes 09-build_abe-gdb/console.log.xz | Bin 38520 -> 38612 bytes 10-build_abe-qemu/console.log.xz | Bin 31240 -> 31352 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3800 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2748 -> 3272 bytes 13-check_regression/console.log.xz | Bin 7024 -> 5476 bytes 13-check_regression/results.compare2 | 82 +++++++--------------------------- 14-update_baseline/console.log | 66 +++++++++++++-------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++------ sumfiles/g++.log.xz | Bin 2651492 -> 2672356 bytes sumfiles/gcc.log.xz | Bin 2224628 -> 2202868 bytes sumfiles/gfortran.log.xz | Bin 891740 -> 896992 bytes sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217000 -> 217024 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 441640 -> 443108 bytes sumfiles/libstdc++.sum | 30 +++++++------ 32 files changed, 89 insertions(+), 135 deletions(-)