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 90e5b79542 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards e610696945 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards ae29ac4275 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 6f18fb51d8 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 985dc7ec83 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards c6a16bf63b 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 39016933bb 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 5b02721842 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 6fa2c1384f 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 06d3a7ff7b 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards e75143dc10 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards c49f325a29 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 4aa76e66de 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 152c00bf1f 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 4ad1dd0d1d 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards af2640380e 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 4cd5d648f5 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 39e979ea3f 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 49f059bf16 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 0b46ef2055 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards e2612e7ce1 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 6ac9ca8e62 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 2388f09c3d 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 8cbbeb238d 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 0cf6f28839 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 551aab6bfd 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards a713cbcf08 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 722582f89a 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards e4761d9c8c 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 2118a29d44 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 35b34269af 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 120da6e1a1 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 1921e90d21 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards be020f3396 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 643ae208da 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards b10a43ffef 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 10a183b6bc 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 3a70a18993 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 63bd4d0b62 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 62b6cb97e9 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 5d1633c2ca 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 246527a84e 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 0e3e06a852 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 33f1e82502 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards d42083bb6a 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 9ed69cc132 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards ceb846aca1 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 6e84660344 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 7d9d9e7758 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards dad3cdf90c 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 2f8f780425 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 9149d2ac24 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards cd5134f86f 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 9d2b83cfc6 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards cb4580056f 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 916496f4f9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards bfb3735c89 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards b9eee0b631 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 1731aaebde 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 8a4da5300a 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 40df310c16 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 1f6b8388b3 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 02252c3ace 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards a08e09fff5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 81bab82838 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards bcaf2f9aaa 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 33c4c24c62 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards cd1e0600bd 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 079a2848d7 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 5d7c57a17e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards d63a322ae0 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards d3e02d139b 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards be91c45783 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards e1da4e7a92 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 74ffb4cbfc 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards d868a3859f 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 1afb98476e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 1272f87cae 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 894a88ce44 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 777b9721f2 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 1361eb222a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards a50bcfad6d 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 15c9720a42 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 224f6574b5 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 6e4c1166e2 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards c11a32a5ca 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 4632e33ebe 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 764c596c40 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards ace5527e0b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 133175b9a8 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 1b49a8636a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 8e66fda1b0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards c3e9a5ef8b 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f3d1ae1cf2 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 0e449d9df4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 440b84781e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 119719ae81 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 8df1976ebc 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 307e0fbc32 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 3f02cdbe2c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 37d272556b 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 982b50af86 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new ea6f07b691 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 996cb7c8c4 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new fcd25e6b4a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 6f42be2738 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 0387c0b11a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new c554647044 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new df0c28cd4f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new cc65814de1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 0e9d3c1e20 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new b17c778334 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new ec04998407 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new e16efb2944 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 211f79825e 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 408a1c2d24 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 2f7f4111fe 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 557af28f81 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new e1fa2769eb 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 5bd9aa1b9d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new efa6dd32c7 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new c4f548327f 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 65173589fa 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 365b122f16 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new ea8d579db0 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 3c47a13152 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ebcd75760d 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 7e72f129f8 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 8a665b918d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 07fcf67cdf 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 73c65a8365 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new e8c56d728f 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new e624abb300 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 2c1dffc1ac 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 256685bb7c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new f9348fa766 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 9d85347dab 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 98e6331c85 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 79097e24d1 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new d2d1b95abd 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 617cb6c547 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 25bc6daa75 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new d0e5386bdc 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 4750c116eb 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new eda4f7c94e 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new b98571f28e 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 07e60e4ca5 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new ae4b6693f4 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 7966bb3e11 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new d13bcd6841 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 7ff42d8f31 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 80ba2911b4 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 8651d65a86 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 22f401be12 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 616d9c414f 384: onsuccess: #2205: 1: Success after gcc: 2 commits new ca12188fab 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 045819c660 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new a2a374c076 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 19bc125b7f 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new f91d19f688 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 095c594008 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new dae6cd06d4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 70f9ce20ca 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 1ee14a2c2b 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new ca4f9379bc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new c0b85640d6 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 04c556b8c5 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 3b9a4b75e4 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 4118054966 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 774e64fe4f 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new ff237f334c 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new ff3403ff9c 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 6b58e332b6 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 9d00c5a535 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 909c849b8e 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new aaf46f8604 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 0f49b1605e 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 0d9d998ccd 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new b5a03d6106 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 2938970a04 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 972ca9647a 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 116d6734e1 411: onsuccess: #2232: 1: Success after gcc: 3 commits new cb9ae4d781 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new d6266e4e93 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new c518c05a4e 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new f9f485ad05 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 086eee59e9 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 32aeba4dc8 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 9056353ff3 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 514a29a88b 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 9f4b2d5aa9 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new ce43c3c6f0 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 25985def76 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new ecb5a713ab 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new aaf887e8da 424: onsuccess: #2248: 1: Success after gcc: 6 commits new c76f9da26a 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 6c170d879d 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new a38b0e918d 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 8615f30f52 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 045a9af7a4 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 7b82da807a 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 21ad25c1fb 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new b3c6f7a250 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 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 (90e5b79542) \ 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30580 -> 31456 bytes 04-build_abe-stage1/console.log.xz | Bin 88456 -> 88860 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 8520 bytes 07-build_abe-glibc/console.log.xz | Bin 235680 -> 235472 bytes 08-build_abe-stage2/console.log.xz | Bin 226888 -> 226244 bytes 09-build_abe-gdb/console.log.xz | Bin 38420 -> 39224 bytes 10-build_abe-qemu/console.log.xz | Bin 31848 -> 30700 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3804 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2788 -> 2784 bytes 13-check_regression/console.log.xz | Bin 6056 -> 5264 bytes 13-check_regression/results.compare | 16 ++++----- 13-check_regression/results.compare2 | 19 ++++------ 14-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_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 2634856 -> 2657580 bytes sumfiles/gcc.log.xz | Bin 2217320 -> 2204508 bytes sumfiles/gfortran.log.xz | Bin 892004 -> 892792 bytes sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216976 -> 217012 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443432 -> 439700 bytes sumfiles/libstdc++.sum | 31 ++++++++-------- 33 files changed, 84 insertions(+), 92 deletions(-)