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 a977f2b46e 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards aff771b461 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 089b781634 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 4a342ab5e2 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards b249595f86 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 2693a40854 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 8bc4b08049 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards e3cb43811e 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards e16afdde0e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 980a41b7ca 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards ff95f8e2d3 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 83df08b678 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 313d2ede3d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 266d02e526 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 8e0a9ffbe0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 83d8900889 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards d14909de0e 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 44ab5483b1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards f335998590 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards b7ac50a573 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 08bb61b1a9 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards de01bcf28d 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 9cf60a095d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards c89716d056 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 70aed267c5 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards ef6354e64e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 46c671f1bb 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 01525088bd 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards e3c8587546 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d18c738d47 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards aa896c09dc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 6ef7614923 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards d82972d28f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 8a2db9d400 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards a6009ba2de 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 849c92a30d 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards c82da63f2f 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards db85138b62 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 9d449d44d3 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards e59aef22e6 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 430385b99e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards e502ae275b 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards e20d2f9b91 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 72e3d3d1b3 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 60973efba2 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 16eb5b73dc 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 6a695ff5b1 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards e2e1174d07 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 2b6914644e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 2c2abadb41 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 67c85eb561 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 746403d77e 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 4c7794b206 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 7e48d73740 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards e22e3a5feb 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards df83083ce9 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8de862b4b3 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 75c85a2270 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 6635ec04d7 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 226c3bac75 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 8853da5227 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 007a02a593 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 94c69e35ce 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 381099e3da 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 6db225ba6f 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards c1efae1e5a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 6756fe00ae 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards ab33e67079 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards be30d98236 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 5c87742a95 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 5e3cd088aa 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 100c5bed58 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 48303af927 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards a1abd52b19 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 05c00e63b4 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards dcf9aedd8f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 717769314e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 9254bb2a95 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 8e0f2a2caa 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 117ecdfa9e 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 51d25599d2 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 302776fc4c 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards a2331b137e 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 1a1dff1124 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 38d64db621 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 35cbb461b3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards a48e5bb469 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards d398c4d647 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 29a7bd5595 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 126494ab4d 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards fdc2efa2c2 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 8c37c81ba6 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 990dbf57a5 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 7152201260 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards a06a6d2106 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 662e5e86c2 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 06fd1ebc5b 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 5efc5f3799 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 71e1f028df 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 5c877888d6 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards b1c2a3c4ef 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new a1d4689ad7 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 182123ac73 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new ab9782927f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 4c08bd6d86 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new f9adbeb3bc 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 32eaa453a0 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 95dd9c1ded 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 7cf00488cc 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 7ede9cd3f0 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new ea970cfc85 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 57ca50d388 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 199ee622c0 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new dd37b22099 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 876641891b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 810adeafeb 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 4334d32e0c 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 6b3e33ff52 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new a6a8734760 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 96ccd65748 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 26603dda80 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 045e89fef1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 593c0a64cd 301: onsuccess: #2118: 1: Success after linux: 16 commits new 5c56d55ae6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new a0073e3fb3 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 53edd470ee 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 4e5a4941a7 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 4270c2a60f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 86e3e99bb1 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 8895d3ce04 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 84d2b31de3 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new bd61d7b1b7 310: onsuccess: #2129: 1: Success after binutils: 4 commits new bd1b209548 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 9bd6fbec2b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 7cf5a77e01 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 787482c853 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 537688b0ee 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 1dd8648e4a 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 7d8f3830a0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 7d3b0703bc 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 690b94b9f4 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new e4f78463e0 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new c0ae260f12 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new ccda61275f 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 1d6cfb50a0 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 6aacce8e84 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 8ac0299e4b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f686e53b8b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new c3251414fc 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new a8db67d6bd 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new bfbfd463f0 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 5779ff90a0 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 8705db7dbd 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 4446099b4d 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new aa473eb93d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new f5cd689d63 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5fe0743411 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 70041e930a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new cb122dd145 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f7e8e11215 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 8dfc42b6c1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 6eb17ad455 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 448f92fef6 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 7bc8e70a3c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 222ce5d2cf 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 2b7492e36c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new e4b53f1aaa 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 2f54736582 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 19ade12fb0 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new f601e666aa 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 9b8e7d3357 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 2a6e299461 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 6fe4bd4b75 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new e641566c61 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 2d62aa5984 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new a0174804bb 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 2feb7bcc55 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new c17a57e401 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 3e6e2326a6 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 6b796cb172 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 5e6248db39 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 71fd849bd0 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 4949f4f7fa 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 71e26698b4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 2e54ac205c 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 957a2b4eb8 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 73c1e5f346 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 7c0aa9cf7f 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new a130b75a5d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 4f9768ea90 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 90c550d02b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 76365fe755 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new ece08773cf 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 7ea70827dc 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 03560cb54d 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new ff1e1f42cc 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new d0418474eb 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 6ead0c1802 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 757594f9d7 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new c47be7da6c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 7224520f29 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new e751951428 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 5730051ef8 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-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 (a977f2b46e) \ 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 1812 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 30856 -> 30976 bytes 04-build_abe-stage1/console.log.xz | Bin 91704 -> 91656 bytes 06-build_abe-linux/console.log.xz | Bin 8980 -> 9064 bytes 07-build_abe-glibc/console.log.xz | Bin 235844 -> 236528 bytes 08-build_abe-stage2/console.log.xz | Bin 227452 -> 228720 bytes 09-build_abe-gdb/console.log.xz | Bin 38112 -> 38264 bytes 10-build_abe-qemu/console.log.xz | Bin 31800 -> 31852 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2632 -> 2644 bytes 13-check_regression/console.log.xz | Bin 5728 -> 5100 bytes 13-check_regression/results.compare | 12 +- 13-check_regression/results.compare2 | 34 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- sumfiles/g++.log.xz | Bin 2667840 -> 2635612 bytes sumfiles/g++.sum | 34 +- sumfiles/gcc.log.xz | Bin 2196680 -> 2207848 bytes sumfiles/gcc.sum | 2510 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 893752 -> 892704 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214336 -> 214464 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442836 -> 436188 bytes sumfiles/libstdc++.sum | 25 +- 35 files changed, 1370 insertions(+), 1379 deletions(-)