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 b771fa633d 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 40a1a5c874 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 96341619be 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 477fa1cab5 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 76381cf9df 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 07ae744992 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 7e04633aac 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 0a3603fd2f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards e29fa63508 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards f545751d44 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards a62be32dea 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards a56ef611b5 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 54e994ae3e 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards d2b50ef89b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 31865922c9 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 4ca4d382ad 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 5369b826b1 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 69801de38e 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards f43600dfef 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 5eab99e53c 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 7692cb388e 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 6d43af8228 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 77223fd572 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards a7ea2034b3 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 048a492995 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 0175f40447 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 7fb0c6193a 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 4224142bae 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 52eef1be6b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 012c760701 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 5c10563371 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 2beeea5e79 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards f092cf3f32 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 812093bc91 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 3d4ec7ba28 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 7ee1460ad9 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 0b08b8f109 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1b0af3e5be 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards d9e0355552 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards ded6b5d63b 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 77e2703d86 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 1a4767027c 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 611ff1027a 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 4d9a676b49 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards fdf3fb89ab 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 1f9d7cdb79 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 33d312e58a 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 61d74fab6d 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 8dd676240f 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 84cadc62f1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 3860db90e7 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards fd767ee082 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards a429f1068a 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 10663e9a31 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 5fac00f2d4 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 6dd26abe3d 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards cd9987bbda 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 05abf545cf 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 16775e417e 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 424b74eb1d 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 21b97b15e5 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards dde1eae8e2 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 27e56ae8fd 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards c3684d0b3f 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 260f4f6420 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 0529d847b3 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 41d683f7b5 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 41fe1c37a9 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 5cd215b1de 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards d54c995c89 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards cc2fa502c8 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards e9e92cd4fa 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 0f63cc7b46 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 0c7499371c 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards d0ca85a1e1 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards d132cb081a 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 74f2885bce 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards e4c2e59992 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 2b615d454b 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards ccde6d8b16 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 58d892973e 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards d3b375d587 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 0dc69a95a3 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards f174c6f62b 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards c19daa4b61 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards c4db2da6e6 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards c1fd2ddc22 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 4eb764fec1 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 8c159469e3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 605e4ca6a3 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 6b76443374 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards cabb7e8966 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 6410b36b63 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 6846055d41 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards 140327cf87 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards 6c6d72b2dc 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 85584c7d1f 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards eeb39420ab 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards aaa2a81584 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 38fa6eb6b8 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards c941efb401 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 00ae8dbf54 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 5518066d3d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new baf3bf86c4 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 25555b712d 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 9f79f9251c 193: onsuccess: #1992: 1: Success after binutils: 151 commits new ad0b5ddc7b 194: onsuccess: #1995: 1: Success after linux: 517 commits new 7f16ee8f7c 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new 61a36465ce 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 8dd1657a37 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 420f6de0d9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 71f7ebb8da 199: onsuccess: #2000: 1: Success after gcc: 5 commits new d5984e1ca5 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new af12ced131 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 296f8bce16 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new 7a96d6d5f8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new e12aa123c2 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new a33b3e8071 205: onsuccess: #2006: 1: Success after gcc: 3 commits new b4b7c6befc 206: onsuccess: #2007: 1: Success after gcc: 2 commits new eddc5b9af7 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 7f52c08444 208: onsuccess: #2012: 1: Success after linux: 12 commits new 9f5cab9586 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 8d501f2460 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 376bea3c46 211: onsuccess: #2020: 1: Success after binutils: 10 commits new e4c06702f1 212: onsuccess: #2022: 1: Success after linux: 3 commits new a8896ed791 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 0cd3ce8f15 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 3dfab5ae47 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 2030665206 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new efa794fbd8 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new a9ab3fd678 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 457f79442d 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 530f709e92 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 0525557cb9 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 685b15bd0c 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 19e1037f04 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 86a63e2286 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 35ece92dd1 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 82cce7704c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new e21fbaae76 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new c77253b874 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 2b52f07bee 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new d318e62018 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new dff3066d45 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 03843739b6 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 7234e945c9 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 9aee585667 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 45cef1cf2c 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new b3d12272ba 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new fc77f53eff 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 5020e8327b 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 632814f5d3 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new a9141efdb5 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 32697a4908 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 623bab7ea3 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 2065ebe0e5 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 099263e99a 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 154f438061 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new f404da0fb0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 01a1ea7120 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 39888b0541 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new b359ae5515 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new d2bc607c77 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new d6d2030fc3 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new a58a63dcde 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new cece3392bc 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 5fae511369 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 9d65628b05 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 78a070f225 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 6cb992c223 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new a47a3f47f6 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 8a3336e973 259: onsuccess: #2075: 1: Success after glibc: 2 commits new c0615c70a7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new cf830e438c 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 4e16cfc0f3 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 8ff448a0a1 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 4378861f2a 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new e4c70bea04 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new c31b6d7374 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new bc58994936 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 94366b3f86 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new bb85b52c6e 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new d43fda5df1 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 1705ccabe9 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new d372083848 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 9f85ce9093 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 5a1840c8d6 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 90f4762f56 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 009e4fddbd 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new d61f7c1282 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 60af7eb096 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new bc4d5a0c7c 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 4df1ed580d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 72b7b7abda 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 60e083ef0b 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 80c0315a31 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new bc04f0ce0c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 1c8ae08759 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 266792f43b 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new b13edd1e4f 287: onsuccess: #2103: 1: Success after gcc: 9 commits new af2b2c037d 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new fe85bcc795 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 36da4db59b 290: onsuccess: #2106: 1: Success after gcc: 2 commits

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 (b771fa633d) \ 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 1808 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31872 -> 31928 bytes 04-build_abe-stage1/console.log.xz | Bin 92136 -> 91884 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8384 bytes 07-build_abe-glibc/console.log.xz | Bin 236996 -> 237088 bytes 08-build_abe-stage2/console.log.xz | Bin 228356 -> 228312 bytes 09-build_abe-gdb/console.log.xz | Bin 39120 -> 39204 bytes 10-build_abe-qemu/console.log.xz | Bin 31088 -> 31132 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2588 -> 2532 bytes 13-check_regression/console.log.xz | Bin 5872 -> 5328 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 34 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 - sumfiles/g++.log.xz | Bin 2667684 -> 2662568 bytes sumfiles/g++.sum | 6 +- sumfiles/gcc.log.xz | Bin 2260716 -> 2275044 bytes sumfiles/gcc.sum | 2269 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 893524 -> 892840 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214016 -> 214080 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431296 -> 435604 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1259 insertions(+), 1310 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions