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 5fae16292e 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards a30f710c06 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards bea78b657e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards c05d73779e 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards d2355dd5f4 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards da9bdbe0db 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards c0d08f25f0 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 3396ec6c1f 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 7f14c038ed 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards cb0b5811a2 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 6e6728c61c 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 6b3d294ec9 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 809dbd7c69 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards ce31a5113b 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 4383c8d20a 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 55846e2209 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 1998b6f57b 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 7446dc5772 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards e703c8d93d 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 835684e141 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 3aa942344a 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 10b6e4ef9f 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 28bd3570c5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 6efdb29a3c 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards d318940ace 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 2494a5ba26 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 41b71a8568 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards d6f3e2d2cc 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards b89db8996b 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards c9b778453e 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 27c73b14ab 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 8a98088ba9 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 0fe2dde698 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards cd5a146acc 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 08faf3dd54 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 1ee4c9b276 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards dc6631b278 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 2a09e7031c 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 4c440e49a8 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards c6042fb4b8 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 02de07786e 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 0c4a0824d9 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards ba1884e455 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards ad4ef76294 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 6317e49b44 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 9455bd1cfa 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 90a62e453d 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards bb918a469d 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards fe8319c7c9 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards d9946e9854 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards cfcf011bd7 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards b3aefca573 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards e753215728 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 1c063e5385 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards fbb6c68374 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 508e8238c6 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards f4fc873f36 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 81d5b1a1e7 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards ab520df3ae 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 13ecc739e0 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 5df2303592 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards cf13389ce4 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 274b66be3f 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 100cb2fd7a 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards d0343a4ed7 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 86e47f1aa3 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards c570e2a977 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards 2fc1224888 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 35d59e9c8b 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards a144254466 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards f18b5afc85 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 8fa33c7366 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 3ccde163a0 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 942dbd8de2 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards c0d942662e 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards a16152e7ae 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards 9ac33db9d8 194: onsuccess: #1995: 1: Success after linux: 517 commits discards e6bdfb2a4e 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 1383c26d2a 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 484448218c 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 32c8e46011 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 34d5ead783 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards bb956a5284 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 6cb8507496 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 61619b7e41 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 5bcb00a336 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards e11eddef67 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 8482b4a3ad 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 766075cd84 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards 51e8e5c776 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards b1d3daa7e5 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 239a52844f 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards c2fc1b9d6a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards efc703902a 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 21c2c9d036 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 8891aef6ea 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 4f466f198b 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards cadc94833e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 1bf8622397 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards f10c36ea6d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 980837cac2 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 237d40a283 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 645e354b34 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 928b5b7454 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 758e54a6a7 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new d0a5fc7d54 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 1951bca640 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new ea343d0ed4 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new eedfbfee4f 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new ffb94c8f24 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 22c51835f4 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 0318ed404a 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 86cff43bde 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 254ec6da95 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new a92139e09f 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 5f379df827 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 55d6e773bf 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new a9bc85370f 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 9a6906f807 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 5ec050bbaf 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 312ff4dbd4 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 9f4c47a1f6 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new 16643115f2 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 14214b807a 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new ee7d8ee0e4 193: onsuccess: #1992: 1: Success after binutils: 151 commits new bf09e9b300 194: onsuccess: #1995: 1: Success after linux: 517 commits new 1e73e382e9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new 56ce8917ba 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new ee88e49476 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 5f4c3a71dc 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 4264845715 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 60784fced8 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 3c9d145eb9 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 5fc8ad263c 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new f66044f096 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 0554a04829 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 2398218bf2 205: onsuccess: #2006: 1: Success after gcc: 3 commits new aa82b71e40 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 53ccd61d35 207: onsuccess: #2010: 1: Success after gcc: 4 commits new cc5621d600 208: onsuccess: #2012: 1: Success after linux: 12 commits new 7fb1aa3a29 209: onsuccess: #2014: 1: Success after binutils: 12 commits new d901fa9c3b 210: onsuccess: #2017: 1: Success after binutils: 6 commits new f841ec7389 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 0b0e298149 212: onsuccess: #2022: 1: Success after linux: 3 commits new 15776fc185 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 1a4ec886a0 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new b76094c25f 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new fd21fbcd86 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 516d443fdf 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new c1d7f352b7 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 25a5dc92ae 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 84b4b74c13 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new d0a60ac3c6 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 61b47b7c84 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new b86da8802c 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 096a57a2a7 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new afe8a382f6 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 10fc84d8ee 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new ecf0982608 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 85d85f1f57 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new aba8b61b95 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 9c4ff35d1b 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new bcaaae492d 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 30d65cdf34 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 9fbdd43dc7 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 1a94b66bb4 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new c22039cf26 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new a1a39f844b 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new da56a5f486 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 21fa482b7b 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new a9985109fd 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new d3e2f26ac8 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new b0bf97e0c1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 66396f882f 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new d298a6c2cf 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 70dfc4a2cc 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 12618e75b7 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new ec1068ace6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 06b0b206fe 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 33b2d6bc05 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 5e191699d6 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 6e49538fb9 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new b6fc2d2ddb 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 16b75e2b2a 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 872bb94437 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new e8d19dbce5 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 149515ae3d 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new ea0e5c3acf 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new cf7c1f06b6 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new d290bce425 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 698517cfb0 259: onsuccess: #2075: 1: Success after glibc: 2 commits new dfbd03c4d4 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 0adbe31ecb 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new f5d0ba3cc7 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 60ba6eab94 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new ada6acf254 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 9aab432352 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new ce235e00e4 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new fdcc68f926 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 2be95a21ed 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new ce909f2ada 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new be8a03f2d1 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 3828e3f74c 271: onsuccess: #2087: 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 (5fae16292e) \ 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 1820 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2812 bytes 03-build_abe-binutils/console.log.xz | Bin 32008 -> 32256 bytes 04-build_abe-stage1/console.log.xz | Bin 92092 -> 92892 bytes 06-build_abe-linux/console.log.xz | Bin 9560 -> 8568 bytes 07-build_abe-glibc/console.log.xz | Bin 238692 -> 237044 bytes 08-build_abe-stage2/console.log.xz | Bin 228308 -> 226580 bytes 09-build_abe-gdb/console.log.xz | Bin 39720 -> 39504 bytes 10-build_abe-qemu/console.log.xz | Bin 31564 -> 31704 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3932 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2544 -> 3128 bytes 13-check_regression/console.log.xz | Bin 6248 -> 6556 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 67 +- 13-check_regression/results.compare | 39 +- 13-check_regression/results.compare2 | 27 +- 13-check_regression/results.regressions | 40 + 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 69 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 40 + sumfiles/g++.log.xz | Bin 2688920 -> 2659500 bytes sumfiles/g++.sum | 30 +- sumfiles/gcc.log.xz | Bin 2237684 -> 2271968 bytes sumfiles/gcc.sum | 2378 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 896552 -> 898540 bytes sumfiles/gfortran.sum | 66 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214132 -> 214056 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439900 -> 438172 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 1518 insertions(+), 1375 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions