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 2a10bca4282a 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 45de8557f27f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards 0454463ba832 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards 949058c360f4 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards cfd6ecccf7c6 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 92f5218f843c 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards 375c696b9f02 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 490b35b0e014 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 9eea6e775e2a 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards e72adad598ad 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards b856c117c280 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 5f6afb469207 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 4c887918c58f 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 3e6133dedcde 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards b04173afbefb 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 856e94fe7779 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards ab8c7df5b724 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards a722e288d49b 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 9d75e0ae3f74 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards bd8e8d8cb1b6 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 7e37f47033f8 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards 874c93321800 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards c557435935af 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 5358f667dbff 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards db244503737a 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 93ed29067ca1 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 7c745c8d7e17 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 73fc28cbb871 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 1e9bf349a003 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards cdacd23979a8 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 3480cfc75117 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 752eebce39df 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 4bf2e0a29324 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 7edd4b6f7747 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 01915941f1c4 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards b13697bed9c6 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 4a8dd1ca247c 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 637d5bb1f8c3 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards fb3e66a31bd5 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 256e0ec25c60 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 4f864f668bbf 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 1939bff4e140 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards f0b498d9f57f 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 560dd825c6ab 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards ac3fbc0d92a8 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 1fd6eb87ff19 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 1647f309a47d 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 7bef72682981 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 4f923f59f79a 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 019c44871c8b 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards b6d91da0d94f 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards d4ec44fc8cfc 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 2d9fd9e35281 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards ae951f1ffe1b 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 357683dea84a 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 9701d4e6cb74 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards cd9faffc05e1 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards a2f7fbd65375 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards d9f21da9bf83 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards e7f1a35e112c 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 98d176fea4d8 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 08f8eeb843d8 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards b94750a92a1c 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards abab124cba0c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards c44dbf542d76 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 55003b2a4b24 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 3406e032c13e 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 0f963bec040f 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards a398ecaf17fc 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards ad12d701423b 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 2ed4e3d6d383 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards 257e6318f309 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 2da90d2cbbb6 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards d519e36770cc 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 9155d2e68441 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 0fd180ac307c 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards e1638bd62ec9 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards b78301c6089b 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards cee563e223bd 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards a5327f367c51 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 811d9781bcdc 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 1ee287007077 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 46a3b73a0b25 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 4203b64349c6 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 9ca968367ac6 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 0343a68be702 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 59ea962a99ac 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards d9e1e5cd602c 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards b36a51a7be75 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 1c245d26aef9 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards ccff34bc4113 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 7750bc557dde 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 2432845cf3a9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards ec2eca1db91a 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards d5d3a583cdc5 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 56806be7fadf 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 661e9550128d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards a0b775abee50 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards 89c88611a776 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards 925598e5b0cc 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 50abdef8b610 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new f901047c8f21 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new 52e0444996ad 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new b81aedecd77b 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new 2450d418af68 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new ab2c4288dadd 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 3d95e02efb84 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new ac6f1397c855 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new a5f5c7d30f54 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new ef6061f4285a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 49570f4b0eca 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 623778448723 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 600216b82b4c 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 5df77aeab9d8 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new d0d0d6cedeff 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new e0f6c14fedcf 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 3d50e5feb1b0 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new e50ee3a154f4 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 1d2b12af5bb2 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new aa03f4ac9261 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 947ce9a55b24 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 9213196d6672 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new ec43f53f6a9b 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new 2e2a5d33a626 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 5fdcfee4f3a2 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 2c0d1a161167 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new e384ed5e948e 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new a0b40388c70f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new a7598fe5edd9 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new fd3e56ea7b18 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new c191a0a960e1 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 3cc9b1a5b5b0 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new d77ea89c90d9 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 88a7938830cf 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new fad208035308 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 7b63b0055e24 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 2f44548d7cf3 194: onsuccess: #1995: 1: Success after linux: 517 commits new b9519588db13 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 7d8c795f4e33 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 1adae27a4930 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 5e39c01b5bad 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 7fa028d5135f 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 97d4c342705a 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new 235357c8df95 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new fcf3130c068e 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new cb379073cce2 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 9b3887f2e815 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new cc13adb43ddc 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 918be15d06c7 206: onsuccess: #2007: 1: Success after gcc: 2 commits new f6865834fda3 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 8418f3b06747 208: onsuccess: #2012: 1: Success after linux: 12 commits new 5ebfa07684cb 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 714a8bfa0641 210: onsuccess: #2017: 1: Success after binutils: 6 commits new aaae9592a652 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 5fdb1cd6734a 212: onsuccess: #2022: 1: Success after linux: 3 commits new e4561eb122c8 213: onsuccess: #2024: 1: Success after binutils: 3 commits new cd7f88a97e2c 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 406147b9b86e 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new c98992d7920f 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new d321b11441ae 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new d6cb50bcffc6 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 663550804432 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 9b91c9838ed8 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 3fdb84c767dc 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 6e6b847c755f 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 90a4e28a5a39 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new f9cef64f4442 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 43133af570a4 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 178173f20338 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new e8a0f0df7189 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 526484112acc 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 1d2f9926dc09 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 3ec5033ee66c 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new f32b5dd01c63 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 83348d72b927 232: onsuccess: #2048: 1: Success after glibc: 2 commits new fffd326994c8 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 5a71fc9c7e31 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 33f7ac9ba207 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 5c62ae000689 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new da7b43a10495 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new f30d4b9fe132 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 838a4133ac21 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new cd33da2f8add 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 10f47fff2d55 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 3dc8a461b74d 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new d24d463593aa 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 6ab1ef930e54 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 1a66e7ebb2fc 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 7d06a378f6bb 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 0a9bb2faec4c 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 613450ab4243 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 535788e9d5b5 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new c615f2c397c3 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new b4b75960a531 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 861cacdccb6f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new f38fd0970a18 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 7433c6610080 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new 3d3e598312b3 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new cd7cd416712b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new 12d513da9c1d 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new bf129ae37c69 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new 56c0fe8bd9e1 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 3146450b6431 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...]

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 (2a10bca4282a) \ 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 1784 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31592 -> 32036 bytes 04-build_abe-stage1/console.log.xz | Bin 91344 -> 91496 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 235176 -> 235064 bytes 08-build_abe-stage2/console.log.xz | Bin 223572 -> 223876 bytes 09-build_abe-gdb/console.log.xz | Bin 39020 -> 39144 bytes 10-build_abe-qemu/console.log.xz | Bin 30624 -> 31676 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2496 -> 2780 bytes 13-check_regression/console.log.xz | Bin 5192 -> 6860 bytes 13-check_regression/results.compare | 31 +- 13-check_regression/results.compare2 | 30 +- 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/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 2652856 -> 2685532 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2271756 -> 2245748 bytes sumfiles/gcc.sum | 2436 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 895224 -> 891304 bytes sumfiles/gfortran.sum | 49 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213848 -> 214040 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427352 -> 430424 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 1432 insertions(+), 1400 deletions(-)