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 08ca244e02 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards edea598973 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards c0759bd5f9 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 1e961b6657 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 69b329ab0a 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 257e7f75bb 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 10d41a2e6f 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards ebd77bbbdf 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards c111b41f48 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards f48668e7bd 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 9b637b7bce 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 59c82552f5 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 4447af5636 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 114f0cbe24 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards c0a5ee964e 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards eb862df7fc 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 3180aaa3e2 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards da5d8d28cd 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards a38a081668 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 17f0bb349e 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 5da4e94d12 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 77a46b9c7a 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 0cf3a54505 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 3045043e58 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 874411c6e5 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 6f828eccc9 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 6ccd72faa1 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 9433b93622 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards fb0d91b28a 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 3437756c5b 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards a58865637e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards f322357658 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 30b14efb99 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 1d8b1af246 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 4042a503ba 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 0160ddfc82 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards dc0f6dd717 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 945d992acc 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 592658d87c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 07091ee804 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 2c291bc94c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards bcf5132f8e 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 75c5009c4c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards d773364dc9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards b8a5eadfcf 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 6810e263f5 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards e61cf39570 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 8bcd2a3cee 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 39e8e3943c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards cad99715b0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards cd957f29a2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards c2fe4fa505 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 0e74ad8bc3 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 068cc4c3a2 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 63956428db 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 541cb4f033 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 323827cf9f 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 74d4a4d1cb 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 7ed84e3bfb 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards cf31e8c93d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 0dec8ddbcc 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 979977805b 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 379c67c4bb 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 0a52ae222c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 04fe04d1b0 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 88c387b527 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 415df147d3 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 343e2ace52 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 25717e7cf6 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards ed2e2a9387 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 8df69a0d68 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards cecf117430 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards e8c7044e10 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 034c35973e 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 01e07357ef 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards eb2bcb20e6 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 23a47eeccd 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards fac43e4415 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 57cac97788 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards fdfc89908b 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 833f87817b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 303bbad820 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 866919f534 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 14f322f1be 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 6b3ecc65b0 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 3948163519 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards dc28e0341d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 962998eafa 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards efa317cbfe 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 57d7f8ee15 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 6a0b8160f3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards c434e0c3c1 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 22820f3b2f 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 5a83255ae6 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards fdfd531741 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 240228d3fc 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 7a0b3704e6 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards a6fddb80d3 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 74912685ef 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards b34b6d6891 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 5b44172e85 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new cc8728a2d7 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 29a3758625 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new c1b1421bd8 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 64cc586cf6 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new d7aa25c051 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new fad431a6cf 290: onsuccess: #2106: 1: Success after gcc: 2 commits new db9042c0ea 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 0bbdade0c6 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new ff33fe92e2 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 8ca7a33ffb 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 7c468e1a81 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new a58b343711 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 85a646db07 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 738eb98198 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 2ee14c7b7d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new c39d6bd39d 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 62ebde1b8b 301: onsuccess: #2118: 1: Success after linux: 16 commits new 49d3080f2c 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new c1f306e9bf 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new d22f6d18d5 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 7fe580a7f9 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 537a867ec5 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new f5c034aa64 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 221e1610b2 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new f2aed25c41 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 464f4d459b 310: onsuccess: #2129: 1: Success after binutils: 4 commits new ca9b586e7c 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 06e8b5ac48 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8345c8e87a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 06671450ca 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new fc7aa9affa 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 7e6a6a95d3 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 3d5bf5e845 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 89035d23ba 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new f3d3e57e89 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 7c04efd818 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 6860334a7c 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new a5d1276d3d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 881673726a 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 5f8f27c9ca 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new e65cc7b87a 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new b4226ce9d1 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new cabd9dd1d4 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new f0deac908c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new d03f2db5a7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new d87d5c445b 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 0222376430 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b99d5790ba 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new b162459284 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 4dda1ee7d0 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new ed4d137627 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 20fa5dc19a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e3a628f371 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 902993d933 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new fd46c731a4 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 2b83277600 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new ee83218be9 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new aadbf75a69 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 897a5c1824 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3ac0ccf5d1 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 1ece9a1aba 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new a1f9b3345b 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 9bf8235947 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new bd648e2b25 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 2259c1d4dc 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new deca9faec7 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 29c31919a1 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 0ea048c8cc 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 4169f56542 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 2642630b40 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 831d01016e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 4162e3088a 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 9bdabe2d10 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 85f60dd9b7 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 531ffdfa0b 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new d1e688b753 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new c2be404568 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new ec61a0be89 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new c780cc1b38 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 2e3cb485ae 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new ac991379b2 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 18c6d606ed 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 97ea2f92aa 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new fb907a9c6f 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 5bc03839ae 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 305a312e7a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 3239b93a1f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 66f05fc692 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new c84e9b38e0 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 024c0dadd6 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new d652ca631d 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 23439d1fad 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 845fabac4c 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new ce1fb4e83d 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 403865317e 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 730eee0011 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new d4fc045827 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 8a51b2d0f5 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new c4184620ba 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 959f686bc5 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 379ead9abc 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 3704d60de9 386: onsuccess: #2207: 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 (08ca244e02) \ 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 1788 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31136 -> 30904 bytes 04-build_abe-stage1/console.log.xz | Bin 91436 -> 91548 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 8900 bytes 07-build_abe-glibc/console.log.xz | Bin 236824 -> 236488 bytes 08-build_abe-stage2/console.log.xz | Bin 228224 -> 228448 bytes 09-build_abe-gdb/console.log.xz | Bin 38548 -> 38212 bytes 10-build_abe-qemu/console.log.xz | Bin 31908 -> 32072 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2776 bytes 13-check_regression/console.log.xz | Bin 6624 -> 6388 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 14 - 13-check_regression/results.compare2 | 47 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 2633792 -> 2643528 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2185500 -> 2194848 bytes sumfiles/gcc.sum | 2390 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 888268 -> 889420 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214416 -> 214284 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435448 -> 437280 bytes sumfiles/libstdc++.sum | 36 +- 40 files changed, 1300 insertions(+), 1377 deletions(-)