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 0dc530c9a8 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards f83000a188 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 44753fbffa 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards c5c6eebdcd 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 5aef975b78 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards fe3f7b2339 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 8048565d1b 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 0bb404759e 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 0760b0eedd 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards bd4c0da0a6 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 1301559955 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards fb0291c963 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards c70368e52f 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards fa0ac8e678 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards b3594e30fb 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards d1dcb7dd9b 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards d019a34580 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 68bd15df1f 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 9776b9fe06 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 58af123d19 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 00c7ce7c67 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 61f3a8e6bb 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 8c771af068 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 923b8bfce3 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards bd406557fe 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards f69b7f6ccd 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 0c7d2ff8e0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 1686871175 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 742247cef3 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards dfc5effd06 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 447d6751d7 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards b91797c55a 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards da6c484fe5 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards fb74f92484 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 9951f70662 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards d76a590ec9 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 4e84e4bc7a 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 8cf2e14530 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards b0af8afd54 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 1a5d1aaab1 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 0000e1fe0c 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 6f247b3126 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 742da7a810 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 609d3d8657 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards cb3556fa5a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards c456591c06 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards b92377a22b 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 39dae4c4b0 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards c817198cc9 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 8c2960a220 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards dfd95e865e 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 760d539ca7 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards e03034df85 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 8f37fd6261 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 72988dee2e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 5905a0a3a7 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards a2d51efbcb 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 8605e8c8f9 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 05566765c7 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards ae40464f77 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 13105a0996 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 08723423ad 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 048b445d44 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 05e7a82a92 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 330c7ba6e1 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 5edc3d2d67 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 01599e5b4d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 38aefbcfe5 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 0dd775470f 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 068d3512aa 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 3f3ca88194 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 44f1307493 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards a10a9a817f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards ef6c438ed7 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 487c18be67 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards a8b2cd4e06 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 9ec02276d8 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 99c65ead60 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 8e4567f9cc 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 8106d8bf07 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 4fa6a10479 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards dd3c34889b 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 6ccedec883 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards cbfb325748 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 6fe6d61c12 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 5d90ae7dc0 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards b4c3249697 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 397c53d0bc 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards a991f077bf 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 7ab27b4d52 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 482f7888d3 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards cfb25ed8f8 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 8f36481d52 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 8642db3f12 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 7b6c8fd70b 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d69dcc0e79 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 2e37881508 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards b4d0aba239 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards eae41b8789 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards f418810369 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 709d2ca8dd 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ba9da5d472 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 37d272556b 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 3f02cdbe2c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 307e0fbc32 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 8df1976ebc 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 119719ae81 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 440b84781e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 0e449d9df4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f3d1ae1cf2 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new c3e9a5ef8b 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 8e66fda1b0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 1b49a8636a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 133175b9a8 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new ace5527e0b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 764c596c40 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 4632e33ebe 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new c11a32a5ca 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 6e4c1166e2 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 224f6574b5 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 15c9720a42 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new a50bcfad6d 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 1361eb222a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 777b9721f2 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 894a88ce44 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 1272f87cae 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 1afb98476e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new d868a3859f 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 74ffb4cbfc 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new e1da4e7a92 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new be91c45783 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new d3e02d139b 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new d63a322ae0 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 5d7c57a17e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 079a2848d7 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new cd1e0600bd 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 33c4c24c62 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new bcaf2f9aaa 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 81bab82838 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new a08e09fff5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 02252c3ace 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 1f6b8388b3 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 40df310c16 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 8a4da5300a 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 1731aaebde 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new b9eee0b631 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new bfb3735c89 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 916496f4f9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new cb4580056f 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 9d2b83cfc6 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new cd5134f86f 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 9149d2ac24 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 2f8f780425 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new dad3cdf90c 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 7d9d9e7758 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 6e84660344 384: onsuccess: #2205: 1: Success after gcc: 2 commits new ceb846aca1 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 9ed69cc132 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new d42083bb6a 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 33f1e82502 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 0e3e06a852 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 246527a84e 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 5d1633c2ca 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 62b6cb97e9 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 63bd4d0b62 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 3a70a18993 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 10a183b6bc 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new b10a43ffef 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 643ae208da 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new be020f3396 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 1921e90d21 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 120da6e1a1 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 35b34269af 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 2118a29d44 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new e4761d9c8c 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 722582f89a 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new a713cbcf08 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 551aab6bfd 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 0cf6f28839 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 8cbbeb238d 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 2388f09c3d 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 6ac9ca8e62 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new e2612e7ce1 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 0b46ef2055 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 49f059bf16 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 39e979ea3f 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 4cd5d648f5 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new af2640380e 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 4ad1dd0d1d 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 152c00bf1f 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 4aa76e66de 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new c49f325a29 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new e75143dc10 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 06d3a7ff7b 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 6fa2c1384f 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 5b02721842 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 39016933bb 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new c6a16bf63b 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 985dc7ec83 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 6f18fb51d8 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new ae29ac4275 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new e610696945 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 90e5b79542 431: onsuccess: #2255: 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 (0dc530c9a8) \ 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 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30652 -> 30580 bytes 04-build_abe-stage1/console.log.xz | Bin 88924 -> 88456 bytes 06-build_abe-linux/console.log.xz | Bin 8860 -> 8484 bytes 07-build_abe-glibc/console.log.xz | Bin 235312 -> 235680 bytes 08-build_abe-stage2/console.log.xz | Bin 225508 -> 226888 bytes 09-build_abe-gdb/console.log.xz | Bin 38608 -> 38420 bytes 10-build_abe-qemu/console.log.xz | Bin 32000 -> 31848 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3796 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2964 -> 2788 bytes 13-check_regression/console.log.xz | Bin 7200 -> 6056 bytes 13-check_regression/results.compare | 16 ++++----- 13-check_regression/results.compare2 | 46 +++++-------------------- 14-update_baseline/console.log | 62 +++++++++++++++++----------------- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++----------- sumfiles/g++.log.xz | Bin 2650332 -> 2634856 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2221464 -> 2217320 bytes sumfiles/gcc.sum | 2 +- sumfiles/gfortran.log.xz | Bin 895304 -> 892004 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216956 -> 216976 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439764 -> 443432 bytes sumfiles/libstdc++.sum | 29 ++++++++++------ 38 files changed, 98 insertions(+), 121 deletions(-)