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 27b9aa1ce0 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards f67a5785b1 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards e7f4ca86b4 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 100cab134e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards de293b75e6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards a06af9c92d 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 98dedec843 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards abfff5cdff 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards bb3b0b085f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 4554e619b0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards c5b1eafc06 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 5fff3f6e13 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 56cc15e847 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards a59cb3296b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 649314864d 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards bbc50f78e2 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 87f1842418 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards efaca7e9b8 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards a8d6febdf3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 3be662e298 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 82e007a8a0 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 4db6313191 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards a0167786c3 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 787f2c1c2a 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards a3dbf2ae20 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards b52313a056 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 9711620ecd 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards a8fbbd59cf 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 686e619c57 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards d77f0d3b58 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards ce3f3c668a 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 0764cb23db 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 9baa208bc7 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 71a535758b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 3ba3d20ee5 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 6d86818c3f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 6ad315550e 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 19dff4c7fd 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 037e1b1d2f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards f358e7f8dc 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5e4634ebe9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 4edfa97792 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards a28214cc0b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 2855af6bbc 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards a8a695566c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards c0d1518d87 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 03e201a0cb 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 5886c08b26 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards cdf8a96dd1 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 6209b23083 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 1c20e75198 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards e55c107ba7 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 5183326d8f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 82476d6327 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 0b769093b6 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards a0b1a11622 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 8f969a4b2d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards bcb023cb54 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 62790d3aad 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 3f7c239b32 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 90e4967773 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards f2e5d9e7c9 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 8da6743af9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 54a8239ed6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards bca09203f9 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 934989e53e 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 5ffaf63ad0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 5638c84bb4 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards a195b24c55 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 4aa26d632f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 68e9e1139f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards a84fc40a14 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 3c428cca48 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 7475f386c5 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 851675e935 301: onsuccess: #2118: 1: Success after linux: 16 commits discards f0c07b92dd 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards b795fda38a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 322c31e4d4 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 0e12e02ed1 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 927a30fdb7 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 38fcf18588 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards faa31e0434 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards ba9582baf6 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 542705ab64 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 130fafce7b 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 27bcc7ed08 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards a9b67afeed 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards d916a7a80d 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 226bffc646 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards e3b0292051 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 99729e871f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards c49dfed4fd 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards e6c924a279 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 10f6716afe 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 8a589daea1 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 5f60d9b4cc 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 09a39da940 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 047667aadc 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 71d1e4784c 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards addc644f89 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards add5856efe 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 8bd6534228 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 73efd75629 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 31082fb899 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 4ba8adb31d 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new c16ea4128e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new c55f3fb17b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new dbc020011b 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 2ff20b5f49 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new e983178afa 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 67933c2028 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new d7ad15d932 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new eebef4a2b8 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 8b07fa81fb 287: onsuccess: #2103: 1: Success after gcc: 9 commits new ab137db75b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 353ebba8e9 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 524a14fa35 290: onsuccess: #2106: 1: Success after gcc: 2 commits new aab6cd024a 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new ffe3606d60 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new f811395522 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new b8e84ce866 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 9d0090b795 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 2d14af48b5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new b12ceba017 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 70569885a6 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 58f7d7aed9 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 5fcfb81f9a 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new eabf6123ba 301: onsuccess: #2118: 1: Success after linux: 16 commits new 83b3d61309 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new c77ec9b56b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 9c9b185915 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new fa99e0e15f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new e4a8d7d0e7 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 7bc6da3197 307: onsuccess: #2124: 1: Success after gcc: 2 commits new c96514e106 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 94bc3a91ad 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new b2bd13ed8a 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 7c911f7104 311: onsuccess: #2130: 1: Success after gcc: 4 commits new c53c0f4765 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 549f6ebbee 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 5a9b656c8a 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new b081b0a4ed 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 582d74d31c 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 43d0c6d6ce 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 904a4b2a43 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new f7f4be1bc6 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 8bc3c7887b 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new f5e1fe9e41 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 455acbdd38 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 8d3cc2982f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new d899ac606b 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 114004c511 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 02361aa2d1 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new fe364ae435 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 4c91724802 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new d488a1804a 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new d68941201a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new b0bec8a61d 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new df66f58348 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 7e65fd3723 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new dac26ece7a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 81891dd92d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 265b38748c 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 3231e47f42 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new a51a7735a5 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new dc95154cea 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new a77896f540 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new fa2421a487 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 255e8d2052 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 0238d45970 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new e375ff3401 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new a3fc06f1e8 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 84dcd4e760 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 5fc0dd9330 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 427ff79aa2 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 68cc29feeb 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 14708159b9 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new d5aab85bc2 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 802c15c5ee 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 87ea01862f 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 61778d9793 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new a331fc7b0d 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new e7e81f1cd9 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 8d94a0ef7d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new cb1ae06d7f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new cdb7e9e902 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new e788f13756 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 889714bb4b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 64684810e5 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new dc5659d281 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 399869a449 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 33dc2d6cf6 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 617db9c346 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 5cd98cc0b8 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 48748abb02 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 24298a3762 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 82d2ef82e8 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new e39ba4ce30 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 0b646bd12f 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 9afab76d3c 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new cbfd4c6d05 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new a5e97f271c 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 122832e3f2 376: onsuccess: #2197: 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 (27b9aa1ce0) \ 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 1752 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30864 -> 31444 bytes 04-build_abe-stage1/console.log.xz | Bin 91456 -> 92112 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8916 bytes 07-build_abe-glibc/console.log.xz | Bin 236256 -> 236868 bytes 08-build_abe-stage2/console.log.xz | Bin 227556 -> 228280 bytes 09-build_abe-gdb/console.log.xz | Bin 38064 -> 38592 bytes 10-build_abe-qemu/console.log.xz | Bin 31868 -> 32364 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2892 -> 3028 bytes 13-check_regression/console.log.xz | Bin 6292 -> 7700 bytes 13-check_regression/mail-body.txt | 40 - 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 108 +- 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- sumfiles/g++.log.xz | Bin 2652092 -> 2637088 bytes sumfiles/g++.sum | 48 +- sumfiles/gcc.log.xz | Bin 2219936 -> 2185368 bytes sumfiles/gcc.sum | 2123 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 888348 -> 886900 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214460 -> 214324 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444076 -> 438936 bytes sumfiles/libstdc++.sum | 45 +- 41 files changed, 1344 insertions(+), 1262 deletions(-)