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 d6964f266f 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards b345e87b9c 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 7d61b1359e 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards c543d6a7ea 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards c5a3ef3e7b 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards ac05cbd169 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 662d457a8d 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards d739e9d36d 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards fd51c587a0 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards e4ea84d2ed 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards acedd20c9d 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards c812c56efb 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards dbc280afb4 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards c4b378a0d5 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 7d2535b15a 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 4a37068a6d 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards c9008f282a 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 929f8e242b 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 7db39b9847 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 6b13c6dc47 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards ab512b5b9c 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 596ece4f65 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 08deeba3bd 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 4c7b6ccea0 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards b8c48656a6 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 534a5831f7 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 1a175d6961 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards a8e2f34977 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 0effae5389 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 2f2a807442 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 60059c3eb1 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards fc0c2bf8a0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 19803213aa 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 1148fc487e 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 1a6f621fed 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 73d1847c67 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards ba70d58fd9 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 46ba71aa4c 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 5231db9be9 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 5526b2782c 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 5926648464 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 28ce432e7b 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards df52b9d428 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards e11b60771e 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 277089eb59 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards f73aedd498 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 52c7d35f61 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 5787847a7e 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 6d39fc029b 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 30656ea0eb 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 53cf285364 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 9a470f87eb 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards b5b6ab66f8 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 402f4eb40c 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 17a6a73a4d 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards b7dbf99efa 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards c92fadf97c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards a220781200 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards e2e4eb895e 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards d6c6975295 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards d45fc6548d 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e695f3b928 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards ec783b9a22 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards bc175da19f 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 45c9bb0457 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards f69e535c42 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards ea5cdfff1c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards c8126fde6e 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 7cec1cfad7 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards c8bf42baaa 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 864b41a241 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 7162bb1b77 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards f3b640f964 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 4bbb3ca6a3 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 7936076e32 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards eccd6a7dc6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 9e7bd46ac4 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 9476810da3 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 9d8a2923c9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards c775f57496 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 9d226c2fd0 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards bfdb1d59e3 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards b359225b83 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 9eba991063 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 52ada3562b 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards aa39033c01 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 483f8cdf0b 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 5726f16484 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 09f73376de 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards c900d193ff 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 094115977e 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards baba404779 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 1d9997193f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 701920cc4f 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 21cca2771a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 4637c914f0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 6d1ddc606a 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 002eae0008 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 6d1ba4e93c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 2db35972a7 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 2bdeae0fe9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new de23328cac 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 6d0114b2eb 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 375c35efa1 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new c31ba642f7 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 27096d2ed0 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new d40c390fbb 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 5cba98e7c3 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 03fbdf292a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new a7dad31395 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 7b21e8aa16 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 91840c2c5c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 67431c3270 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 498be3d7b3 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 834fd09f92 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 96a663ac18 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new d85aabd802 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 96e7bc1ab6 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new dec57a5e8a 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new dc1a0a5739 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 839093e66a 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 994313d8d8 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 4cec9cc406 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 5cbab77c59 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new d4a47bc72c 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 837f09a812 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new e81d640e83 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 7bbd9c6083 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 47d5387ce1 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 402b3b3522 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 7228d5aba2 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new c91297f13a 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 9a301efadb 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 9b3bd2b386 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new aaba8a93f8 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 08705e7c61 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 5c82c40a8f 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 6fa47ef3b8 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new a38c1c92d8 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 8c5cdad229 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 13608b9078 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 2d139f3590 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 5596ee5e09 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new f827431ee8 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 92f14be713 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new c4773ca7cf 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 02e90618d2 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new dcfc44c4c9 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new d84e53e53b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new cecb8b2321 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 093861ceaf 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 23ce3b2124 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 3491e7b55f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 4f27f8965a 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 354d6d0b4b 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 6cbef0d6b4 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new b6df737179 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 5346f61f7f 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 45c6b87100 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new c9b5e8e0e6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 6d8c1232fa 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new b350b2f98c 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 2ad8d588a5 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 5b345ef7a2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 3d732453ab 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new bc98467c73 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new ea413a3309 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new ffd809fda0 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new e7c33069d2 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 6ad2e6e793 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 8c2d6dafac 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 452fc8ee3c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 93e57cd11b 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 6c8787039e 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new c54e84e83c 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 9f9e28955e 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 6066283d02 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 3a725f40d0 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 2b2fd55c00 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 3018a872e5 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 0f6ac980bc 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 77f30d8cfe 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new b7e1da5342 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new e3984e03d6 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 771be66921 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new ec8375ee15 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 723a668edc 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 4aa8afe7b9 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new cb6743136e 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 01b84a0deb 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 0191398ab8 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 037f8308bd 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 09f27366d0 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new ff7dd706ad 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new e47b59d485 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new acfec0089b 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 67e4cb3423 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new b0110420cf 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new b7a5d5c6a9 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new aad1c3bbbf 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 3bdedd0f90 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 02a2181bd9 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new d85646dce6 436: onsuccess: #2260: 1: Success after gcc: 7 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 (d6964f266f) \ 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 1804 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30668 -> 30672 bytes 04-build_abe-stage1/console.log.xz | Bin 89236 -> 89116 bytes 06-build_abe-linux/console.log.xz | Bin 12936 -> 12912 bytes 07-build_abe-glibc/console.log.xz | Bin 235524 -> 235800 bytes 08-build_abe-stage2/console.log.xz | Bin 225948 -> 225380 bytes 09-build_abe-gdb/console.log.xz | Bin 38460 -> 38344 bytes 10-build_abe-qemu/console.log.xz | Bin 31200 -> 31348 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3792 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2740 bytes 13-check_regression/console.log.xz | Bin 9052 -> 5628 bytes 13-check_regression/results.compare2 | 711 ++-------------------------------- 14-update_baseline/console.log | 66 ++-- dashboard/dashboard-generate.sh | 2 +- git/gcc_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 2657624 -> 2659756 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 2196008 -> 2218096 bytes sumfiles/gcc.sum | 12 +- sumfiles/gfortran.log.xz | Bin 894316 -> 889820 bytes sumfiles/libatomic.log.xz | Bin 2264 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217148 -> 216840 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440840 -> 439592 bytes sumfiles/libstdc++.sum | 29 +- 33 files changed, 125 insertions(+), 745 deletions(-)