Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (59acff14eb -> d66f27462a)

by git＠git.linaro.org

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%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (162d25c159 -> 3f0c2948f1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from 162d25c159 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 3f0c2948f1 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] The 1 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 1756 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52404 -> 52720 bytes 04-build_abe-gcc/console.log.xz | Bin 238620 -> 237988 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8356 -> 9212 bytes 07-build_abe-glibc/console.log.xz | Bin 236148 -> 235956 bytes 08-build_abe-gdb/console.log.xz | Bin 52504 -> 52300 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3860 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2552 -> 2648 bytes 11-check_regression/console.log.xz | Bin 5156 -> 5588 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- sumfiles/gdb.log.xz | Bin 14488 -> 14460 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (1d05acde67 -> e282392a56)

by git＠git.linaro.org

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 1d05acde67 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 90b3f0f250 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards e6e40e6d6e 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 7fb1e6f0c5 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards 0c50e75da6 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards 26a860c9ad 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards 09884d7859 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards 96c0ab8828 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards fca98030bb 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards 827969bde9 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards 8c838c258a 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards 96acf000b8 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards 7e8aa4a098 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards eedc3b3fdb 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards 89f232f931 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards c6ff4c983f 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards 4e15c1fa50 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards da5f68e41b 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards 6bc6206749 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards c72b0b6490 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards d0a161d84f 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards ae2ec1f2e6 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards bdcc59012d 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards aea6d9b60e 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 2d16ae50ba 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards 706c0bfe10 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 8a1e4bf24b 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 4591971b1f 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards c6d279c3c2 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards dd28e085d0 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards f3e5c1b871 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards 8066d6026a 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards 88e9f7d4a7 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards c32d2df9cf 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 8c5146be11 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards 33ce69456e 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards 3feceffe8a 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 1442a732b4 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards e2017a3351 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards 64797b13fc 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards e773738b60 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards 409041f89b 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards af4b70cddd 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] discards f5e807ebd7 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] discards 6b6be3a0ee 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] discards 53061d9200 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] discards d9151beeae 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 11956c7c47 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] discards a5b0f72e1f 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] discards 9247c03329 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] discards 6df7b2d6f4 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] discards 2dbaff1ad8 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] discards b978fe2d77 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] discards a6ed7df511 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] discards 21b0b65ae0 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] discards 68775ac7a5 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] discards aff1bf672f 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] discards 02ca56a9c2 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] discards decc2534e0 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] discards b0f5e1925d 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 1db4e3cc8a 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] discards fcb71a3942 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] discards 0a91852704 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] discards 4df3c6f3c1 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits discards 4732028793 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits discards b59de2bc9d 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] discards fd09d431f5 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits discards 2fc96294ca 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] discards 8fc4e1e58a 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] discards f1e7d16148 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits discards 987c64ed56 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards 60d4cce095 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] discards 73765593a9 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] discards 4ca9db5278 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] discards df488eaf51 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] discards 4e14f5afc4 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards de451c6f23 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards 0f05256af4 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] discards 7351e05a7a 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards f6c48d1f97 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] discards ec9d1e093f 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] discards 92927c716d 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] discards 0d236fef72 221: force: #1949: 3: Failure after basepoints/gcc-13-4492-g [...] discards 8a9b19a62c 220: force: #1948: 5: Success after gcc: 4 commits discards 88d17585f5 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards fa11e5bd91 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards bcf6d7ad7f 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943- [...] discards 98e22b8399 216: onsuccess: #1940: 7: Success after linux: 12 commits discards e8a7feb24c 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards be49d30be1 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards 3a9c69448b 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards 7478fff478 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards 91cffd91f7 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards f2c30db9fa 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 commits discards c7c99430aa 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/g [...] discards ba463390d6 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 88e2735340 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 22 [...] discards 4006dbe7d6 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/g [...] discards 4cdb5332b9 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 40 [...] discards 21591e3207 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 13 [...] discards 78022ba364 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 16 [...] new 254be2b4d8 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 16 [...] new 6ef0fedabc 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 13 [...] new 995b79f1fa 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 40 [...] new eee16c9bcb 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/g [...] new ff476cce4c 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 22 [...] new db9a1d2b06 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new 203a28713d 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/g [...] new 7bb400eeab 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 commits new 9ec1768b96 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 84a288b587 212: onsuccess: #1934: 7: Success after gcc: 3 commits new 133abaf6d7 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 360261d822 214: onsuccess: #1937: 7: Success after binutils: 4 commits new 277f680024 215: onsuccess: #1938: 7: Success after gcc: 4 commits new b7716c39c2 216: onsuccess: #1940: 7: Success after linux: 12 commits new 6bcff6a5d1 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943- [...] new 38d8e10542 218: onsuccess: #1943: 5: Success after gdb: 3 commits new 79d884c89e 219: onsuccess: #1945: 5: Success after binutils: 8 commits new 10c7f012c9 220: force: #1948: 5: Success after gcc: 4 commits new 7c0b397427 221: force: #1949: 3: Failure after basepoints/gcc-13-4492-g [...] new 839402d57c 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] new bf3074bb6a 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] new c355a2f836 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] new b1584e829d 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 6f13041b63 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] new d040efd639 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new c950c69edd 228: onsuccess: #1956: 7: Success after gcc: 5 commits new c8ff6bd45d 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] new 3568ad968f 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] new 5b69c91926 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] new 795bd2dfce 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] new 336ffb4b19 233: onsuccess: #1962: 7: Success after gcc: 6 commits new 307d7e5f76 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits new a9f6a28b08 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] new cbf7fb7076 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] new aa6242e234 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits new 2d7cdbb6ee 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] new 2008c40804 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits new bb2227f403 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits new f8deaeb8eb 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] new 08d74ae05d 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] new d071c9c5db 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] new 3f748b3010 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new e197b8942f 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] new 01397ca411 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] new 7808bcc868 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] new c0fafe5a98 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] new 479396b78b 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] new f2a0c9311a 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] new 3d622043b9 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] new 410e746214 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] new 08a026c018 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] new 5106141bce 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new 2f0b953f79 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] new c91053964b 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] new de8fcee75c 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 6052980293 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] new 7939547e18 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] new 7af171307f 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] new 119e070151 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] new e0e1a3feac 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new d96d4237bb 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new 583164a237 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new 6031b5c2f6 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new aa0b2ab5fd 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new acdae5fcae 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new 5252634620 268: onsuccess: #1997: 7: Success after glibc: 2 commits new 35f97e67b4 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new 228c7882cc 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new f15080786c 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new 7296c236e9 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new 433b46399c 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 8db4b4c2c1 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 7de81841a2 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new db7f8db1c0 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new b7872b3fb2 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new 2597fa3e1c 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new 8e93c29599 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new 25ab68803c 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 5d609c5279 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new 6f19d01713 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new 5d50a54a68 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new d96e70827f 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new a940b26af4 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new 64744dfd83 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new 5cf65f5b8e 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new 720c2bae8a 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new 206bd62242 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new 458083dc2c 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new df7ef2ea47 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new ea34056e12 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new 7edf545f64 293: onsuccess: #2022: 7: Success after gcc: 2 commits new 6028f64ce2 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 78f1b201a4 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new 8be8f6e050 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new 70c51299e1 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 320dce85db 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new a4f057ac0e 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new 54b4b4025b 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new 7b633ec428 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 2aa9b4a616 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new e0f534e634 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new e282392a56 304: onsuccess: #2033: 7: Success after gcc/linux: 60 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 (1d05acde67) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1768 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 31916 -> 32056 bytes 05-build_abe-stage1/console.log.xz | Bin 91196 -> 92292 bytes 07-build_abe-linux/console.log.xz | Bin 8352 -> 9256 bytes 08-build_abe-glibc/console.log.xz | Bin 236512 -> 237516 bytes 09-build_abe-stage2/console.log.xz | Bin 227988 -> 228856 bytes 10-build_abe-gdb/console.log.xz | Bin 39188 -> 39344 bytes 11-build_abe-qemu/console.log.xz | Bin 31744 -> 31836 bytes 12-check_regression/console.log.xz | Bin 3220 -> 3708 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++------- 18 files changed, 52 insertions(+), 52 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (5be4bb1fd9 -> 4f4fe4dda7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 5be4bb1fd9 475: onsuccess: #2437: 1: Success after gdb-13-branchpoint-2 [...] discards 45430713b3 474: onsuccess: #2436: 1: Success after basepoints/gcc-13-49 [...] discards 57ed746f85 473: onsuccess: #2435: 1: Success after binutils/gcc: 3 commits discards 8fd1adaf49 472: onsuccess: #2434: 1: Success after binutils: 2 commits discards f345e71438 471: onsuccess: #2433: 1: Success after gcc: 2 commits discards f4e0135626 470: onsuccess: #2432: 1: Success after gcc: 2 commits discards 17707f63ca 469: onsuccess: #2431: 1: Success after binutils/gcc: 7 commits discards cd3c16f0c2 468: onsuccess: #2430: 1: Success after binutils/gcc: 11 commits discards d318c357e9 467: onsuccess: #2429: 1: Success after basepoints/gcc-13-48 [...] discards 82e8a6ee86 466: onsuccess: #2428: 1: Success after binutils: 9 commits discards c365a806af 465: onsuccess: #2427: 1: Success after binutils/gcc: 3 commits discards 9511341b2f 464: onsuccess: #2426: 1: Success after basepoints/gcc-13-48 [...] discards b7a9e00ba8 463: onsuccess: #2425: 1: Success after binutils: 2 commits discards 8c31057872 462: onsuccess: #2424: 1: Success after gcc: 2 commits discards d39b7970d6 461: onsuccess: #2423: 1: Success after binutils: 2 commits discards 3107c484d1 460: onsuccess: #2422: 1: Success after gdb-13-branchpoint-1 [...] discards af87124525 459: onsuccess: #2421: 1: Success after binutils/gcc: 11 commits discards e3058bc76d 458: onsuccess: #2420: 1: Success after binutils/gcc: 9 commits discards d8ed3fe14d 457: onsuccess: #2419: 1: Success after binutils/gcc: 3 commits discards b349992bda 456: onsuccess: #2418: 1: Success after binutils/gcc: 4 commits discards cb0233def4 455: onsuccess: #2417: 1: Success after binutils/gcc: 2 commits discards 3419ea5cd5 454: onsuccess: #2416: 1: Success after binutils/gcc: 6 commits discards af37cfaa1c 453: onsuccess: #2415: 1: Success after binutils/gcc: 27 commits discards abeb71b0f5 452: onsuccess: #2414: 1: Success after binutils/gcc: 17 commits discards c4cf912092 451: onsuccess: #2413: 1: Success after binutils/gcc: 31 commits discards c3f5670a0f 450: onsuccess: #2412: 1: Success after binutils/gcc: 12 commits discards 4d3d72dc78 449: onsuccess: #2411: 1: Success after binutils/gcc: 11 commits discards c7ede7f193 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits discards fad9e9d787 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits discards 808245de6b 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits discards 311c1b44cc 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits discards 4e00111fbe 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits discards f96ee588c3 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits discards d0835d3332 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits discards ea7d154677 441: onsuccess: #2403: 1: Success after gcc: 3 commits discards 2000905127 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits discards ed159fe669 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits discards 6672ef1975 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits discards 35267690e6 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits discards 0d5508cb06 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits discards dcc21178dc 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] discards 452bb99539 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits discards e945b5762f 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits discards e41500ac3f 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits discards 32d09245a9 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits discards 6be9ea91f0 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] discards 31b3cc4a3c 429: onsuccess: #2391: 1: Success after binutils: 3 commits discards 3097dd3141 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits discards ddeaa9bfb4 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits discards b1a4caddb8 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits discards 7e10ca5534 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits discards 52264ab217 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits discards c523b1b4cf 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits discards bff5f96bb9 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits discards ab410ec822 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits discards b9ad18668f 420: onsuccess: #2382: 1: Success after gcc: 2 commits discards 64dadfe532 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits discards 141c4b08ab 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits discards 06b53d35bf 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits discards a04266f8ea 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits discards 48fef04b04 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits discards 97c04629b3 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits discards 0e6a6b8c70 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits discards 74287bac23 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits discards 66d2db45fb 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits discards 15eef5ebef 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits discards d88c5f9b70 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits discards a98508be19 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] discards b227740e1c 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits discards df428a4739 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits discards 038da2d225 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] discards dc74d26994 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] discards df5ae819cc 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits discards 4818856e8c 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits discards aac60b848b 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint-3 [...] discards 068f506980 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits discards 952a40ea2f 399: onsuccess: #2361: 1: Success after gcc: 10 commits discards 22bb32034d 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits discards e83eedf44c 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits discards 426d173fa5 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards b7ad7a83af 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards b7048ae04c 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards 8f864d9d0f 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards c309d02560 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards 0fa8bfd498 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards 8ea6ede753 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards 289a75853c 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards eb10491f49 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards ade00c1eac 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards f1afdd0706 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards 63a8c2942d 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards f152e9599b 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards 2ce40587b9 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards 68a3f5b0ef 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards d3be74f80e 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards 333a23a0d3 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards 70ba5109d1 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-44 [...] discards 6704dc738f 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards f9169d1a78 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards f0b8a4e06c 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards 4761fcfc48 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 1bcc16ce73 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 1c1be25106 376: onsuccess: #2338: 1: Success after gcc: 2 commits new 87eecb655e 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new dd8c3edcba 378: onsuccess: #2340: 1: Success after binutils: 2 commits new e0da5643f5 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-44 [...] new 6bc6da1897 380: onsuccess: #2342: 1: Success after gcc: 3 commits new d3e33ab76d 381: onsuccess: #2343: 1: Success after gcc: 2 commits new 72b059f037 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new 2ce01491ca 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new 650a170610 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new 90b938bbdc 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new a78c7dce72 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new 542c429bca 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new e6e694612a 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new 41fe1ea725 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new c1df6996f9 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new 7fc07d4838 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new 9280074435 392: onsuccess: #2354: 1: Success after gcc: 5 commits new 3f062ce22b 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new 7cc743d3d8 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new dd37464aa1 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new b80b67ca59 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new e1feed4ecf 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits new c5c0e2ed5a 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits new b5fd6a41b8 399: onsuccess: #2361: 1: Success after gcc: 10 commits new bf6d586308 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits new ec73090732 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint-3 [...] new 25d1c7abcb 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new 1a6f276595 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits new 8de99769d6 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] new c636e3bba9 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] new 0f0196a7a9 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits new 7a9d4c9b94 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits new d245a79e25 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] new badd08787f 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits new a26138c31f 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits new 87c312536d 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits new d280d23856 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits new 54d42258d3 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits new c4847b81cf 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits new ab621cbd84 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits new 3b75f6cb0c 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits new 987ad6be90 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new f0b8fbedc6 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits new fe7567c254 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits new af3030cbfa 420: onsuccess: #2382: 1: Success after gcc: 2 commits new 1fd9d9abb9 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits new 15d8347704 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits new 050e7a8850 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits new 335bd8c3ba 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits new 53bda695dc 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits new 06014ee3ac 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits new 89655caa14 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits new 628f667168 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits new f8ca7465eb 429: onsuccess: #2391: 1: Success after binutils: 3 commits new bb5fdd9a13 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] new 4ec88656fd 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits new 7706857bd5 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits new c09ee17b45 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits new ae3e17de7b 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits new fd9fb728c4 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] new 045f1639cc 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits new 5a92fc947f 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits new d5361e0f1e 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits new 99d7b22bc5 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits new ad8a06b43a 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits new 47ea03ba0c 441: onsuccess: #2403: 1: Success after gcc: 3 commits new 6c2ce4af84 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits new 5150ecc310 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits new 428f60eac7 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits new 6e1e1219fa 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits new ed587c6640 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits new ba5cf1466c 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits new 08ddd4b3c0 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits new 3b8e5a5592 449: onsuccess: #2411: 1: Success after binutils/gcc: 11 commits new 98b5bdd865 450: onsuccess: #2412: 1: Success after binutils/gcc: 12 commits new 47d62a115c 451: onsuccess: #2413: 1: Success after binutils/gcc: 31 commits new c91f9cd39e 452: onsuccess: #2414: 1: Success after binutils/gcc: 17 commits new 4c790c8b6b 453: onsuccess: #2415: 1: Success after binutils/gcc: 27 commits new ccdc0340ef 454: onsuccess: #2416: 1: Success after binutils/gcc: 6 commits new d2bbee0d6d 455: onsuccess: #2417: 1: Success after binutils/gcc: 2 commits new debe32b33e 456: onsuccess: #2418: 1: Success after binutils/gcc: 4 commits new d52cfa16cd 457: onsuccess: #2419: 1: Success after binutils/gcc: 3 commits new ddc113494a 458: onsuccess: #2420: 1: Success after binutils/gcc: 9 commits new 3a46e77859 459: onsuccess: #2421: 1: Success after binutils/gcc: 11 commits new f1ee055ab1 460: onsuccess: #2422: 1: Success after gdb-13-branchpoint-1 [...] new 0179ffc85c 461: onsuccess: #2423: 1: Success after binutils: 2 commits new add9f07756 462: onsuccess: #2424: 1: Success after gcc: 2 commits new 3a544db090 463: onsuccess: #2425: 1: Success after binutils: 2 commits new 71e10042aa 464: onsuccess: #2426: 1: Success after basepoints/gcc-13-48 [...] new 04415fcd6c 465: onsuccess: #2427: 1: Success after binutils/gcc: 3 commits new 81af5b5a93 466: onsuccess: #2428: 1: Success after binutils: 9 commits new 75ae2b9169 467: onsuccess: #2429: 1: Success after basepoints/gcc-13-48 [...] new b5eb9f5f0c 468: onsuccess: #2430: 1: Success after binutils/gcc: 11 commits new 7595c5901a 469: onsuccess: #2431: 1: Success after binutils/gcc: 7 commits new 1ef9938114 470: onsuccess: #2432: 1: Success after gcc: 2 commits new 3d722a9573 471: onsuccess: #2433: 1: Success after gcc: 2 commits new 6e499b5a53 472: onsuccess: #2434: 1: Success after binutils: 2 commits new 60e4c1a452 473: onsuccess: #2435: 1: Success after binutils/gcc: 3 commits new 1a8ef00c70 474: onsuccess: #2436: 1: Success after basepoints/gcc-13-49 [...] new f6adc2c798 475: onsuccess: #2437: 1: Success after gdb-13-branchpoint-2 [...] new 4f4fe4dda7 476: onsuccess: #2438: 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 (5be4bb1fd9) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 1796 -> 1836 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 40228 -> 40376 bytes 04-build_abe-gcc/console.log.xz | Bin 213560 -> 213960 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3920 -> 3840 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2404 -> 2568 bytes 07-check_regression/console.log.xz | Bin 4324 -> 4488 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 08-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 3625180 -> 3630376 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 3145004 -> 3136936 bytes sumfiles/gcc.sum | 4356 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1056600 -> 1051120 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 220152 -> 219696 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453564 -> 458764 bytes sumfiles/libstdc++.sum | 12 +- 30 files changed, 2324 insertions(+), 2326 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (08d21b7718 -> e11c21a466)

