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 6c842f4f59 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 435c31d82e 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 3a4bf55be9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards e03a6442ee 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e98e997d12 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 1aed2f1f9e 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 7dc2c11131 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 422216bd52 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards b1d037d59a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 7b3b77a1be 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 03785b8f06 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards c89eec8b3f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards b7b62ed6a4 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards a2d056110f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 079cb0d983 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 85ce46e7d6 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 88d3b912e2 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 72664b79ec 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards feba6cd4b7 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards ef4d0c7489 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 759b53648d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 5f1a95bb95 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 8221317a8c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards ffcfed9697 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 2dc0bc7f00 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 815b9ad4a7 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 40aa965579 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d5453f4e97 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 1ea4608daa 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 7977b4dd28 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 6be4595c31 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 600310fad0 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0c1929bc36 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 107101cb6e 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 2ba2b9a755 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 2c321e6472 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards c4e4201987 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 338097f4f8 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 1064f3a585 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 5b2a0b2b32 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f22b5e969c 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards c7cea911f8 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards d7785f3eb5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 144fd92bd4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 63b8f2397f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards fcdba547e7 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 36e5de135a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 7b10a1b24c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards eece2b41d8 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 6764ccb533 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 9a9fddfce9 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 36b48a3d58 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 6910372d60 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 0ca8e9afbb 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 0b3b2a7f59 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards a364ff87c7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards b6c0fb8a5d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 675582e8e3 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 924f2ebd55 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards cea98f80f7 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards f8344d9ccd 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards b8cb619577 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards fbe1e83bb2 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 3ad68994b5 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 52de6e8e86 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 8a2361598b 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 0d36126bc0 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 72c55177b3 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards a90373dbf6 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 48b4416400 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 7993633fa8 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards be1edbe023 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 1485be483c 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 557c1eeae1 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 0d8c07ed1b 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 25f3f36f6f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 5cc758082c 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 6888b1113f 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 231d7418db 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards b23e237f1e 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 00b9191c96 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards fbb98a25ee 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 276edc757b 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards b408a9c122 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards a5b8023dfb 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards d0f427ced4 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards f4a5d72353 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards bd58d99680 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards ea5621bc36 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards abdf740172 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 41937fa279 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 1039835a18 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 51839bd901 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards fd44527db6 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 7dce54457a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 21a2fa0bb4 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards bc33abf3b9 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 5d94fc31d7 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 7372a98817 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards d414d3521d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards a1732d6cf7 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 5c0972a6ca 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new ac2c6f2c3d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 46b8d5714d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new a95ee1fa29 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 501897582c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 326a8b8293 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new c04923148f 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 7f8a6fa834 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 1a14d7ca56 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new f8178a17e6 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 1da706d239 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 0b0e00baa4 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 62042e316f 290: onsuccess: #2106: 1: Success after gcc: 2 commits new bd000735c9 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new a3e3689566 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new abd24959bb 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 03d1cd7dfb 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 68ba36ba76 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new c9ed8b3be5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 1fbe86d5f1 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 7077c3d257 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 88e0137bf2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 081eca3503 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 2779a3f494 301: onsuccess: #2118: 1: Success after linux: 16 commits new baf28109fb 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new f5b39884dc 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 861dddf5a2 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 68c3ea877d 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 5315ace778 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 9e5110776d 307: onsuccess: #2124: 1: Success after gcc: 2 commits new b5c4f445c5 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 27134575a0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new b6a7e10b41 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 203213dc51 311: onsuccess: #2130: 1: Success after gcc: 4 commits new fc6dde3baa 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 3d87ae196a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a36a19e80e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new c87aa7495d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 2eba49fc25 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 7bec491f1f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 06970d5c16 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 036cfe5a50 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 2ac81e0c96 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 67237a3046 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new d20d67e309 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 703f2cf581 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 904b52ebc9 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new fc1e50c410 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d961a8b14a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 64f2b5a26f 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 1fcc8444b1 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new f790be27b2 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 1e7be316ac 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 9679f562b5 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new cdc0da8d1a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 2ef24cd6be 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a52ae37bfa 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new e06c8129fd 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 0e65557489 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new d0b47ee62d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new fc20dba488 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 0ca49a870e 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 79b6c9511b 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new ef9d7c1df4 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new d4714c9e6e 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new b8069f386c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new b1826db4a0 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new b92aecd10c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new d4d85940a8 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new d8e597ac4f 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 28670972be 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new da3c2ff076 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 8f343022ae 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 91635bf7a8 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 1a840ea6fe 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 6cfeac3776 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 55c8ea0df7 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new cd4a585241 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new c56f832fa1 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 556c39796f 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new f4aae3b70b 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 5f3e0f30af 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 9bd9b5f7bc 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new ff2cf7b2e1 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new acdf729579 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new cc6d3b197a 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 800a69a86d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 25237d8ca3 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 59117281b1 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new ba30cc08bb 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new de14e3ac5f 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 0fcce08ff3 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 4cd28a0310 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 56d6a0aa1d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new b3cb87b1ac 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 8d532d71b0 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 09656ecfb8 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 9607307f70 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new b2eb9f9313 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 13b7a87e84 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new a2ae2ee67c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 8ae16f97b1 379: onsuccess: #2200: 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 (6c842f4f59) \ 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 1792 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31720 -> 31260 bytes 04-build_abe-stage1/console.log.xz | Bin 91380 -> 91856 bytes 06-build_abe-linux/console.log.xz | Bin 8900 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 237984 -> 235796 bytes 08-build_abe-stage2/console.log.xz | Bin 230488 -> 228920 bytes 09-build_abe-gdb/console.log.xz | Bin 39204 -> 38624 bytes 10-build_abe-qemu/console.log.xz | Bin 32044 -> 31792 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2696 -> 3124 bytes 13-check_regression/console.log.xz | Bin 5544 -> 6496 bytes 13-check_regression/mail-body.txt | 27 - 13-check_regression/results.compare | 10 +- 13-check_regression/results.compare2 | 19 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- sumfiles/g++.log.xz | Bin 2677324 -> 2666272 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2211628 -> 2191752 bytes sumfiles/gcc.sum | 2388 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 895252 -> 890648 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214436 -> 214392 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 445088 -> 441400 bytes sumfiles/libstdc++.sum | 32 +- 40 files changed, 1333 insertions(+), 1394 deletions(-)