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 36da4db59b 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards fe85bcc795 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards af2b2c037d 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards b13edd1e4f 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 266792f43b 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 1c8ae08759 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards bc04f0ce0c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 80c0315a31 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 60e083ef0b 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 72b7b7abda 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 4df1ed580d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards bc4d5a0c7c 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 60af7eb096 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards d61f7c1282 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 009e4fddbd 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 90f4762f56 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 5a1840c8d6 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 9f85ce9093 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards d372083848 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 1705ccabe9 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards d43fda5df1 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards bb85b52c6e 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 94366b3f86 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards bc58994936 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards c31b6d7374 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards e4c70bea04 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 4378861f2a 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 8ff448a0a1 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 4e16cfc0f3 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards cf830e438c 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards c0615c70a7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 8a3336e973 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards a47a3f47f6 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 6cb992c223 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 78a070f225 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 9d65628b05 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 5fae511369 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards cece3392bc 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards a58a63dcde 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards d6d2030fc3 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards d2bc607c77 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards b359ae5515 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 39888b0541 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 01a1ea7120 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards f404da0fb0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 154f438061 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 099263e99a 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 2065ebe0e5 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 623bab7ea3 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 32697a4908 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards a9141efdb5 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 632814f5d3 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 5020e8327b 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards fc77f53eff 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards b3d12272ba 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 45cef1cf2c 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 9aee585667 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 7234e945c9 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 03843739b6 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards dff3066d45 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards d318e62018 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 2b52f07bee 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards c77253b874 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards e21fbaae76 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 82cce7704c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 35ece92dd1 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 86a63e2286 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 19e1037f04 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 685b15bd0c 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 0525557cb9 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 530f709e92 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 457f79442d 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards a9ab3fd678 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards efa794fbd8 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 2030665206 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 3dfab5ae47 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 0cd3ce8f15 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards a8896ed791 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards e4c06702f1 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 376bea3c46 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 8d501f2460 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 9f5cab9586 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 7f52c08444 208: onsuccess: #2012: 1: Success after linux: 12 commits discards eddc5b9af7 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards b4b7c6befc 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards a33b3e8071 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards e12aa123c2 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards 7a96d6d5f8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 296f8bce16 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards af12ced131 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards d5984e1ca5 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 71f7ebb8da 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 420f6de0d9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 8dd1657a37 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 61a36465ce 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards 7f16ee8f7c 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards ad0b5ddc7b 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 9f79f9251c 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 25555b712d 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards baf3bf86c4 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 5518066d3d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new 9376a2c67f 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new 95ed9d028c 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new d5893cb098 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 1f1f5329cd 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 3a93c968a4 194: onsuccess: #1995: 1: Success after linux: 517 commits new b2a92e2710 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new 1300231db5 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 6d276b87ba 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 24fd3d3b7d 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 96ac76cce0 199: onsuccess: #2000: 1: Success after gcc: 5 commits new dab882cd89 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 1cad08d55f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new b5b4b50fd8 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new f247776b16 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 82a1c24f47 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 3c9878bfd1 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 77dc157e1d 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 8f9e712771 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 7a37b45199 208: onsuccess: #2012: 1: Success after linux: 12 commits new 508277ad9e 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 9b46167465 210: onsuccess: #2017: 1: Success after binutils: 6 commits new d863a56981 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 0c0f46d36b 212: onsuccess: #2022: 1: Success after linux: 3 commits new 25e153f47b 213: onsuccess: #2024: 1: Success after binutils: 3 commits new d17efb19d3 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 4716e32472 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 30144a6839 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 4dd7907d8f 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new f7fe8eec6e 218: onsuccess: #2030: 1: Success after gcc: 5 commits new e2bf810f56 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new cddaf97f41 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 28214a22c5 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 9d00347741 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 7c87edb67e 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new c82d2a7a24 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 7f9f218d54 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 540ce57eea 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new cd37a24062 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 3603185508 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 135ae6e12e 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 9bd5e53aab 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new ed247e2330 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 41ad337291 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 5a6a929e19 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 17a2e78022 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 2b2b8df41e 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 350421f554 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 82990e61b8 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 34a3174c35 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 756c2eedf1 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new fdc028e6be 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 21b196f635 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new bc61891751 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 4eb9bba7cc 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new da856429e1 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new bccf6058b1 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 0d0a186524 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 34c12f7d31 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 6bb7275de4 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 74a57c0825 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 809faae2b3 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new cb8d9d0460 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new defa00a05f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 38578e9aed 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 0cd4fc1880 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 443cf6ffe9 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 3983586091 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 21f4f0423d 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new aab799a331 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new c72129466a 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 95ecd84f3f 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new dbd6d81f02 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new bef18d6bc1 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new faf49de787 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 11fe4cf067 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 0d05d52a14 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 2ab75e1c4e 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new ade5e930c7 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 0db60314c2 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 3422dbfce2 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 2e4556383e 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new b81a052ccd 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 991edf2ab6 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 0a55f950d4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 5a4b6c12cd 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new e9be39a25a 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 1faf6851f7 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 3755d826ea 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 8afb89f219 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new b6659f57e7 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 08fa83353f 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new d2addd2f46 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 6056dda4af 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new b74ac0bb1a 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 249b97c51e 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 372f853a4e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new e3d6ddb665 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new f2699d852a 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 15946e0900 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 88c4775ff4 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new ade4472a24 290: onsuccess: #2106: 1: Success after gcc: 2 commits new a2d348b46c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 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 (36da4db59b) \ 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 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31928 -> 31972 bytes 04-build_abe-stage1/console.log.xz | Bin 91884 -> 92448 bytes 06-build_abe-linux/console.log.xz | Bin 8384 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 237088 -> 236928 bytes 08-build_abe-stage2/console.log.xz | Bin 228312 -> 229288 bytes 09-build_abe-gdb/console.log.xz | Bin 39204 -> 39308 bytes 10-build_abe-qemu/console.log.xz | Bin 31132 -> 31640 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2532 -> 3344 bytes 13-check_regression/console.log.xz | Bin 5328 -> 5432 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 27 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 2662568 -> 2687012 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2275044 -> 2242420 bytes sumfiles/gcc.sum | 2252 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 892840 -> 899452 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214080 -> 214060 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435604 -> 443540 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1196 insertions(+), 1277 deletions(-)