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 59acff14eb 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 3de2f3e6bc 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 640378b4ba 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards fcfabfab77 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 480f061fab 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards a70ec0bb84 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards b43277de90 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 74d208debc 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards fcda4aaeb3 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards fee0444c36 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards f7ee8dc3b1 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards cd3fc6e4a0 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 2939cfb281 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards e48ed5e1ac 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards b89789c506 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 5e2504f847 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 23e4b39b81 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 1355b1b2fd 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards e7650f7636 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 84d5ae3efd 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 82c50a5efe 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards beb4e62c50 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 77c1480688 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards f56a45175d 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards a8bdcf5005 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 8f0f3c6208 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards daacb9b884 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 2fd13a0c5c 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 0f9f7b4af1 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards d5f9d8edc6 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards a6361b5b25 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards eb14b1755b 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 76f9105675 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 42a5972e58 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 889e280200 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards c370461c51 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 1cfd656395 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 89b6fe6fc8 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 0e02ce9f88 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 53e007a93e 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards e5d5e449c5 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 3f20765119 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards dc2f9c458a 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 530984b816 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 8d11cfe8ab 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards b28bae6ee1 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 9c37f635c6 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 316df54c3b 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards e447bd3c20 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 0668d99ba5 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 101b34706f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards e1d228311e 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards f590d46226 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards effe530c5a 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards a123537d3c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 8410c13acd 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 8744cf4d5a 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 5d12bda479 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 4c12a228fa 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 24f10b447f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 08e1b379f5 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards a4b9e86fa1 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 9f7e10d959 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards b8d961fa14 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards a34bc3a6a5 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards a6ea171229 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 9b1a52229c 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards f11988e67e 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards a58b6e68ed 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards c0ccabb558 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards cd8b67eca5 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards ac20b7684d 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards fc40a722b2 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards d46a6c1bea 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards ae1e7799d3 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards caee5be0f3 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 04126c66ad 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 86e0c42b18 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards f467e9aaf1 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards af313813e4 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 5fc438b09a 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards d4071f86b1 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 9837755ceb 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 94ad69a00d 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 62823d508e 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 480b19813b 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 31657aa051 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 352d5fbd88 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 88b1b093a5 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards c30a539dad 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards a1f0457206 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 77dff4de4c 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 9d86cc7235 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 763dd0a374 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards bc19fed181 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 8e1e60a571 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 84ef9bf938 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 29b00b21b5 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards 61f4352e13 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards 123f452c61 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 4f8dd46d3f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new f731fa56aa 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 564459f80a 194: onsuccess: #1995: 1: Success after linux: 517 commits new b4fe47e4c1 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new 98c5f29f7c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new a9807ee6f2 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new c2c2e2c0fe 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 638dd170be 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 9d496026c1 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 72f9236e2e 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new c1e300c145 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new 146391d085 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 40e5569019 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 9305fc3a3e 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 9998933759 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 1d9bbe683b 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 87372d2e8f 208: onsuccess: #2012: 1: Success after linux: 12 commits new 5003e0d18f 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 6d9fab0acd 210: onsuccess: #2017: 1: Success after binutils: 6 commits new b242fbe1e4 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 2c99830b84 212: onsuccess: #2022: 1: Success after linux: 3 commits new ecf207c269 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 7dba90bf85 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 5e68ff9a40 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 050dc3552f 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 7677bf1a3e 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new ea9e1975b3 218: onsuccess: #2030: 1: Success after gcc: 5 commits new f031685df2 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 66f2fc2f0d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 47fe5152b0 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 33da9b6dd0 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 76b5313cfa 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new b8724a6a53 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new f8f429ffda 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new fe6c5f56c0 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 787fbdde0f 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new d71f0e4e8a 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new d93a3629a3 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 068f3ecdca 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new bd88c8c000 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 706064bdb5 232: onsuccess: #2048: 1: Success after glibc: 2 commits new d9e29d4361 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 217aea997d 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 9a2b1a5d05 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 922262162d 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new d7c33f155c 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 70079e8a79 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 088187ec29 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 2f69e93e27 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 9f76361b62 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 9d1775a094 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 424a13f238 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 6fe163d530 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 5b599f8456 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 181ea49547 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 6347b382a2 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 891bdf6375 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 66faaec970 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new a6518c2de1 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 61efb25c2c 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 386ca4eb04 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new bf9454cf33 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new b721c372e5 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 9e4aa02ce5 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new a254d79283 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new cf00be0afb 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new f9692065e7 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 9e96a38763 259: onsuccess: #2075: 1: Success after glibc: 2 commits new a3fbaab386 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 3530f7c143 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 65d65653c1 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new eef5f78300 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 29200a9a9d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 942798f45e 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 9f67154a36 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 4f45590035 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new fffc5bb4f9 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new b7f3d1eb78 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 750e0b1142 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 20bc3cefa6 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new f8f4492215 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new fb7b949fd3 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new feebc2f0e8 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 04bb8b9d35 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new cfb95bec97 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new b62b19f719 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new b1daad8c6b 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new ba64b5a5f7 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 636c00b74d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 7c93e602be 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 2f247b9f3e 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 0a71c96ebd 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new ca77bcdf44 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 0b06759851 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new eb8afe9be4 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new c898b77754 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 027ac9d5cd 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new c84e1e1ee8 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new f110bf539d 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 2e3e7ec597 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 1f65bbbb52 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 9714785d2b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new d66f27462a 294: onsuccess: #2110: 1: Success after gcc: 17 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 (59acff14eb) \ 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 1792 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31900 -> 32008 bytes 04-build_abe-stage1/console.log.xz | Bin 91552 -> 91796 bytes 06-build_abe-linux/console.log.xz | Bin 8396 -> 8384 bytes 07-build_abe-glibc/console.log.xz | Bin 236900 -> 236800 bytes 08-build_abe-stage2/console.log.xz | Bin 227420 -> 228468 bytes 09-build_abe-gdb/console.log.xz | Bin 39128 -> 39328 bytes 10-build_abe-qemu/console.log.xz | Bin 31712 -> 31692 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2496 -> 2716 bytes 13-check_regression/console.log.xz | Bin 5252 -> 5556 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 52 +- 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 34 +- .../results.regressions | 59 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 26 + sumfiles/g++.log.xz | Bin 2688384 -> 2652052 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2231648 -> 2248108 bytes sumfiles/gcc.sum | 2250 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 891668 -> 896332 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214188 -> 214028 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434972 -> 434496 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1300 insertions(+), 1317 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (73%)