by git＠git.linaro.org

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_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 08d21b7718 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards c112ffc27d 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 7c3153b25a 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards 4a1e558fb2 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards 22ca05f667 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 1b04479862 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards 250679a07e 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards 0fb39c22ed 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards a68bfee995 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards 74f153b579 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards ab749fa428 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards 4433c2bdaf 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards e330824289 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards 68ea2cdf2a 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards 799b2694be 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards d10a945fd8 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards b9f9f71fa9 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards 85a0be81ed 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards d755987bfd 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 4f04bb320b 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 35d2d42c75 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 76f4e4ed0a 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards 59f07576cb 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards efeb260aa7 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards 3bc0816f2c 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards 4e3d1394db 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards b466187d1a 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards 342e1b31d2 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards f247fe6376 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards ea95c226e5 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 72d59910d3 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 3a6825a5d1 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 53d67c17dc 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards e335f500db 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards dce9cb4f46 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards a9a61e12b2 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards c6367f3f67 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 4310087d03 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards 8b31910619 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards 6715bf54ca 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards a2bbf17d86 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 666148d2d0 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards 3d49982e94 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards a97d4cf803 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards 0856297f6c 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards 5c230883a5 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards c6790861af 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards a9b7e97305 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards 6ee427fd6e 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards b800ed999b 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards 46d97cee12 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards 557cfee0ec 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 26821c4788 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards d6c8a68997 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 337301b535 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 322defa741 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 2fc14c472f 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards 15297a20ef 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 31d496bf4e 229: force: #1926: 7: Success after gcc: 7 commits discards d02841e9f0 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards 26b9321896 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 8ba6f8f056 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 4c0e57ca66 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards 70d8c4a2d4 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards 114b09f669 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards e1c8d805e7 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards 93e74082ed 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards 1d50c2aa2a 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards 7bef071a1c 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards 69009838d0 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards 70a6d0f693 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards 718f3c2efe 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards d939fa8d20 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards 4708b9e76e 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards da4c020d7f 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 3d1cb21ff6 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards 8c2841f2b2 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards 2bcacbfa0b 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 65bb30690e 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards 5a9986d06c 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 5805319a75 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 9d61b6c97a 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards 7ac91971bd 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 58aae860b5 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] discards 2caf5dea94 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits discards 80a97d8da3 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 031135f196 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] discards fa87a775c0 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards 86696c4682 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] discards a65a13da97 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 2235fdf9da 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] discards a6c3365ffc 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] discards bff09ae8bb 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] discards 26928db94d 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] discards b5e48b037f 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] discards 6055bc7ee4 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] discards fe7fe445d8 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] discards 37759d22aa 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 98b726580d 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] discards a7119dbe16 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] discards c099d0c47d 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] new adfe9ea345 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] new e70461480c 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] new 99768bd172 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] new 102b9e8db3 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 4ac0182ed1 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] new defdb911f9 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] new c7958c0057 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] new 7b47a55fef 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] new 4839fa67d2 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] new 9fb80b9880 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] new 40adf78040 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] new 39fbc45246 198: onsuccess: #1852: 7: Success after gcc: 5 commits new 64e2d09a38 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] new 405771cf75 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new a2b6c74e8b 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] new 10f20a1116 202: onsuccess: #1856: 7: Success after gcc: 2 commits new b57a64f64b 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits new 74f6f9d881 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] new c319e176e4 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 0a5b11f287 206: onsuccess: #1860: 7: Success after gcc: 2 commits new 3f561065af 207: onsuccess: #1862: 7: Success after binutils: 4 commits new d4d66fb768 208: onsuccess: #1865: 7: Success after linux: 12 commits new 401d9b05f8 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new bc106d7dee 210: onsuccess: #1868: 7: Success after binutils: 7 commits new a93d457975 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new 5164f54c0e 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new 06bf1e0b86 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 2687c604b3 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new 2160e5595d 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new cfd50f13a9 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 2cffac53d1 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new 3d3023ab61 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new a421fb0e1a 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new 81339eb0c7 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new 5dab7c683c 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new f264c7f556 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new e251ee4a20 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new 0cb2e86218 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new 9c90826cd8 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new b0445d0926 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new 24bb8a9c96 227: onsuccess: #1906: 7: Success after binutils: 9 commits new b4359f5850 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 0f88592369 229: force: #1926: 7: Success after gcc: 7 commits new 5a6f44c92c 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 441ffaec2e 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 437663f076 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new 23c8218dd3 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new 8bd3792b3f 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 8d58bcc47b 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new 35218b6a52 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 5acec8d540 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new 723f244227 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new 389e13ea8c 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new 205b5bfc5f 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new a99d193b69 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new cc01a6fc25 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new 76ccd61aaf 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 14ece8de99 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new 5338aa94b1 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new d21b03ec2a 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 1cfa038aec 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new bd31f15c4a 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 35188958c8 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new b4695b3375 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new d8f00dd0fc 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 4da983ad2d 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new 6d1b7aac75 253: onsuccess: #1950: 7: Success after glibc: 2 commits new e7bf175e16 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new 53b7f57cf6 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 4b8fcaa016 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 3171a7fb3f 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new b9b84d48a2 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 513d05bd6e 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new c1e1a67461 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new 3cad6d6884 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new e3979a8156 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new fde91df2e6 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 220823c6c3 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 8fb460cec1 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 769cc6cacc 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new 3b6116ddf9 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new fb2abf8018 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new 2489dc4b63 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new 6bce3ede1f 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 5acf79d4f3 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new e17381214f 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 319aee9c67 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 274920124f 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 674fa0ac9f 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new 863591f4ac 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new d7a18d2372 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 0052d99010 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new a616ecf540 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new a2419bc7e0 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new 17483bb156 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new c65b14ee5e 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new 8eefb309fb 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 56faa35dfb 284: onsuccess: #1981: 7: Success after gcc: 2 commits new 8a52916ea0 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new e88f5e4d90 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 1f002930b4 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new e11c21a466 288: onsuccess: #1985: 7: 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 (08d21b7718) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1720 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 32196 -> 32192 bytes 05-build_abe-stage1/console.log.xz | Bin 73368 -> 73604 bytes 07-build_abe-linux/console.log.xz | Bin 8392 -> 8384 bytes 08-build_abe-glibc/console.log.xz | Bin 245356 -> 245368 bytes 09-build_abe-stage2/console.log.xz | Bin 204804 -> 204828 bytes 10-build_abe-gdb/console.log.xz | Bin 39520 -> 39500 bytes 11-build_abe-qemu/console.log.xz | Bin 31428 -> 31944 bytes 12-check_regression/console.log.xz | Bin 3108 -> 3336 bytes 13-update_baseline/console.log | 42 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++--------- 17 files changed, 36 insertions(+), 36 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-release-arm-spec2k6-O3_LTO updated (8460e5a440 -> d9d95e5274)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-release-arm-spec2k6-O3_LTO in repository toolchain/ci/base-artifacts. from 8460e5a440 48: onsuccess: #337: 1: [TCWG CI] No change after binutils/g [...] new d9d95e5274 49: force: #345: 1: [TCWG CI] No change after baseline build [...] The 1 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 1772 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30168 -> 30660 bytes 04-build_abe-stage1/console.log.xz | Bin 88700 -> 88436 bytes 06-build_abe-linux/console.log.xz | Bin 7900 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 231336 -> 231856 bytes 08-build_abe-stage2/console.log.xz | Bin 209016 -> 210524 bytes 09-benchmark/benchmark-build.log | 136 +- 09-benchmark/benchmark.log | 134 +- 09-benchmark/console.log.xz | Bin 3884 -> 4012 bytes 10-check_regression/console.log.xz | Bin 7444 -> 5772 bytes .../csv-results-vs-first-0/results.csv | 439806 +++++++------- .../csv-results-vs-first-0/size.csv | 474886 +++++++-------- .../csv-results-vs-first-0/vect.csv | 29 - .../csv-results-vs-first-1/perf.csv | 185 +- .../csv-results-vs-first-1/results.csv | 566261 ++++++++--------- .../csv-results-vs-first-1/size.csv | 568688 +++++++++--------- .../csv-results-vs-first-1/vect.csv | 40 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 196 +- .../csv-results-vs-prev-0/results.csv | 555768 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 558186 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 42 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 185 +- .../csv-results-vs-prev-1/results.csv | 566261 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/size.csv | 568688 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 40 +- 10-check_regression/mail-body.txt | 5 + 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 183 +- 10-check_regression/results-vs-first-internal.csv | 80 +- 10-check_regression/results-vs-first.csv | 80 +- 10-check_regression/results-vs-first.log | 1324 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-full.csv | 201 +- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 1574 +- 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 8 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../434.zeusmp/results-metadata.json | 8 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 8 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 8 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 8 +- .../453.povray/results-metadata.json | 8 +- .../454.calculix/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 8 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 8 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../471.omnetpp/results-metadata.json | 8 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 8 +- .../483.xalancbmk/results-metadata.json | 8 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- mail/jira-body.txt | 21 +- mail/mail-body.txt | 26 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 0 -> 2549756 bytes save-temps/401.bzip2.tar.xz | Bin 0 -> 234492 bytes save-temps/403.gcc.tar.xz | Bin 0 -> 6843768 bytes save-temps/410.bwaves.tar.xz | Bin 0 -> 47844 bytes .../results.csv => save-temps/416.gamess.tar.xz | Bin 15201259 -> 13817220 bytes save-temps/429.mcf.tar.xz | Bin 0 -> 69628 bytes save-temps/433.milc.tar.xz | Bin 0 -> 333244 bytes save-temps/434.zeusmp.tar.xz | Bin 0 -> 428176 bytes save-temps/435.gromacs.tar.xz | Bin 0 -> 2111148 bytes save-temps/436.cactusADM.tar.xz | Bin 0 -> 1524620 bytes save-temps/437.leslie3d.tar.xz | Bin 0 -> 151400 bytes save-temps/444.namd.tar.xz | Bin 0 -> 486200 bytes save-temps/445.gobmk.tar.xz | Bin 0 -> 2490084 bytes .../size.csv => save-temps/447.dealII.tar.xz | Bin 12106217 -> 10714172 bytes save-temps/450.soplex.tar.xz | Bin 0 -> 1215988 bytes save-temps/453.povray.tar.xz | Bin 0 -> 2277212 bytes save-temps/454.calculix.tar.xz | Bin 0 -> 3174532 bytes save-temps/456.hmmer.tar.xz | Bin 0 -> 808860 bytes save-temps/458.sjeng.tar.xz | Bin 0 -> 301852 bytes save-temps/459.GemsFDTD.tar.xz | Bin 0 -> 521928 bytes save-temps/462.libquantum.tar.xz | Bin 0 -> 120504 bytes save-temps/464.h264ref.tar.xz | Bin 0 -> 1827476 bytes save-temps/465.tonto.tar.xz | Bin 0 -> 6061996 bytes save-temps/470.lbm.tar.xz | Bin 0 -> 43972 bytes save-temps/471.omnetpp.tar.xz | Bin 0 -> 1408972 bytes save-temps/473.astar.tar.xz | Bin 0 -> 141708 bytes save-temps/481.wrf.tar.xz | Bin 0 -> 6952448 bytes save-temps/482.sphinx3.tar.xz | Bin 0 -> 519772 bytes .../results.csv => save-temps/483.xalancbmk.tar.xz | Bin 15201259 -> 15541408 bytes 116 files changed, 2172826 insertions(+), 2130915 deletions(-) create mode 100644 save-temps/400.perlbench.tar.xz create mode 100644 save-temps/401.bzip2.tar.xz create mode 100644 save-temps/403.gcc.tar.xz create mode 100644 save-temps/410.bwaves.tar.xz copy 10-check_regression/csv-results-vs-prev-0/results.csv => save-temps/416.games [...] create mode 100644 save-temps/429.mcf.tar.xz create mode 100644 save-temps/433.milc.tar.xz create mode 100644 save-temps/434.zeusmp.tar.xz create mode 100644 save-temps/435.gromacs.tar.xz create mode 100644 save-temps/436.cactusADM.tar.xz create mode 100644 save-temps/437.leslie3d.tar.xz create mode 100644 save-temps/444.namd.tar.xz create mode 100644 save-temps/445.gobmk.tar.xz copy 10-check_regression/csv-results-vs-prev-1/size.csv => save-temps/447.dealII.t [...] create mode 100644 save-temps/450.soplex.tar.xz create mode 100644 save-temps/453.povray.tar.xz create mode 100644 save-temps/454.calculix.tar.xz create mode 100644 save-temps/456.hmmer.tar.xz create mode 100644 save-temps/458.sjeng.tar.xz create mode 100644 save-temps/459.GemsFDTD.tar.xz create mode 100644 save-temps/462.libquantum.tar.xz create mode 100644 save-temps/464.h264ref.tar.xz create mode 100644 save-temps/465.tonto.tar.xz create mode 100644 save-temps/470.lbm.tar.xz create mode 100644 save-temps/471.omnetpp.tar.xz create mode 100644 save-temps/473.astar.tar.xz create mode 100644 save-temps/481.wrf.tar.xz create mode 100644 save-temps/482.sphinx3.tar.xz copy 10-check_regression/csv-results-vs-prev-0/results.csv => save-temps/483.xalan [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (77a393f38d -> 2c9c4d16d1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 77a393f38d 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 375724eb76 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 3e41c40e51 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 978d00d000 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 3c4bcacabc 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 112ace12b3 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 839d381ef7 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 74297ec058 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards b30d62a1f9 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards cacb58b1df 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 9c385c1025 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 006b8a3763 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 0fb0b1148a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 8729bb78a5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards faa1da1510 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 4c87e70201 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 81023c14aa 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 6bc40fe449 127: onsuccess: #874: 1: Success after linux: 219 commits discards 657c50cfcc 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 835dd77589 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 47c1b23d33 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards c421e848fb 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 641a9d8151 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 97d336663c 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 2e394f9b39 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards fb41c51340 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 85fd1a565c 118: onsuccess: #863: 1: Success after linux: 12 commits discards 530eba5ce5 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 574c04f0b1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 7d3409d1ab 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 6f14db952c 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 0401b9c15c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards fd0c431ead 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards d6ed9c2243 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 7b3ce70931 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards af304e8035 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards c71a7d355a 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 8f5c62498e 107: onsuccess: #849: 1: Success after binutils: 5 commits discards c48b7da249 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards d145dc8d4f 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 2ff6e6f6ab 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 985666ec4a 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards aecfdbdc96 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 55a98a2798 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 52e95e95a8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 94d02e6b04 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 568d9cdc57 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 96b0f5b851 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 06988a334f 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 3ca9126fdd 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 026786b387 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 06df8271ed 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 5b4accfc6b 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards abc07571a3 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 0f54c2e826 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 9d5c42b655 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 2400f643e0 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards b490c099f6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 76badb6424 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 36e0550617 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards cbfd8fd6fd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 8691904441 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 402f69e6ef 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 080ba6c4f6 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 7e3881f187 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 7f59f761ac 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards dfac8582f1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards d54a435ee4 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 3ec44caac0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 333065644e 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 8683f57d9c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 04ff134229 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 5e267444ee 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 24ee31c89b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards ebb6b78f0c 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 80b074a62b 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 268bbffdee 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 8f65c70663 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards aad3b641d6 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 5dd1ae1133 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards f5eff59d75 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards df2ccd9da0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 5327f1d355 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 10e94b81f1 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards f39f6a3c44 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards fba45f217b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 36a5002f8a 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards fea32b80b9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 295774c30a 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 96526bfe65 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 6cd53f163a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 543cd79c6f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards e1ccc60399 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 1292b09ed4 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 0415cf1c39 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 0b1b120554 49: onsuccess: #785: 1: Success after binutils: 12 commits discards b31b100852 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 1adc18cce2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 74c31ad4d5 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards d365b578f5 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 29d1b93781 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new da013c2b8c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 191c2cc239 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new b2efff13e5 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 8adcf680e6 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new b0dac5b735 48: onsuccess: #782: 1: Success after binutils: 8 commits new 7af707d007 49: onsuccess: #785: 1: Success after binutils: 12 commits new d4bb7a3984 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 0d751cd653 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new e54479d540 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new f1a3127921 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 77daa8b69b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 44145f1dd5 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new ba7a260138 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 615900261e 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new a9ba0ba87c 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 4f7f1532b5 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 84476c4a37 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new a22f828097 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new d47cd57242 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new e8da32b884 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new e9a4754893 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 8ac606e8cf 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new f330a326b9 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 9800b9b0e8 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new e0fe7e7993 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 2a66fae41d 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 94d5131c54 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new f55c9773c1 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 6710d3ec9e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 20bf82338c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new a17d506ee6 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 04355755fc 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 774c2bb42c 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 4865057772 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 1fa7ff82df 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new fdbaa9877c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new bdcaab6899 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new fea247141e 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new ce6e4355f2 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 89b045c217 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 7f053e9b3b 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 441ea34f32 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 188a7cb994 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 24c9c7f676 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new c5e1d3ba6f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 2e240b9987 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 129c240ef4 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 1013e3f96f 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 5ac89d31b0 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new dcb61a1b66 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 9ccd402560 94: onsuccess: #832: 1: Success after binutils: 5 commits new a1fe8fa987 95: onsuccess: #835: 1: Success after binutils: 3 commits new c58c454c12 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 6752875e5f 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 59c4d4b7e6 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 3c31993f0b 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 220cb39fde 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 3a42d12ebc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 5ee49c3c9f 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 5c16c55c20 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new d804ff6e95 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new a6736b940d 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new f3d4754fb9 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 5c054d1aef 107: onsuccess: #849: 1: Success after binutils: 5 commits new 231484db07 108: onsuccess: #850: 1: Success after gcc: 2 commits new ae4a97746a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new b4476c07c8 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 2d959e7ee2 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 2b52751c5c 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 5de2315957 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 13ad58939f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new efa3a57d83 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 90a8b8f07b 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 64df89c713 117: onsuccess: #861: 1: Success after binutils: 18 commits new e92ff66b31 118: onsuccess: #863: 1: Success after linux: 12 commits new 3e89817dcd 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 0996a3d3cb 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 3ff7aa9298 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 263e4970ef 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new a7ebaa8438 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 80c0f23c2a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new f0dd45f0be 125: onsuccess: #871: 1: Success after binutils: 26 commits new d6b0ae661d 126: onsuccess: #873: 1: Success after glibc: 2 commits new bfa8d0418d 127: onsuccess: #874: 1: Success after linux: 219 commits new aac8d9ad06 128: onsuccess: #876: 1: Success after binutils: 12 commits new bcb7055c3f 129: onsuccess: #878: 1: Success after linux: 3008 commits new 6c02710f90 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new be1eb62d5a 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 3636a003b9 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 2cf95525bb 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 6bc663df0b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 52e44e41cb 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new e412273c69 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 4101db7bcf 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 059eaab368 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new e3d4ac71d8 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new df96f15138 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 9cb6755d8e 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 5c7be1cf12 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new b95c1c2a22 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 0c12b80ab4 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 2c9c4d16d1 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 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 (77a393f38d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 1732 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39800 -> 39776 bytes 04-build_abe-gcc/console.log.xz | Bin 214496 -> 213616 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8356 -> 8380 bytes 07-build_abe-glibc/console.log.xz | Bin 244684 -> 245964 bytes 08-build_abe-gdb/console.log.xz | Bin 39348 -> 39408 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3892 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2424 -> 2480 bytes 11-check_regression/console.log.xz | Bin 5656 -> 5356 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 18 +- 12-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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 3731524 -> 3774208 bytes sumfiles/g++.sum | 110 +- sumfiles/gcc.log.xz | Bin 3291524 -> 3305512 bytes sumfiles/gcc.sum | 4456 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1079284 -> 1073896 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232132 -> 232224 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 456444 -> 457348 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2378 insertions(+), 2386 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (0ac2e6e6aa -> 510f80cfb5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 0ac2e6e6aa 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 3349c0284e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards a47b198320 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards eedf5b1665 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards e99a435c4e 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards cb8aadbbab 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards e6d6280d14 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 4a08c66ce6 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 416868be77 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards c14a0349f5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards ea48ee8025 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards ccf3ed8bf0 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 37ec61698b 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards dd1a4bdf9b 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 95235cb24a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 6409a1ef56 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards bd0b6b8e7a 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 8173de9027 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 8db347fdf3 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards e9142fdc48 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 6fe7ca075c 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards dd0f6badee 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 4088b937a6 125: onsuccess: #614: 1: Success after linux: 12 commits discards 1c65e42df3 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 0facc32aeb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 626b5dfccc 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards eb39c927cd 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards aa8d3225f5 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 7f62a430b6 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards df6e0d491a 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards bd57f458d9 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 6ca69b4db4 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 5305d7360e 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards cd76eac69f 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards f972c5d791 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 7e697f2548 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 789daae745 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 70b55b78bd 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards b786c18d82 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards d8c345a3f4 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 7ae8edec2c 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 0b6bc6806f 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards a027fdec6a 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 9510c43aa5 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 14df8f6660 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 6e90f2631c 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 2f71c57b89 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 640296c095 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards f34a585dff 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards b94aa1b4ed 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 71e275e2a5 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 1b73febc99 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards cb1774497d 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 0877a38a6d 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards c06701af1d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards a6e05ad34f 92: onsuccess: #575: 1: Success after linux: 34 commits discards 8b9c768a08 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 785f2289e2 90: onsuccess: #572: 1: Success after binutils: 15 commits discards b9ae89319a 89: onsuccess: #570: 1: Success after linux: 11 commits discards 65e23639a4 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 3e971060ef 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 77f136a4dc 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards bd958c8efd 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards ddf761dbc1 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards ff2274309d 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards e9d2594f3b 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 230f64bc92 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards a5bc768c7b 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards b316705a2d 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards d54ca08680 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards fa28b278da 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards ac89cef3cc 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards bfb999288f 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 49a039ea29 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 67636ef2c8 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 86a08d290e 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards ba6db754fc 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 0dd54c5189 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 9a20882e2a 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 4839818292 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards e3d6efa932 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards fbd79aa2a0 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 6e640dd1b6 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 63f87abaa0 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards d434a245eb 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 3ec17cbe93 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards d16666d77e 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards e6ea834bef 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 6d3564c6ea 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 5aa6d9c32c 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 5941368c1f 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 8e91293400 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 0d94bb0a12 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 91aaf9e84a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 66c218448f 53: onsuccess: #531: 1: Success after binutils: 12 commits discards c3a0acbf12 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 2f57f9944c 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 87ec9ddbbe 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 4e278b4d17 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 6d67be3a94 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards fe4b6acc63 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 953cae74f3 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new d887012929 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 13883d3379 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 932f4b6599 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 62a20430fd 51: onsuccess: #525: 1: Success after binutils: 8 commits new 85b15c1bd2 52: onsuccess: #528: 1: Success after binutils: 8 commits new 00d6a53a47 53: onsuccess: #531: 1: Success after binutils: 12 commits new 1d7fbd0506 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 7205ac4505 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 7664153310 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 630217e8db 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 1896c1ceda 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 3e51f99a05 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new dbb1e11ce8 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 516412395c 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new cb6c780dba 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new f2a46ba03f 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new d1d1647e9f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 0ab9105780 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new c4bdd13ffc 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new a560048a73 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new bff39b80cd 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 2ca7847d8b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new b6827ca80d 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 9db3dda933 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 04441701c8 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new dd8e6bc2e9 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 681c33f9b4 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new f6d676583e 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 0e32c8e95d 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new b634f769aa 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new fab126aa77 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new d5a34042c2 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new fd1eec9255 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new f20c5e1d05 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 0f8d5bfede 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new e9ff46cbc9 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new c70f6fb824 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new dd58562fd7 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new a6689be014 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 12269037bf 87: onsuccess: #567: 1: Success after binutils: 8 commits new 7e44d330cc 88: onsuccess: #569: 1: Success after glibc: 10 commits new 62810533b9 89: onsuccess: #570: 1: Success after linux: 11 commits new 9f356d8f44 90: onsuccess: #572: 1: Success after binutils: 15 commits new 72f89b391e 91: onsuccess: #574: 1: Success after glibc: 3 commits new 43d8ffdf2c 92: onsuccess: #575: 1: Success after linux: 34 commits new f8f1e5d4e1 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 48878b1028 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new addfd51b36 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 55e8a0f4b8 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new aee585d925 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 8753185845 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new b5055b6142 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 9e40c88cce 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new bf3a15c546 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new e22607dbe3 102: onsuccess: #586: 1: Success after binutils: 5 commits new 2ec8d59f03 103: onsuccess: #589: 1: Success after binutils: 3 commits new 851e2fb93a 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 13432baebe 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new acb897c3d6 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new e5d4575ce0 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new aa83582c51 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 0261407f6d 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new a20f7f287b 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 8663a27a2b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 1aacf95fc6 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new e67c279e72 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 5c9b21cf76 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new aec59721be 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new a7f291566c 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 728273310d 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 6f7be130ac 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new a03207b9fd 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 44a87d42f3 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new b95c9e6888 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new cad7c921ae 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new a0b4459343 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new fb3ff4d48d 124: onsuccess: #612: 1: Success after binutils: 18 commits new 5aca69f576 125: onsuccess: #614: 1: Success after linux: 12 commits new a57bc7fab6 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new dbb880ad44 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 7ae6631425 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 95e1ca445c 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new d14a259b60 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 4bb45323ff 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 19bdae4a13 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 9983989ded 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new d7ca108a49 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 614f32d9fd 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 3f3db36b34 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 31025738da 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 06f5c0582f 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 501362cee5 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new c941428798 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 855fa0e6d7 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new a89efdaf82 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new ecdcba577a 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 28a8d2cafe 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new e6a1827183 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 8045c09b50 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new f444cbb502 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 510f80cfb5 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 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 (0ac2e6e6aa) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1728 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 52872 -> 52916 bytes 04-build_abe-gcc/console.log.xz | Bin 240124 -> 237924 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8428 -> 8304 bytes 07-build_abe-glibc/console.log.xz | Bin 238832 -> 236888 bytes 08-build_abe-gdb/console.log.xz | Bin 52540 -> 51556 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2208 -> 2308 bytes 11-check_regression/console.log.xz | Bin 7708 -> 19968 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 41 +- 11-check_regression/mail-body.txt | 174 +- 11-check_regression/results.compare | 83 +- 11-check_regression/results.compare2 | 6074 +++++++++++++++- 11-check_regression/results.regressions | 83 +- 12-update_baseline/console.log | 46 +- 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 | 176 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 83 +- sumfiles/gdb.log.xz | Bin 1694500 -> 1723064 bytes sumfiles/gdb.sum | 11042 ++++++++++++++++++------------ 29 files changed, 12960 insertions(+), 4884 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[linux] branch master updated (1b929c02afd3 -> 2258c2dc850b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from 1b929c02afd3 Linux 6.2-rc1 new 55c590adfe18 KVM: x86/pmu: Prevent zero period event from being repeate [...] new fceb3a36c29a KVM: x86: ioapic: Fix level-triggered EOI and userspace I/ [...] new 8b9e13d2de73 KVM: x86: hyper-v: Fix 'using uninitialized value' Coverit [...] new 3c649918b764 KVM: x86: Simplify kvm_apic_hw_enabled new 77b1908e10ec KVM: x86: Sanity check inputs to kvm_handle_memory_failure() new 53800f88d414 KVM: selftests: Zero out valid_bank_mask for "all" case in [...] new 057b18756b46 KVM: nVMX: Document that ignoring memory failures for VMCL [...] new 31de69f4eea7 KVM: nVMX: Properly expose ENABLE_USR_WAIT_PAUSE control to L1 new a0860d68a25d KVM: nVMX: Don't stuff secondary execution control if it's [...] new f5d16bb9be68 KVM: x86/mmu: Don't attempt to map leaf if target TDP MMU [...] new 80a3e4ae962d KVM: x86/mmu: Map TDP MMU leaf SPTE iff target level is reached new 21a36ac6b6c7 KVM: x86/mmu: Re-check under lock that TDP MMU SP hugepage [...] new 50a9ac25985c KVM: x86/mmu: Don't install TDP MMU SPTE if SP has unexpec [...] new e779fd53b4aa KVM: selftests: Define literal to asm constraint in aarch6 [...] new 73441efa36c2 KVM: selftests: Delete dead code in x86_64/vmx_tsc_adjust_test.c new d61a12cb9af5 KVM: selftests: Fix divide-by-zero bug in memslot_perf_test new 43e96957e8b8 KVM: selftests: Use pattern matching in .gitignore new 1525429fe5cb KVM: selftests: Fix a typo in x86-64's kvm_get_cpu_address [...] new 6a5db83adfd6 KVM: selftests: Rename UNAME_M to ARCH_DIR, fill explicitl [...] new 5dc38777a7de KVM: selftests: Use proper function prototypes in probing code new 2b2d8afc1acf KVM: selftests: Probe -no-pie with actual CFLAGS used to compile new 7cf2e7373ab1 KVM: selftests: Explicitly disable builtins for mem*() overrides new 5efb946b9569 KVM: selftests: Include lib.mk before consuming $(CC) new db7b780dab67 KVM: selftests: Disable "gnu-variable-sized-type-not-at-en [...] new 2f5213b8fc31 KVM: selftests: Use magic value to signal ucall_alloc() failure new feb84f6daa7e KVM: selftests: document the default implementation of vm_ [...] new 7a16142505cb KVM: arm64: selftests: Don't identity map the ucall MMIO hole new 92c8191bb5d3 KVM: selftests: Mark correct page as mapped in virt_map() new e0a78525f540 MAINTAINERS: adjust entry after renaming the vmx hyperv files new a303def0fc18 kvm: Remove the unused macro KVM_MMU_READ_{,UN}LOCK() new 562f5bc48a8d kvm: x86/mmu: Remove duplicated "be split" in spte.h new 23e528d9bce2 KVM: Delete extra block of "};" in the KVM API documentation new 385407a69d51 KVM: x86/xen: Fix memory leak in kvm_xen_write_hypercall_page() new 92c58965e965 KVM: x86/xen: Use kvm_read_guest_virt() instead of open-co [...] new 70eae03087a3 KVM: x86/xen: Fix SRCU/RCU usage in readers of evtchn_ports new 1c14faa5087d KVM: x86/xen: Simplify eventfd IOCTLs new b0305c1e0e27 KVM: x86/xen: Add KVM_XEN_INVALID_GPA and KVM_XEN_INVALID_ [...] new af2808906aab KVM: x86/xen: Documentation updates and clarifications new a79b53aaaab5 KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET new 02d9a04da453 Documentation: kvm: clarify SRCU locking order new 129c48cde6c9 KVM: selftests: restore special vmmcall code layout needed [...] new a5496886eb13 Merge branch 'kvm-late-6.1-fixes' into HEAD new 2258c2dc850b Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt [...] The 43 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: Documentation/virt/kvm/api.rst | 46 ++++--- Documentation/virt/kvm/locking.rst | 19 ++- MAINTAINERS | 2 +- arch/x86/kvm/hyperv.c | 63 +++++---- arch/x86/kvm/irq_comm.c | 5 +- arch/x86/kvm/lapic.h | 4 +- arch/x86/kvm/mmu/spte.h | 2 +- arch/x86/kvm/mmu/tdp_mmu.c | 25 +++- arch/x86/kvm/pmu.c | 3 +- arch/x86/kvm/pmu.h | 3 +- arch/x86/kvm/vmx/nested.c | 20 ++- arch/x86/kvm/vmx/vmx.c | 7 + arch/x86/kvm/x86.c | 3 + arch/x86/kvm/xen.c | 144 +++++++++++---------- include/uapi/linux/kvm.h | 3 + tools/testing/selftests/kvm/.gitignore | 91 +------------ tools/testing/selftests/kvm/Makefile | 64 ++++----- .../selftests/kvm/aarch64/page_fault_test.c | 2 +- tools/testing/selftests/kvm/lib/aarch64/ucall.c | 6 +- tools/testing/selftests/kvm/lib/kvm_util.c | 13 +- tools/testing/selftests/kvm/lib/ucall_common.c | 16 ++- tools/testing/selftests/kvm/lib/x86_64/processor.c | 2 +- tools/testing/selftests/kvm/memslot_perf_test.c | 3 + tools/testing/selftests/kvm/x86_64/hyperv_ipi.c | 3 +- .../kvm/x86_64/svm_nested_soft_inject_test.c | 13 +- .../selftests/kvm/x86_64/vmx_tsc_adjust_test.c | 5 - .../testing/selftests/kvm/x86_64/xen_shinfo_test.c | 6 + virt/kvm/kvm_mm.h | 4 - 28 files changed, 290 insertions(+), 287 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (638e373f36 -> f1dad23dab)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 638e373f36 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new f1dad23dab 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits The 1 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 1780 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39712 -> 39884 bytes 04-build_abe-gcc/console.log.xz | Bin 214724 -> 216568 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8500 -> 8384 bytes 07-build_abe-glibc/console.log.xz | Bin 247240 -> 246856 bytes 08-build_abe-gdb/console.log.xz | Bin 40204 -> 39864 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3880 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2552 -> 2756 bytes 11-check_regression/console.log.xz | Bin 5276 -> 5264 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 3 +++ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- sumfiles/gdb.log.xz | Bin 14652 -> 14632 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 46 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page: