Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (06c73b8406 -> 482ef2386f)

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 06c73b8406 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards 6fd64325b3 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 57d210b78e 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards dc86e27d8b 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards d542fbea93 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards b083e206c3 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards d8b32d5e69 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 11bbc344b6 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 9740779427 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards 87b0e3c357 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards 484ae2c794 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 038471c3dc 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards add2c51983 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards 4ff617121d 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards f6b1f5c273 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 2de6f6b80f 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 87431b21bd 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards 85258ccff9 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards 31babdff1a 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards 987027a6e6 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards b54893307c 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 01d418c105 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards 8ac390642c 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards babd59d766 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards b1f1dcc603 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards 587d25e3d9 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards 172ac9ece0 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards 88a7d31a7b 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards 8b8f2b9acb 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 7feb32f02e 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards 52a2f408c8 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards 44168b35de 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 8605852412 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 684f1e35da 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 34d89a669b 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 75f75f96d3 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 8ebcec3f1e 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 2e52e27a81 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards d23ebc22f3 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards 1e62387ceb 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 6757c3dff2 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards db9db621cc 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 2beffaf6be 321: force: #2055: 7: Success after gdb: 2 commits discards 673ab0468c 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 1ad04e5b58 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 81e53036f9 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards a9cd88eb71 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards b1454ff803 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 7aac0be45b 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards a9c2640ad0 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 2b8f8ad04a 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards 9fd54c381e 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards 92446a89c6 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards a92c0afe7b 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 75b1dd7681 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 1c547cfa49 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards e0c6fd4c67 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 39d6883564 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards 3499f1a298 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards 8b9bad0772 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards 1ba2a54f9d 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 85c7d8d3d9 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards f26b9f62ec 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 8104e59cd2 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards ec8acb46a8 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards 3b410eb829 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards 291cf4e5f6 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards a966c3baae 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards 9fde390247 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards 8efd3f9bd7 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards cc833b4a7f 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards 284a28f793 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards 21d0d9c52a 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards 41cdac1b2d 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards 2c61e9adab 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards f9df480dd6 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards 96098a5a61 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards fb1cfcf673 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards 760503abb0 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards f1a2ad133e 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards d088631351 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 504b124812 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards b0d1ea4dd7 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards a9b9cbbde3 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 83ca51c39c 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards 991eaddcc3 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 4ef143d23b 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards b75cb1471d 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards b3065c75fd 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards 642022c39d 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards 6ec597bb32 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards 4cb45ee9e8 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards 62cb965236 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards d16194442e 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 3b12cfeeff 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards 6485674c6f 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards 5a4c4b8bd7 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 57133389d6 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards c6fbdd0319 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards 8b265c0c95 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards 1d0f3728c0 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new a31208a725 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new 13469f9248 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new 660a5a5e58 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new 937af1ae87 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new 4f88bff288 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new b80050d4e1 268: onsuccess: #1997: 7: Success after glibc: 2 commits new bb03c1ffd5 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new 3bf4c8aacc 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 643ba0533d 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new ae63cd7224 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new c7414eacaa 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 0516ef34a5 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 7fb02cc262 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new 5b6ba8b666 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new c4026749f4 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new cb4aeb714a 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new 41f80b5450 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new 1cfcc5fcf6 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 47e100af39 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new 035b101fb3 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new 6ee2cc0634 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 46e7fd7d99 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new 551eedb4c0 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new 4d959f0a11 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new 6d05ff231a 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new bc5ad89bdf 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new 88db57a7ec 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new 08d30d41cb 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new 7962d1c872 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new e7f62f3b0e 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new 54da93256d 293: onsuccess: #2022: 7: Success after gcc: 2 commits new 7bc11e6947 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 7201d447d8 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new ab4f96c654 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new 048eaee2f0 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 208e440fd8 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new 6e952349e5 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new fb79fae16a 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new e8ca7dc0bd 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 7cc059367a 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new 7cac2ee8d9 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new 3a5ad02256 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new 9149afbd31 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 0452469f25 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new 7299022d5e 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new b2dda0439b 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 95de04c6f6 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new b25d7b3e68 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 5e9229fa02 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 782f2fe7c0 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new a8668d8a45 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new c4afef8883 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new cfcf6b15fc 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new e566d42b11 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 261d05cbfb 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new c57b211571 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new d7e91b47b2 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 8f562c6242 320: onsuccess: #2050: 7: Success after gcc: 4 commits new cb18240f9a 321: force: #2055: 7: Success after gdb: 2 commits new 7e62320d6a 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new e2b6045836 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new 161f887fe0 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 967b3f10d3 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new 6f83a688f6 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 12d71b495b 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 8445d563e3 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new afe260c544 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 5c8cc38b23 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new 35d39f21c4 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 94ce56ba56 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new a93aa5d01d 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new 16b958bbcf 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new d4ff581aeb 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new be04452c94 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 34a7a4d4e4 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 64edd537c3 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new da6443b95c 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new c2d2004d1e 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 70d0ec5522 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new 6942ea1058 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new 7dcb7dfd2c 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new 4e1c2d21eb 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new c95d885cee 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new 8eb20636f0 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new d301af4c67 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new ff889fd7d5 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new a9b7388bec 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 00f998b3b0 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 1150090c6f 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new 650979560b 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new 05e279246d 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 48ccd4a199 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 2a58de57fc 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new e2a6540376 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new e8beb4c232 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new 92a96f1be1 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new f7f3a0fc4a 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new dd5e399d5b 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new ff196a8ab5 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new ffae262fe8 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 6d03d05cf5 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 482ef2386f 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 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 (06c73b8406) \ 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 1776 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 31448 -> 31360 bytes 05-build_abe-stage1/console.log.xz | Bin 91556 -> 91196 bytes 07-build_abe-linux/console.log.xz | Bin 8732 -> 8748 bytes 08-build_abe-glibc/console.log.xz | Bin 236460 -> 236772 bytes 09-build_abe-stage2/console.log.xz | Bin 228232 -> 228296 bytes 10-build_abe-gdb/console.log.xz | Bin 38576 -> 38772 bytes 11-build_abe-qemu/console.log.xz | Bin 32544 -> 32344 bytes 12-check_regression/console.log.xz | Bin 3756 -> 3136 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++------ 18 files changed, 53 insertions(+), 53 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (1a6dcb8832 -> 78ae2eff09)

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-aarch64 in repository toolchain/ci/base-artifacts. discards 1a6dcb8832 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards ff494a9555 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 167f596543 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards ecea0af00f 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 5698af0224 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards f3961102da 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards fc9f8aacd8 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 6490049071 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards f3b1499a9e 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 1fca2fdd53 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 45212405f8 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 9b53cc942d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 97a39f2c05 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 96cfb155fe 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 668219f036 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards a5bebaa560 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards fd9bdb286c 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards d0c2c6a342 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 9b8b60dfb4 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards a47aa7ca09 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 182129cdbc 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 8c42d55aa0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 649209d942 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 51682b51f4 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards bd3efce23e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards c45339fb2c 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards fdcd9c00d6 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 6117a823e7 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards b27cfb5341 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards d80b9ada84 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 48c42db822 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 1eac558742 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 326b3ea465 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards f05096f025 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 23d4f2a10a 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 6bb31fdf2d 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 225a9d8363 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards b43db2fc96 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards fb2cc6a0d3 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 754a44bc99 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 44fef0ef89 295: onsuccess: #2545: 1: Success after linux: 10 commits discards eb8162eb7e 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 35f1b0c597 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 125181905e 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards a58a4094fc 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 0cd708874c 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 82a8e0a64c 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 039346369a 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 1b04675e55 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 6b13c9f458 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 41a891a54e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards a3d7f51e26 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 390fe2cec3 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards ac7e24b346 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 6891349b1b 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 108cd13b9e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards bec4bce3bf 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards f3d280ca9c 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards d2677f0e64 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 543ffe80a2 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 644b9022bc 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 6e464a9525 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 8aab58bb22 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 0142366265 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 47a31edee6 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards e201969b27 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 1d1c6359f7 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 1683c14e2d 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 9fc61b9d40 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards bc9311b66d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards e55a4d0be9 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 2da347d9b7 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 5a076ee39b 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards e3e3bb752e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 058403c5d5 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards a2d500dce7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 5451afcc1a 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 626f74f707 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards d89e6b49bf 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 3a772c204e 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 82d902a69d 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 07e926185f 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 65088749d8 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards f0a6f3c8f0 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 3162cdfdf9 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 169dbcd9e6 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards b2158de6a9 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards f0f98a1b7b 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards e7a8e839f6 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 6fb804b3bc 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 1161910e86 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards fff8ea1c50 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 8a84aab4b7 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 71562a6675 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 2f25d0e42e 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 7c00d5073e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 2a67a3cdf9 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards dfb3da9d78 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 31b930eb26 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards a46977e1a6 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards a9310d5616 235: onsuccess: #2483: 1: Success after linux: 108 commits new 06e723120b 235: onsuccess: #2483: 1: Success after linux: 108 commits new c99fdc63d7 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 1f50b5f9ac 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new b2c0fd7763 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new cc33d6a555 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 8e1bec74cb 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 6d51db07b4 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 37abbe17b5 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new d6887e48df 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new b83104d2f7 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new c176390db9 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 1a35bc7569 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new c784262ed8 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new d26e1e64ca 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 8ccaf322d2 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 48ca287750 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 8075e08de1 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 0620c3a31c 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 2f6eca4523 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 199163498b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 76a276deb7 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new a3f07465fd 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new b396d2dba7 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 16fe00ab38 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new a5e58530af 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new c5c2c7066c 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 9596106cb3 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new e15ee828c1 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 68d4ddda30 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new b30b3a3c41 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 9383c4cfcb 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 47fa4aa0ac 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new dd26013306 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 9bfe05733a 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 6087cf22d2 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 063fd898b6 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 0c2943e2a4 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 29ea24b459 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 11b987768f 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 96abe7da29 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 1f0c95360b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new f95f060276 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 63fae85da4 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new a7cc87ac4d 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new e6acc3ffcc 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 72f2d8fc0b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 48233a0a54 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new bd88715749 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 52263ac7fc 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 87eb233f5b 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 0211ec041e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new bffdbd4b70 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 8d0d2e9565 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 77db83544e 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new f11e4bd850 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 7f80bffd89 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 740995a93c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new ee7df058f5 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 17d1420638 293: onsuccess: #2542: 1: Success after gcc: 5 commits new a4a4455796 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 0db33d68fc 295: onsuccess: #2545: 1: Success after linux: 10 commits new 9aba929908 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new ead40c5332 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 9b6f42460b 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 6de5dba534 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new dfc924a612 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new c5a80539ce 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 8c68598791 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new bfa2bd4699 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 20aaafe371 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 2925bd0bd8 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 79d1c4df22 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 2e3a3eba60 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 26a613e4ec 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new c73aa74ad4 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 90a4656b21 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new ee82fdca43 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 0584e0b1e9 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 059b6850e4 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new d7b97ae2f9 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 9f5da206f3 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new e16dd1e228 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new f706c97b09 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new c9589e5a5c 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 0c9c1e933f 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 9dd0848cbe 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new cac1caa261 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 24f27c2c89 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 277d7b46f5 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new ab7bd417c4 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new c9f3709828 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 663e6e6407 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new d91eb14564 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 513722c5e8 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 574e54dcd3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new f7391351b1 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new dc5d3feda0 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new bf7743aeb9 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new d32127812b 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new a1b0105028 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new ba4c3c8cfa 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 78ae2eff09 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] 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 (1a6dcb8832) \ 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 1760 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31968 -> 31756 bytes 04-build_abe-stage1/console.log.xz | Bin 73368 -> 73068 bytes 06-build_abe-linux/console.log.xz | Bin 8736 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 245656 -> 244968 bytes 08-build_abe-stage2/console.log.xz | Bin 204648 -> 204136 bytes 09-build_abe-gdb/console.log.xz | Bin 39300 -> 39060 bytes 10-build_abe-qemu/console.log.xz | Bin 32484 -> 32872 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2812 -> 2724 bytes 13-check_regression/console.log.xz | Bin 7132 -> 6184 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 116 +- 13-check_regression/results.compare | 54 +- 13-check_regression/results.compare2 | 87 +- 13-check_regression/results.regressions | 54 +- 14-update_baseline/console.log | 62 +- 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 | 118 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 54 +- sumfiles/g++.log.xz | Bin 3402424 -> 3429556 bytes sumfiles/g++.sum | 44 +- sumfiles/gcc.log.xz | Bin 3040476 -> 3044636 bytes sumfiles/gcc.sum | 4220 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037496 -> 1047844 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214572 -> 214616 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432144 -> 437092 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2392 insertions(+), 2500 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-defconfig updated (2595f93332 -> bf72d75a0b)

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_kernel/llvm-master-aarch64-next-defconfig in repository toolchain/ci/base-artifacts. from 2595f93332 45: onsuccess: #521: all: Success after linux: 4316 commits new bf72d75a0b 46: onsuccess: #522: boot: Success after binutils/llvm/linux [...] 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 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31932 -> 31656 bytes 04-build_kernel_llvm/console.log.xz | Bin 64672 -> 66032 bytes 05-build_abe-qemu/console.log.xz | Bin 31712 -> 32812 bytes 06-build_linux/console.log.xz | Bin 2996 -> 3112 bytes 07-boot_linux/console.log.xz | Bin 5912 -> 6152 bytes 08-check_regression/console.log.xz | Bin 2804 -> 4148 bytes 08-check_regression/mail-body.txt | 7 ++++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 9 +++++---- mail/mail-subject.txt | 2 +- manifest.sh | 29 ++++++++++++++++------------- results | 4 +++- 19 files changed, 35 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (eaa13962f22 -> 2025c82b954)

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 binutils-gdb. from eaa13962f22 sim: build: drop depdir subdir hack new 9a7472d7c59 sim: igen: simplify build logic a little new 2025c82b954 sim: m32r: fix typos in stamp depends The 2 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: sim/Makefile.am | 3 +- sim/Makefile.in | 568 ++++++++++++++++++++++++++---------------------------- sim/configure | 50 +---- sim/configure.ac | 10 +- sim/igen/local.mk | 2 +- sim/m32r/local.mk | 4 +- 6 files changed, 279 insertions(+), 358 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-aarch64-check_bootstrap updated (04c6a4edfb -> 249aca2008)

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_bootstrap/release-aarch64-check_bootstrap in repository toolchain/ci/base-artifacts. from 04c6a4edfb 44: onsuccess: #167: 1: Success after binutils/gcc: 9 commits new 249aca2008 45: onsuccess: #168: 1: Success after binutils/gcc: 6 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 1748 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 37800 -> 38748 bytes 04-build_abe-bootstrap/console.log.xz | Bin 262944 -> 262368 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3884 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2552 -> 2316 bytes 07-check_regression/console.log.xz | Bin 5396 -> 5336 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 10 +- 07-check_regression/mail-body.txt | 68 +- 07-check_regression/results.compare | 32 +- 07-check_regression/results.compare2 | 54 +- 07-check_regression/results.regressions | 32 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 32 +- sumfiles/g++.log.xz | Bin 3595408 -> 3586572 bytes sumfiles/g++.sum | 152 +- sumfiles/gcc.log.xz | Bin 3126804 -> 3141680 bytes sumfiles/gcc.sum | 4360 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1086752 -> 1081556 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2348 -> 2344 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 208396 -> 208380 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2728 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451368 -> 451560 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2513 insertions(+), 2405 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allyesconfig updated (45f3a3c976 -> 431b59f730)

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_kernel/gnu-master-aarch64-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 45f3a3c976 37: onsuccess: #533: 33: Success after binutils/gcc/qemu: 31 [...] new 431b59f730 38: onsuccess: #534: 33: Success after binutils/gcc/linux/qe [...] 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 1784 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 32656 -> 32372 bytes 04-build_abe-stage1/console.log.xz | Bin 74012 -> 74804 bytes 05-build_abe-qemu/console.log.xz | Bin 32344 -> 33128 bytes 06-build_linux/console.log.xz | Bin 5148 -> 6036 bytes 08-check_regression/console.log.xz | Bin 4100 -> 4540 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-defconfig updated (9ae533556d -> 8ce6121b25)

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_kernel/llvm-master-aarch64-mainline-defconfig in repository toolchain/ci/base-artifacts. from 9ae533556d 37: onsuccess: #506: boot: Success after binutils/llvm/linux [...] new 8ce6121b25 38: onsuccess: #507: boot: Success after binutils/llvm/linux [...] 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 1960 -> 1968 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 32020 -> 32256 bytes 04-build_kernel_llvm/console.log.xz | Bin 66268 -> 64308 bytes 05-build_abe-qemu/console.log.xz | Bin 31864 -> 32884 bytes 06-build_linux/console.log.xz | Bin 3120 -> 3176 bytes 07-boot_linux/console.log.xz | Bin 6144 -> 6184 bytes 08-check_regression/console.log.xz | Bin 4332 -> 4516 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 20 files changed, 30 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-fujitsu_speed-cpu2017rate/gnu-aarch64-master-O2 updated (bbecb956ba -> 789b4fbe22)

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-fujitsu_speed-cpu2017rate/gnu-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from bbecb956ba 37: force: #8: 1: [TCWG CI] 521.wrf_r slowed down by 5% afte [...] new 789b4fbe22 38: onsuccess: #9: 1: [TCWG CI] No change after gcc: 54 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 1932 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 32512 -> 32420 bytes 04-build_abe-stage1/console.log.xz | Bin 74076 -> 74764 bytes 06-build_abe-linux/console.log.xz | Bin 8092 -> 8132 bytes 07-build_abe-glibc/console.log.xz | Bin 246928 -> 247280 bytes 08-build_abe-stage2/console.log.xz | Bin 181524 -> 181428 bytes 09-benchmark/benchmark-build.log | 110 +- 09-benchmark/benchmark.log | 108 +- 09-benchmark/console.log.xz | Bin 3812 -> 3884 bytes 10-check_regression/console.log.xz | Bin 14160 -> 13048 bytes .../csv-results-vs-first-1/md5sum.csv | 2448 +- .../csv-results-vs-first-1/perf.csv | 2807 +- .../csv-results-vs-first-1/results.csv | 20677 +- .../csv-results-vs-first-1/size.csv | 502140 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 24288 +- .../csv-results-vs-first-1/vect.csv | 636 +- .../csv-results-vs-prev-0/md5sum.csv | 2500 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2779 +- .../csv-results-vs-prev-0/results.csv | 21643 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 442635 ++++++++------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 24396 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 628 +- .../csv-results-vs-prev-1/md5sum.csv | 2448 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2807 +- .../csv-results-vs-prev-1/results.csv | 20677 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 502140 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 24288 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 636 +- 10-check_regression/exe.regression | 1 - 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 3 - 10-check_regression/mail-body.txt | 3 - 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 2787 +- 10-check_regression/results-vs-first-internal.csv | 190 +- 10-check_regression/results-vs-first.csv | 190 +- 10-check_regression/results-vs-first.log | 1018 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-compare.csv | 10 +- 10-check_regression/results-vs-prev-full.csv | 2883 +- 10-check_regression/results-vs-prev-internal.csv | 190 +- 10-check_regression/results-vs-prev.csv | 190 +- 10-check_regression/results-vs-prev.log | 1292 +- 10-check_regression/results.regressions | 5 - 10-check_regression/skipped-symbols.txt | 41 +- 10-check_regression/trigger-bisect | 3 - 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../500.perlbench_r/results-metrics.json | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../503.bwaves_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../507.cactuBSSN_r/results-metadata.json | 10 +- .../507.cactuBSSN_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 10 +- .../510.parest_r/results-metadata.json | 10 +- .../511.povray_r/results-metadata.json | 10 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 10 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../527.cam4_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 10 +- .../538.imagick_r/results-metrics.json | 2 +- .../541.leela_r/results-metadata.json | 10 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../squad-vs-first/544.nab_r/results-metrics.json | 2 +- .../548.exchange2_r/results-metadata.json | 10 +- .../549.fotonik3d_r/results-metadata.json | 10 +- .../554.roms_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 104 +- dashboard/squad-vs-first/summary-annotation.txt | 1 - git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1050 - jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 5 - results_id | 2 +- 101 files changed, 807550 insertions(+), 803652 deletions(-) delete mode 100644 10-check_regression/exe.regression delete mode 100644 10-check_regression/results.regressions delete mode 100644 10-check_regression/trigger-bisect delete mode 100644 10-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allyesconfig updated (035ff14613 -> e36a0061b0)

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_kernel/gnu-release-aarch64-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 035ff14613 36: onsuccess: #391: all: Success after binutils/gcc/qemu: 1 [...] new e36a0061b0 37: onsuccess: #392: all: Success after binutils/gcc/linux/q [...] 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 1796 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 30916 -> 31264 bytes 04-build_abe-stage1/console.log.xz | Bin 69136 -> 68928 bytes 05-build_abe-qemu/console.log.xz | Bin 31224 -> 32852 bytes 06-build_linux/console.log.xz | Bin 3448 -> 3428 bytes 07-boot_linux/console.log.xz | Bin 576 -> 580 bytes 08-check_regression/console.log.xz | Bin 3692 -> 4276 bytes 09-update_baseline/console.log | 16 ++++++++-------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 18 files changed, 31 insertions(+), 31 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-flang_speed-cpu2017rate/llvm-aarch64-master-O2 updated (989d013e25 -> 0ee8677076)

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-flang_speed-cpu2017rate/llvm-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from 989d013e25 0: init: #56: -3: Success after baseline build: no new commits new 0ee8677076 1: onsuccess: #57: -3: Success after binutils/gcc/linux/glib [...] 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 2500 -> 1980 bytes 01-reset_artifacts/patch-env.sh | 2 -- 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39896 -> 39596 bytes 04-build_abe-stage1/console.log.xz | Bin 82192 -> 82128 bytes 06-build_abe-linux/console.log.xz | Bin 8720 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 245216 -> 244404 bytes 08-build_abe-stage2/console.log.xz | Bin 187796 -> 190968 bytes 09-build_llvm-true-true-cflags-/console.log.xz | Bin 110164 -> 110140 bytes 10-benchmark/console.log.xz | Bin 932 -> 932 bytes 11-check_regression/console.log.xz | Bin 2420 -> 4752 bytes 11-check_regression/mail-body.txt | 16 +++++++++- 12-update_baseline/console.log | 9 ++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 18 +++++++++-- mail/mail-subject.txt | 2 +- manifest.sh | 40 ++++++++++++------------- 23 files changed, 68 insertions(+), 33 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page: