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 572212afc6 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 8078d711b7 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards ac8867c016 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 56450a16de 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 2b3205ea90 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 78e496add6 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards c0480bd84f 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards bcd0959892 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 59d3b803d6 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards e3439dd638 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards c3a18503ab 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 69d22ee140 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 078daf4d06 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 6af9138e4c 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 14c99a5e5a 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 8a88da7a65 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards ed53f83ca9 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 6d4607e809 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 8cd562d4c7 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 3b3d9c42ac 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 806974f932 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 25a6d8c75d 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards c5f150091d 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 5ebe8e03db 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 3ef1f202b8 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards b1f870405f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 4e1a82583d 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards d57e8b4867 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards d7ab4b783f 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 5002b4af02 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 3d7a805b5a 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards da8b179178 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 1aa48a438a 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards d0cb35f6ec 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards b9d58f7434 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards a5b7f39e0a 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 3c4018b6be 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards cfdde42a36 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards be56c13698 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 57da896f3d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 2a7da81828 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards dddf5ffc8f 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards e3ce94ba34 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards ca6c48d0a6 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 2f0ca9d3f9 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards da3a48ca8b 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards fbd0d14e7b 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 5cf84f71d3 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 60d542b482 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards eaf1800912 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 79b3050d86 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 851c07c6fd 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards e9af489e4e 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 39479a504f 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards f111e56e19 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards d12ce3b90c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 9144aeefca 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 4616bec857 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 85633ec0c4 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 4bdad6ccd0 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 0998d9207b 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 10419274d9 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards fefe98c8e2 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards bcfd14a2e4 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 8eb7649d64 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 5edc0956ff 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 5a5a9c8a51 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 02a4b684b0 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards aaf80579e1 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 028ee0bfd7 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 4a79a10f47 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards c3ea946fa5 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards f5482bd46b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 9cd7cbcc0b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 47896e6cc3 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 3cc5d7e268 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 2a49396961 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 07e5e72506 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 6132283856 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards fb28800cc8 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 186a5a64b1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 954ec5e112 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 498f71735e 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 50140eb028 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards bb55c9fc3a 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 30351c2d99 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards dc8246c1e0 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 1af249f1e8 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards e225dde8ec 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards bb2048691c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 12b20c0130 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards ad9420f155 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 9e8d71b5b6 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 37c249713e 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 59c55a2cb3 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 906a7eff32 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 40274b87a9 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards c84f79c6da 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 5fc7aef5dc 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d79627d006 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 3ce3562931 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 58b78a1ece 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 2bdeae0fe9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 2db35972a7 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 6d1ba4e93c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 002eae0008 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 6d1ddc606a 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 4637c914f0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 21cca2771a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 701920cc4f 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 1d9997193f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new baba404779 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 094115977e 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new c900d193ff 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 09f73376de 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 5726f16484 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 483f8cdf0b 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new aa39033c01 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 52ada3562b 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 9eba991063 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new b359225b83 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new bfdb1d59e3 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 9d226c2fd0 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new c775f57496 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 9d8a2923c9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 9476810da3 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 9e7bd46ac4 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new eccd6a7dc6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 7936076e32 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 4bbb3ca6a3 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new f3b640f964 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 7162bb1b77 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 864b41a241 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new c8bf42baaa 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 7cec1cfad7 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new c8126fde6e 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new ea5cdfff1c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new f69e535c42 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 45c9bb0457 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new bc175da19f 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new ec783b9a22 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e695f3b928 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new d45fc6548d 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new d6c6975295 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new e2e4eb895e 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new a220781200 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new c92fadf97c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new b7dbf99efa 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 17a6a73a4d 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 402f4eb40c 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new b5b6ab66f8 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 9a470f87eb 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 53cf285364 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 30656ea0eb 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 6d39fc029b 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 5787847a7e 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 52c7d35f61 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new f73aedd498 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 277089eb59 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new e11b60771e 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new df52b9d428 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 28ce432e7b 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 5926648464 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 5526b2782c 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 5231db9be9 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 46ba71aa4c 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new ba70d58fd9 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 73d1847c67 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 1a6f621fed 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 1148fc487e 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 19803213aa 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new fc0c2bf8a0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 60059c3eb1 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 2f2a807442 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 0effae5389 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new a8e2f34977 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 1a175d6961 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 534a5831f7 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new b8c48656a6 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 4c7b6ccea0 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 08deeba3bd 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 596ece4f65 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new ab512b5b9c 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 6b13c6dc47 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 7db39b9847 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 929f8e242b 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new c9008f282a 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 4a37068a6d 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 7d2535b15a 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new c4b378a0d5 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new dbc280afb4 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new c812c56efb 424: onsuccess: #2248: 1: Success after gcc: 6 commits new acedd20c9d 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new e4ea84d2ed 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new fd51c587a0 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new d739e9d36d 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 662d457a8d 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new ac05cbd169 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new c5a3ef3e7b 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new c543d6a7ea 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 7d61b1359e 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new b345e87b9c 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new d6964f266f 435: onsuccess: #2259: 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 (572212afc6) \ 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 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30944 -> 30668 bytes 04-build_abe-stage1/console.log.xz | Bin 88796 -> 89236 bytes 06-build_abe-linux/console.log.xz | Bin 10536 -> 12936 bytes 07-build_abe-glibc/console.log.xz | Bin 236128 -> 235524 bytes 08-build_abe-stage2/console.log.xz | Bin 225716 -> 225948 bytes 09-build_abe-gdb/console.log.xz | Bin 38672 -> 38460 bytes 10-build_abe-qemu/console.log.xz | Bin 31308 -> 31200 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3804 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2708 -> 2592 bytes 13-check_regression/console.log.xz | Bin 5844 -> 9052 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 707 ++++++++++++++++++++++++++++++++-- 14-update_baseline/console.log | 66 ++-- 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 2639536 -> 2657624 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2198340 -> 2196008 bytes sumfiles/gcc.sum | 646 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 891672 -> 894316 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217016 -> 217148 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 441356 -> 440840 bytes sumfiles/libstdc++.sum | 24 +- 38 files changed, 1110 insertions(+), 413 deletions(-)