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 3828e3f74c 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards be8a03f2d1 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards ce909f2ada 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 2be95a21ed 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards fdcc68f926 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards ce235e00e4 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 9aab432352 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards ada6acf254 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 60ba6eab94 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards f5d0ba3cc7 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 0adbe31ecb 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards dfbd03c4d4 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 698517cfb0 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards d290bce425 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards cf7c1f06b6 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards ea0e5c3acf 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 149515ae3d 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards e8d19dbce5 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 872bb94437 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 16b75e2b2a 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards b6fc2d2ddb 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 6e49538fb9 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 5e191699d6 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 33b2d6bc05 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 06b0b206fe 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards ec1068ace6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 12618e75b7 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 70dfc4a2cc 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards d298a6c2cf 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 66396f882f 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards b0bf97e0c1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards d3e2f26ac8 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards a9985109fd 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 21fa482b7b 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards da56a5f486 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards a1a39f844b 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards c22039cf26 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 1a94b66bb4 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 9fbdd43dc7 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 30d65cdf34 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards bcaaae492d 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 9c4ff35d1b 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards aba8b61b95 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 85d85f1f57 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards ecf0982608 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 10fc84d8ee 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards afe8a382f6 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 096a57a2a7 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards b86da8802c 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 61b47b7c84 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards d0a60ac3c6 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 84b4b74c13 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 25a5dc92ae 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards c1d7f352b7 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 516d443fdf 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards fd21fbcd86 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards b76094c25f 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 1a4ec886a0 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 15776fc185 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 0b0e298149 212: onsuccess: #2022: 1: Success after linux: 3 commits discards f841ec7389 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards d901fa9c3b 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 7fb1aa3a29 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards cc5621d600 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 53ccd61d35 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards aa82b71e40 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 2398218bf2 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 0554a04829 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards f66044f096 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 5fc8ad263c 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 3c9d145eb9 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 60784fced8 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 4264845715 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 5f4c3a71dc 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards ee88e49476 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 56ce8917ba 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards 1e73e382e9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards bf09e9b300 194: onsuccess: #1995: 1: Success after linux: 517 commits discards ee7d8ee0e4 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 14214b807a 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 16643115f2 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 9f4c47a1f6 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 312ff4dbd4 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 5ec050bbaf 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 9a6906f807 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards a9bc85370f 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 55d6e773bf 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 5f379df827 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards a92139e09f 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 254ec6da95 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards 86cff43bde 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 0318ed404a 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 22c51835f4 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards ffb94c8f24 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards eedfbfee4f 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards ea343d0ed4 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 1951bca640 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards d0a5fc7d54 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 758e54a6a7 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 928b5b7454 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 645e354b34 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 8b8d9570ae 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 69bcf1ee2d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new f921f96de2 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new fc11752843 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new ce3d065537 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new ed12d14367 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new a07b32730d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 3bad7a1cf5 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 50fe4065d0 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new cc4b9a27b6 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new d81154db4f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new dffaa715f2 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 146a8dd7fe 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 467bd81d32 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new ed718c1e2d 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new e12b9d9a5c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 4b2669510a 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 7465c06ecb 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 18ce9d648d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 8b26273970 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new 7150c74c99 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new f09e3f4cc3 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 3c8cd5432f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 4a860b7853 194: onsuccess: #1995: 1: Success after linux: 517 commits new 8d71f7511e 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new 78e073b214 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 3b5a075c45 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new ea6ae3509c 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 372aae537e 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 5368ee5620 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 91856bc522 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 0a6138f00b 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new d49a584204 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 9ac7c072c1 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 06a6f98afe 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 362965dc07 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 6a2935b58b 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 3c180fd3df 208: onsuccess: #2012: 1: Success after linux: 12 commits new ceb48cd54f 209: onsuccess: #2014: 1: Success after binutils: 12 commits new e29fdeaf62 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 69a1ec092b 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 895bc1529f 212: onsuccess: #2022: 1: Success after linux: 3 commits new 123327233a 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 4896b649ed 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 78c8bf457f 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 3d02e528d2 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 2c4b28a1cc 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 7276a8af69 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 62f1207e6f 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new e7455fafaa 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new ea6ed4d204 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new d8fb52eafa 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 396ba9b20b 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 75ccac3a8f 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 4e797f90c9 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 6f7c94c1d0 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new e8ae9ddbed 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 248463e71c 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 29dbeaa965 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new fa0206f699 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 5f7c903750 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 3c7f44932f 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 0208d93219 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 7a749ad775 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new e74e25bf70 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 2ca944e76c 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 0372d80dfe 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 283ed94eb3 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 892dbe1795 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new db59d34d2c 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new b991ee420a 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 4d0f5a9c45 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 1791d9f768 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 4e8c7997ff 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 7cff4d45d4 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 442ca97846 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new c4814d3098 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 02e86d3fa2 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 8b3ffafedb 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 9c5e5fe4ce 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new a5f9618d1f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 1a2d8fdb5d 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new e70ca85d4b 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 24301c141f 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 30fca8e9e8 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 59b6f0278c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 04db8febcf 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 22f8916dd7 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 50d58cb04f 259: onsuccess: #2075: 1: Success after glibc: 2 commits new ea83eb851f 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new fc98c39982 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 16b3fd00d8 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 76d7174664 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 85a263ba36 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 643ec2de2b 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 0cd9ef8054 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new da9968ac20 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new ec9a0834d6 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 8af1a01a24 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 981215969a 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 427ab69a44 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 243b1b55d2 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...]

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 (3828e3f74c) \ 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 1788 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2812 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 32256 -> 32568 bytes 04-build_abe-stage1/console.log.xz | Bin 92892 -> 93588 bytes 06-build_abe-linux/console.log.xz | Bin 8568 -> 8588 bytes 07-build_abe-glibc/console.log.xz | Bin 237044 -> 236960 bytes 08-build_abe-stage2/console.log.xz | Bin 226580 -> 225820 bytes 09-build_abe-gdb/console.log.xz | Bin 39504 -> 39564 bytes 10-build_abe-qemu/console.log.xz | Bin 31704 -> 31416 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3128 -> 3104 bytes 13-check_regression/console.log.xz | Bin 6556 -> 6716 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 61 +- 13-check_regression/results.regressions | 20 +- 14-update_baseline/console.log | 70 +- 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 | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 20 +- sumfiles/g++.log.xz | Bin 2659500 -> 2661204 bytes sumfiles/g++.sum | 20 +- sumfiles/gcc.log.xz | Bin 2271968 -> 2276408 bytes sumfiles/gcc.sum | 2074 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 898540 -> 902896 bytes sumfiles/gfortran.sum | 61 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214056 -> 214000 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438172 -> 437472 bytes sumfiles/libstdc++.sum | 6 +- 41 files changed, 1339 insertions(+), 1191 deletions(-)