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 56eedc7dad 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 9fd8b936db 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 394bd3d40d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 235050a35d 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards ed4c9f8743 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 88847e0af9 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards e928f92b42 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 61447184f7 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 31952d46e7 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards be70549697 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards cbb854a6b7 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards b75c967022 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards adef036b97 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 8123ded034 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 7be3f27207 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards ba95a0988b 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards df3176fdc9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 4106f5757c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards ddb2af922c 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 74d8f95cf4 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 1275559f31 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 0e47b016b7 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards be51338283 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 981be569c5 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards efa91ec016 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards bcb1d4cba3 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 1f75fe704c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 9031d14624 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards efe13fea0b 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards ac07927e6c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 4d9cc71fa6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 6bb202dd5a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards ae78ee4700 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 4c9ae08d63 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 2b4d776b21 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 8eba3c7825 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards f44b3143f5 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 6ed20445d8 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 1d766ce57d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 7937a2119b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards fca29ac17f 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 38e1ec4f14 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards e23405b714 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 839c0b0617 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 92cc72b746 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 478faf9666 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards b9ca6484a0 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 4f56cc27c1 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 2352bd12f7 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 44a4f183da 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 7e811c348f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 2435f2ccd8 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e25ca5464d 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 8216ceb682 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards eb1d416617 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 18352d6f07 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards a45c6ae5a8 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 1cd93e84a7 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 5731ccd756 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 4c93c41bba 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards f765fd9ee8 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 817bb60bf8 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards ec084e7d73 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 3aee5ec4df 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 97a8316976 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards e9ce901fac 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards b64704750b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 816eb509e5 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 011a61ec5f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards ab97357dcb 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards d538d81af0 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 5470bef6a6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 11c355b96f 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 0c63f4e0c3 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards db6b04f2a2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 63a143058c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards d3f8996a45 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 5aba65a595 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 527c6352f4 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 22325f3541 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards cb13ad3463 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 16391a3ddb 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 6991905c91 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 6c08097492 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 1061749ac6 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards ad3385337b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards a9d22b4d53 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 6f8c2d6b46 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 2355241d2a 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 29e8594f52 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 0fdad84755 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 92df4163e0 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards e0e940c1c9 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 46e9ba4c52 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards d214f2b11b 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 83b68bada3 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 56c7b693e4 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards fa7f7fb258 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 08bc5cb93c 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards bc4da5b62a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 61c4c52e6a 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 4730190379 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 1e16f4aa70 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 988827bffb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 4912d77c82 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 14518628a7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 883c4bbb02 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new ffc19544b4 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 5afebd2189 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new b91889af5f 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 06041aac5a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 8ab2931bb6 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new ab074430e1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 701a56e8ac 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new cf40d2fe17 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new ffa6286571 287: onsuccess: #2103: 1: Success after gcc: 9 commits new f9635cf324 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 3d68b5a653 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 5530c403c4 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 2cd3a87cee 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 3dab3144da 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 3c08286279 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 2b44788f98 294: onsuccess: #2110: 1: Success after gcc: 17 commits new aedf19a57a 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new b51f7da26a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new a9671bc509 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 479c90895f 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new adb48d06f2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new c3bbec5c43 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 6e5d1e7e70 301: onsuccess: #2118: 1: Success after linux: 16 commits new 6ae9dad1bc 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new dc37b52263 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 9d0c15b53c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new c71631652b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 6514f62902 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 0c29bf4193 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 5872a01556 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 8658e59939 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new c6625bec67 310: onsuccess: #2129: 1: Success after binutils: 4 commits new ddc15f0567 311: onsuccess: #2130: 1: Success after gcc: 4 commits new feadc89cbd 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new e1848c0351 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 4ddbf6764e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 674a96bf67 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 5a99c02876 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new d2e2d897d0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 012adafc8d 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 8d02b991ac 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 7b61852fee 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new c4c4c71954 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 593c6da656 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new ce35131288 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new f205548f71 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 0d38e83c95 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 2f60b3a87d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 23c5afea07 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new f4dde31721 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 3ab007b090 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new fddd424347 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ffc980e0fb 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new db7052e94a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 12c8b29e2a 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 9e705a2135 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 8bcaab3a6f 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 0f0d699c1d 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new b2b4ee206f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 6564558f9e 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 96aebc0841 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 72c585a761 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new d30ed013f6 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 7871016b40 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new e39f8743ea 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 0d18ee9033 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 762b8fb1ed 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new c3ded8017e 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 8c1e7d9046 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new f1da25b218 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 2951687b18 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 03b6b875dc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 4b91a0c70e 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 85fe015faf 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 20c4ab5062 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new dbe1acc45c 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new d08f5091b3 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new a52451e7dd 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 94ed397748 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 83b308a1c7 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 06b0cae56a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 8e74adad57 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new bd0ef2b4ee 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 50f1426006 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 90248795f4 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 1707806d49 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 3393a0f742 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 04d81fe487 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 262ff63bb9 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new d6e6cdbd62 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new b5818ba815 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 33f4b68ba1 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new d10151bd41 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 14135d3d53 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 4bae07c9d4 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 7648b6883f 374: onsuccess: #2194: 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 (56eedc7dad) \ 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 1808 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 36132 -> 31128 bytes 04-build_abe-stage1/console.log.xz | Bin 93156 -> 91784 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8616 bytes 07-build_abe-glibc/console.log.xz | Bin 237420 -> 237412 bytes 08-build_abe-stage2/console.log.xz | Bin 229972 -> 228436 bytes 09-build_abe-gdb/console.log.xz | Bin 43336 -> 38512 bytes 10-build_abe-qemu/console.log.xz | Bin 32500 -> 32108 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3188 -> 2680 bytes 13-check_regression/console.log.xz | Bin 7760 -> 7328 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 44 +- 13-check_regression/results.compare | 4 +- 13-check_regression/results.compare2 | 168 ++- 13-check_regression/results.regressions | 4 +- 14-update_baseline/console.log | 66 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 4 +- sumfiles/g++.log.xz | Bin 2642652 -> 2656784 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2204756 -> 2222284 bytes sumfiles/gcc.sum | 2406 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 904976 -> 897312 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214296 -> 214344 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436504 -> 443996 bytes sumfiles/libstdc++.sum | 37 +- 43 files changed, 1542 insertions(+), 1385 deletions(-)