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 ce0570c277 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 18e479e57d 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards bada1aed8a 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 5ffec53997 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 9aa4826010 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards df4ffa4c63 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards c721a4f98b 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards f165f30fa3 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 39d426f85b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 635e6892ae 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 6a9e44e1a7 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 33c1f96b25 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 5a347838b0 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 6d74511dd9 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 03afff2f2a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards ab317131f5 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards df0164933c 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 1916f8ff38 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 7ccfa1a7fb 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards bb1427bc2a 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards b447940352 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards c87ccee328 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards bdee9718cd 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 96c774a1c7 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 5d16823ccb 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 6664641709 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards e57b7a8d3c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 099cf77e40 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 5f23e3d4e4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 23b7bbf7ea 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards e42fea4d32 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 33c72fe186 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 42d4f26873 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 0bc6bfa868 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 9b5f273c4c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 2b7a2c3a87 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 0f542687fa 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 3c10f0c731 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards e1f5f4bdae 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 765089562a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 4ae6c9dfb1 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards f4fb619911 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards e916d6fc8b 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 02434267e4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 29c2f5016f 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 354757efd2 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 872de83128 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards c324147969 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 937a456fde 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards af444c4b36 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 5475a56389 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 6f76e800ff 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards c8240a3feb 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards d4533113c1 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 17d762e1f1 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 2865f3b67a 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards fdcaa1335e 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards f67d3c195d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 3dc76a8235 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 0ad24e3722 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 4601c1c947 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards a5c6981973 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards d76dafecfb 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 1b61871c2d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 185080b540 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 934316f585 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards b816690c7a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 3859cc56ce 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards f7ba2af839 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards ec52fd8c39 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 9dd89e3872 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards b7cd0b630e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 3f1976570b 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards f1319eda2c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards b63cc6c574 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 9e8658bb7a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards a1fdd3de07 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards fc835152e1 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards c5fb19e521 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 92aaf19841 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards fa4a21194d 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards d723801a1f 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards fac7ccc4e0 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 21f2d17c73 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards f4ad5a83e0 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards a1a2339aeb 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 906d409373 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 933d8ae6cb 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 3558337646 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards d5314c6243 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 05dcdff3d1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards b38a1fa887 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 5b1a825b41 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 65164c6525 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 4e737cd98a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards df07cbb254 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 6395f9c46b 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards c3f15a92bb 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards e9fb507459 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards b178c5f1a0 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 2c273ca4ed 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 63d568f41d 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 154ded014c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 1f63f3e3cb 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new ae7b96fc1b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 04217e5fad 294: onsuccess: #2110: 1: Success after gcc: 17 commits new a3172fbadc 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new dbd788acb6 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 7bfb2063fa 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 6a5c93d970 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new ff450252cd 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 858b263b66 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new b22cfd80d0 301: onsuccess: #2118: 1: Success after linux: 16 commits new 40e07cbdf5 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new d1f887d51a 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new e44bd7f8f9 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new db632e7318 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 5748f3ef0f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new ec4e08fa7d 307: onsuccess: #2124: 1: Success after gcc: 2 commits new e19086f120 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new e68b7ff1ca 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new ffc82b104e 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 31a8476e53 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 64111bfb1e 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 5289922746 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 6117257552 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 6278440b43 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 1ea75993ec 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 61caa922f2 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 9603fd48a9 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new d9d7a74ee6 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 95d8d6511f 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 0af2234670 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 2b49dbfe60 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 1517b32904 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new b239103c0c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 39fe0f4f42 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 786b199732 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new fba95042bc 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 1b42f0802f 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 38d4a3681d 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new c1cbe1002b 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 43ef35828e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new c03435d245 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 6f240957c6 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new fda8e8c921 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 14faa578d2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 32ad497737 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 999087f4ba 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new af0db77dc7 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new dbac76ff8c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 82c20285c4 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 9c441b6491 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 51cbcc2f88 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new d325929487 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 71c635bd1d 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 8f46cc9fe9 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new a5de714b43 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 9744e214a5 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 7bb8981c00 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new df9bf397b5 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 0d2b8fb0f2 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 3115820e47 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new cadae28639 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new a1d8a72d17 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 5b9b63835f 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 746be0e693 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ee2c16945c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 307ac618af 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new cf085ab231 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new e90c56d4ad 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new bf8354f5ef 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 4893cbb0c6 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new e398c384dd 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 61095d793a 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new e23bb6c95b 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new d1e4f3873a 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 50183f203c 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 4df66b2b35 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new ad9f7943e3 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 75263ccc1d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new b46cec0131 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 547132b8c7 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new a133bc1577 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 6d0f2bec05 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new fa85eb4b72 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 367fa887af 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new a3ef106ea4 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 900c7a3823 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 0c59e566d5 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 2b2a55eead 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new cf86edcb9e 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new c024187fe4 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 23c9fb89d0 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new cd950bf5a4 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 1728a8d0cd 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 2474d81b47 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new d5c35f2340 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 0b174dd628 387: onsuccess: #2208: 1: Success after gcc: 2 commits new f0fa81d6a8 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 89883924fd 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new b7e73e6b88 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new d4bd3a00e0 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...]
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 (ce0570c277) \ 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 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30952 -> 30720 bytes 04-build_abe-stage1/console.log.xz | Bin 91040 -> 91588 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 236580 -> 235748 bytes 08-build_abe-stage2/console.log.xz | Bin 228480 -> 228080 bytes 09-build_abe-gdb/console.log.xz | Bin 38308 -> 38156 bytes 10-build_abe-qemu/console.log.xz | Bin 32504 -> 31948 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 3056 bytes 13-check_regression/console.log.xz | Bin 5720 -> 6452 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 39 +- 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2635596 -> 2645872 bytes sumfiles/g++.sum | 39 +- sumfiles/gcc.log.xz | Bin 2215612 -> 2224888 bytes sumfiles/gcc.sum | 2024 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 890736 -> 889500 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214512 -> 214236 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438808 -> 435920 bytes sumfiles/libstdc++.sum | 26 +- 39 files changed, 1151 insertions(+), 1165 deletions(-)