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 de22132a01 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards fd870f3d68 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards a1197c26fb 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 3e4d887afe 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 2d6f322358 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 7bc8009b02 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards e9897f9327 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 0a2f3b5a1d 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 5a4ccb9457 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 070be68c62 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 0d56fb9232 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards c90ab2c3d9 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 3607fdd69f 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards a4c18c7318 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 4228296b86 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 003bc3c6ac 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 66830e64de 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards c5526f2053 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 6428d5aa5b 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards f10a0abc61 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards dacab92140 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 5c14309a50 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards a2fbe4480e 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards eebd2466ff 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards df3a547eb3 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 8206fe3888 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards bf06873a77 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 36134d5feb 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 5c42c99722 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 2a82f673a5 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 7d38289798 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 1171e5ec60 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 6aa0281260 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 0c9426eaba 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards a55e7116b3 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 028b2e1e52 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 6d1e9e029a 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards c1c1277956 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards d38c36fdc2 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards f8161bbe37 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e5ad05345b 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 0edab593e6 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards c56b28484e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 5d62ab644d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 9fd399cb41 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 7d1c2327a4 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards dab055f7f9 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 62a8f589c4 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 101d05eb7c 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 24b6a8dfad 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 93862d8c59 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 18b45bc523 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 66f451f690 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards d89e7b3197 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 6b510a0c18 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards d066d398d9 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 399b6f2270 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 1afed830bc 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 831b029586 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 0320ad54ff 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 8578779944 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 4d7e759c83 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards ff9926796b 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 058edce224 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 43859cd9be 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 3318ea6cfa 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 71131b4289 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 7aa450321e 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 929b675436 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 43d3bdc320 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 6198558b96 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 8a7813f9f4 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards b27b46be9e 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards ca5af0204a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards a68bdb2f4f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards b6a6d096f3 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 4ebd35cde7 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards d0b7218e7d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 70755ef4f6 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards db36c9ecd0 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 34b66adfba 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards aff609cd67 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1f72bf7285 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 72467cf58d 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 81e8138213 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards a1154fd64a 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 264b5552ff 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 23221e582f 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 16ee3d6b74 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards f4208ecd6c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards bcee8d8e37 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards bdff9705c7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 9c207895d9 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 0be9ba5d30 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards c0d451aff6 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards ac4afde418 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 4373347163 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 4e73389463 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards fa0557893e 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards fb64520dcb 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 73554e9be1 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new bf09d1e104 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 1ef18d4cd9 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 25bad9d80b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new b4e6d4d618 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new ad3f4a3a24 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new fe27f2b3b2 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 1907d75190 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 25095eb9e6 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new fca9d664c9 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new ec7395454f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new e2ebaec98b 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 366c33a556 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new b00cfe2681 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new f048a72309 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 0831adefbd 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new f6ae03b661 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new ca4750c105 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new f80c4f8c0d 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new ba6ec2948e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 1d26257ddd 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 1a053af4ad 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new a6040fcfb4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new e53d662b44 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 9c74b6e35e 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new d306e56766 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new b9a72b6843 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 8a15960b9e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new ddf36d5c56 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new d55c15ee8b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new b3cb2177f3 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 32a319fb0f 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 9cfaa425f7 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 2a22b7a3f8 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 5a50b0244c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new ed54575174 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new ab7581dc26 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new b2bc618eeb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new c7b54f5586 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new ec960efa5e 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new f8062161e7 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 5e10e91683 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new b4488e6940 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new b77dce2c37 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 592ee54d44 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 730d12d58a 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 328f7ea3dc 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 7779594c46 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 395234ca45 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 3559d8fc63 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 42212e2e6b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new c8fecf0925 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 38219855e2 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 9fcf1f8f4d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new a551ea3309 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 73429a79fc 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 91a6807ea3 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new cee4c32aab 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 4db90325f6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 5eb414b942 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 23a2b0cfab 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new a41a6b8bae 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 8307f54277 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new c81317eeb4 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 923d2de2a5 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new e15b70bf9f 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new c3aa3e221b 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 31e5e355e6 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new c2db365eaf 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 0af1472876 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new c67b67219e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 1146edda6d 384: onsuccess: #2205: 1: Success after gcc: 2 commits new ae286f9a3e 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new a527cf6b78 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 981a7f08a2 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 487d1ad8a3 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new d73828aeb9 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new d186a83686 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new cc88a9c7c4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 295d75acf0 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 6683115ca3 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 23d97c80f5 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 675f748b84 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new e52df10c25 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 9362cee3f4 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 4f68f21d97 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new af7d4a3936 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new cc541e86e3 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new fe15411ba9 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 3e0b43c6ba 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 19ae46fd51 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 4452ebad36 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 65feab1ebe 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 4d5a8212f4 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 6aaff9d6cc 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 978593a07a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 7b9188cff3 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 8e1717a0b6 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 4fe834feba 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 17374d5557 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new d128c728ae 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new b459dbe96b 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new dcf3d14319 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...]
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 (de22132a01) \ 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 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31100 -> 30904 bytes 04-build_abe-stage1/console.log.xz | Bin 91768 -> 92480 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 236692 -> 237020 bytes 08-build_abe-stage2/console.log.xz | Bin 228248 -> 229520 bytes 09-build_abe-gdb/console.log.xz | Bin 38548 -> 38232 bytes 10-build_abe-qemu/console.log.xz | Bin 32632 -> 32576 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2632 -> 3852 bytes 13-check_regression/console.log.xz | Bin 6012 -> 6140 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare2 | 105 +- 14-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 2634536 -> 2631212 bytes sumfiles/g++.sum | 74 +- sumfiles/gcc.log.xz | Bin 2182976 -> 2187356 bytes sumfiles/gcc.sum | 2399 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 888544 -> 896088 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216840 -> 216888 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437316 -> 437640 bytes sumfiles/libstdc++.sum | 25 +- 37 files changed, 1388 insertions(+), 1359 deletions(-)