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 c09e7caf14 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 827c2b0c4a 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 33e46ea518 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 6e0c0fdf65 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 152b038194 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 24777000d9 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 6ddaf8c87f 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 5636587e3c 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 7998792699 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards f3b957c08f 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 167558afa1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 9805331807 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards e24d50596e 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards ff7afee727 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards da42487f86 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 948b19546b 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards b8516a40b0 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 1b344497ce 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 135e761cf6 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 27f1eff19a 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards dc070932db 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards c3544e694a 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 2972749bd0 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 52ddd51d41 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards a59c59f84c 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 4d62e38f86 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards bc78e2090a 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 9ded26e9ef 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 7fc78f0343 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 29a3e9bfde 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards b5797030e0 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 3e426888ce 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 0cc033d845 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards c4b03ea1f2 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 0821ddf1c3 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 6518e5dfee 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 8e8f72035b 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 81b623957c 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards efb9921400 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 06a39a027d 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 0653d8610f 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 054d35cac9 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards a42507729f 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 2ce068fc3d 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 36f0e09fdd 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards e419f85eaa 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards c6be726d7a 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 1299228406 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 556e682273 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards df92bc2680 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards c9ea1fd2d2 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards f14f6eaf95 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 2fc70c51fc 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards a322eb13c5 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 6d347c39b1 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards add451e222 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards c07d17ab5f 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 4112fa8a80 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 8cce94e076 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 9b3675d312 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 1e07e73543 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards e1f1ee0e6b 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards cc2d4336f9 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 1a6130c4da 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 93c192e24f 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 80cd698642 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 7096a09d34 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 53359a3afe 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 30feb08b85 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards e2cfc90a5c 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards a9c868fce6 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 9d2d1cfae5 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 91ab074cfd 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 49a0cd6ddd 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 3fa745c10e 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards d1685ad4af 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 9acf0801c6 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards c385d3028d 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 4ad567949a 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 9c84336239 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 154d879cbc 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 8e243c2b2a 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards e069249c41 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards 35bc772d76 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards 5fec75e795 194: onsuccess: #1995: 1: Success after linux: 517 commits discards d57707721a 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 9e00ac9493 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards ac936bf203 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 0df5bbb55b 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 3a0a5357c6 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 2dc43d5090 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 66c25bd093 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 7f453060ae 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 05a8f8ff1c 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards f423e986fa 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards d1de31dbb1 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 88f6752b81 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards 5c0c396c40 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 0a611bbcdf 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards c7139f29ba 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 4694728d32 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new d5d3a0f009 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 0783643973 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 4188ac51d1 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 55be853a36 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 19f668374b 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 945e8835ec 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new d642d96c29 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new d31008d675 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new ef78acecc4 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 9ea90b911c 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 8fa6b754fe 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 8f93dc7702 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 0fdf0a663e 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new bf3eee3855 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 1b399ea745 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 548c5ac866 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 87f4ee76a7 194: onsuccess: #1995: 1: Success after linux: 517 commits new 19da4908f9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new eaafaa361d 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new d06d39fd35 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new c13a03e882 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new b767dc9f78 199: onsuccess: #2000: 1: Success after gcc: 5 commits new bbef22de68 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 8a403136e8 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new b085b2b391 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new b7f15ed9d7 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 6f3bac0a92 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 2cf12c31ed 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 179d08f86f 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 9533d57cd9 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 96d8466c70 208: onsuccess: #2012: 1: Success after linux: 12 commits new 7aeaf5ce91 209: onsuccess: #2014: 1: Success after binutils: 12 commits new bcab7ba643 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 14a2ae527e 211: onsuccess: #2020: 1: Success after binutils: 10 commits new b4fc6c8ae6 212: onsuccess: #2022: 1: Success after linux: 3 commits new df2c96f47b 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 75ae569942 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 3301dc8637 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new b19e0830ff 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 69580e1a4f 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new edd4a95232 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 7ab772c098 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 0b0163c3ac 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 813d58582c 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 9c16d44d10 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new a1d3fb0484 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new f1b1bb695f 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 4ee36b1b48 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 2e7234ece8 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 139cefe5ac 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new b89f4e48c1 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 44e64b103f 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 8afa46f0b6 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new cd41859a27 231: onsuccess: #2047: 1: Success after gcc: 4 commits new c63b1e627b 232: onsuccess: #2048: 1: Success after glibc: 2 commits new c0f9b22c71 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new e0cf652714 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 8b2b039954 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new be930d4118 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 7cd9281eb2 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 0b5edbb4b7 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 35795073c7 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new df9c685d81 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 989c5fd60f 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 724452824d 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 8fe706110b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new abb873d08b 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 2ceff2262d 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new ec3f8c61b6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 472a61c287 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 0de9c0fbb7 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 7fb7f70264 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new a77ba38ecb 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 02b85b10b5 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 71cc80fa26 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new f30133687f 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new a0a6f5e455 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new e750d4b1b9 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 3421e32391 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new eda0056fc4 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 09b2c0e5cc 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new fe9acb4f83 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 0bb461ff1b 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 0bd03a946b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new b03e2e8530 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 6e49e378d5 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new df40bc8ae7 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new c9805ae443 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 0d8b2946e8 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new a8a1134fa8 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new e137fe3944 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 1d1aa8c7e2 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 2dd230802a 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new b58ac2a92a 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new ee62955b50 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 4db0307dc2 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 27e76db652 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new b05b019be1 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 82d289328f 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new d5983d2291 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 135e92d374 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 53f2a2852c 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 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 (c09e7caf14) \ 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 1736 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31936 -> 32940 bytes 04-build_abe-stage1/console.log.xz | Bin 91932 -> 93048 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 237228 -> 238908 bytes 08-build_abe-stage2/console.log.xz | Bin 228604 -> 230256 bytes 09-build_abe-gdb/console.log.xz | Bin 39312 -> 39960 bytes 10-build_abe-qemu/console.log.xz | Bin 31204 -> 31440 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3920 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2484 -> 2820 bytes 13-check_regression/console.log.xz | Bin 6136 -> 6132 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 11 + 13-check_regression/mail-body.txt | 97 +- 13-check_regression/results.compare | 34 +- 13-check_regression/results.compare2 | 52 +- 13-check_regression/results.regressions | 45 + 14-update_baseline/console.log | 64 +- 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 | 99 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 45 + sumfiles/g++.log.xz | Bin 2654688 -> 2667848 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2247428 -> 2275796 bytes sumfiles/gcc.sum | 2637 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 896332 -> 904568 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213908 -> 214072 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436804 -> 445024 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 1642 insertions(+), 1531 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