Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-defconfig updated (38fed2c761 -> daa89eaae2)

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-arm-next-defconfig in repository toolchain/ci/base-artifacts. from 38fed2c761 33: onsuccess: #407: boot: Success after binutils/gcc/linux/ [...] new daa89eaae2 34: onsuccess: #408: boot: Success after binutils/gcc/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 1748 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30392 -> 30844 bytes 04-build_abe-stage1/console.log.xz | Bin 87040 -> 86932 bytes 05-build_abe-qemu/console.log.xz | Bin 31088 -> 32132 bytes 06-build_linux/console.log.xz | Bin 3080 -> 3072 bytes 07-boot_linux/console.log.xz | Bin 5616 -> 5620 bytes 08-check_regression/console.log.xz | Bin 4040 -> 4024 bytes 08-check_regression/mail-body.txt | 4 ++-- 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 | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 19 files changed, 28 insertions(+), 28 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-next-allmodconfig updated (0315202a74 -> 377b92b634)

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-next-allmodconfig in repository toolchain/ci/base-artifacts. from 0315202a74 38: onsuccess: #568: 33: Success after binutils/gcc/linux/qe [...] new 377b92b634 39: onsuccess: #569: 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 1788 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31876 -> 31776 bytes 04-build_abe-stage1/console.log.xz | Bin 73140 -> 73136 bytes 05-build_abe-qemu/console.log.xz | Bin 31688 -> 32736 bytes 06-build_linux/console.log.xz | Bin 4956 -> 4796 bytes 08-check_regression/console.log.xz | Bin 4388 -> 4280 bytes 09-update_baseline/console.log | 9 --------- 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, 23 insertions(+), 32 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-release-aarch64-lts-defconfig updated (d7a3b660b8 -> 647122ed43)

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-release-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from d7a3b660b8 35: onsuccess: #278: boot: Success after binutils/llvm/qemu: [...] new 647122ed43 36: onsuccess: #279: 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 2012 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31068 -> 31192 bytes 04-build_kernel_llvm/console.log.xz | Bin 65600 -> 63052 bytes 05-build_abe-qemu/console.log.xz | Bin 32056 -> 32304 bytes 06-build_linux/console.log.xz | Bin 3564 -> 3964 bytes 07-boot_linux/console.log.xz | Bin 6068 -> 6048 bytes 08-check_regression/console.log.xz | Bin 3636 -> 3996 bytes 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 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-release-aarch64-mainline-allnoconfig updated (c99ece41ca -> cd2de48a52)

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-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from c99ece41ca 35: onsuccess: #459: boot: Success after binutils/gcc/linux/ [...] new cd2de48a52 36: onsuccess: #460: boot: Success after binutils/gcc/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 1792 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2820 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31112 -> 31228 bytes 04-build_abe-stage1/console.log.xz | Bin 69356 -> 68552 bytes 05-build_abe-qemu/console.log.xz | Bin 32228 -> 32820 bytes 06-build_linux/console.log.xz | Bin 3108 -> 3036 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4136 -> 4064 bytes 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, 23 insertions(+), 23 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_build/master-arm updated (14e7b7758a -> 06c73b8406)

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 14e7b7758a 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 96733ed223 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards 7d035cc962 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards c9ab506da7 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards 25e49e6b90 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards c0d1f28691 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 2721f252ff 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 8586d6e852 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards 04873dbc4b 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards f541756191 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 0a5e655873 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards 3acd19c13a 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards 3453262545 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 55dc86d3b5 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 7cb833f18c 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 5dda83a012 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards 1fa508a7d4 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards 67e9ad5e84 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards f720ba485e 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards 7e59a247bd 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 96cf83095b 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards 25fc4a1713 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards ab02150d69 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards ac6f8d6338 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards 1a307cac5f 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards dfb7182d59 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards 88f3a32a94 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards 52b16c56eb 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 2a5274fd89 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards 68e2ca8aae 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards e5b244a37c 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 895bb7e575 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 6318fb48e0 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 10e3f3cef3 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 843a5a4084 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 6d801a08cc 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 467c992ab0 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 7068cb589f 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards 41381252ff 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 46326118f4 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 0f856a757f 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 93c40d60c7 321: force: #2055: 7: Success after gdb: 2 commits discards 44bbc17f9f 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 876d4c9ca0 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 0167f35ef9 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards 21d4b988ea 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards 72692d6756 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 9e1c82760c 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards a80140de0f 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 706934dbe2 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards 9027fa9397 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards e76e140b94 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards f727afd0a8 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards bdcc0aefde 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 61fcccfae4 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 3cefc76244 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 2251023877 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards fdb4ba5961 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards 9216ea05f0 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards eb0abe498f 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 13beffa15e 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards 96d1152069 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 66a5e589e8 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards 47b2757b03 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards 19a51664d9 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards 073d5f16eb 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards 3bdef00161 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards e42dcd59ac 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards e6931f1c3a 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards 2355626dee 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards 32e819837e 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards 00ac25a567 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards 1678853237 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards 908d1a317f 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards f568d8e61f 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards 4d2a407648 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards 31294e083b 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards f2d7eb6239 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards 3d47e1a553 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards d1e52fa8d3 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 91654fdb22 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards 3bb990e20e 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards ba890e2d34 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards f76335ff42 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards 454ada1189 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 7c69d8c69d 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 8078d6a72d 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards c897242009 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards ecec2e9f9a 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards e43a8b48e7 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards 1caaa1a33b 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards 23dd9601fd 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards 694c0c8a7c 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 173d476e35 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards 7fb3a1cc86 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards 2029aba6b0 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards f61a5f2791 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards c9b9602028 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards 634de54a5f 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards 93aee4d1d8 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards 3b0b18446d 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new ac1e13a390 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new 1d0f3728c0 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new 8b265c0c95 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new c6fbdd0319 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new 57133389d6 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new 5a4c4b8bd7 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new 6485674c6f 268: onsuccess: #1997: 7: Success after glibc: 2 commits new 3b12cfeeff 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new d16194442e 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 62cb965236 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new 4cb45ee9e8 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new 6ec597bb32 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 642022c39d 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new b3065c75fd 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new b75cb1471d 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new 4ef143d23b 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new 991eaddcc3 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new 83ca51c39c 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new a9b9cbbde3 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new b0d1ea4dd7 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new 504b124812 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new d088631351 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new f1a2ad133e 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new 760503abb0 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new fb1cfcf673 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new 96098a5a61 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new f9df480dd6 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new 2c61e9adab 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new 41cdac1b2d 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new 21d0d9c52a 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new 284a28f793 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new cc833b4a7f 293: onsuccess: #2022: 7: Success after gcc: 2 commits new 8efd3f9bd7 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 9fde390247 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new a966c3baae 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new 291cf4e5f6 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 3b410eb829 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new ec8acb46a8 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new 8104e59cd2 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new f26b9f62ec 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 85c7d8d3d9 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new 1ba2a54f9d 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new 8b9bad0772 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new 3499f1a298 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 39d6883564 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new e0c6fd4c67 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new 1c547cfa49 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 75b1dd7681 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new a92c0afe7b 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 92446a89c6 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 9fd54c381e 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new 2b8f8ad04a 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new a9c2640ad0 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 7aac0be45b 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new b1454ff803 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new a9cd88eb71 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 81e53036f9 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new 1ad04e5b58 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 673ab0468c 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 2beffaf6be 321: force: #2055: 7: Success after gdb: 2 commits new db9db621cc 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 6757c3dff2 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new 1e62387ceb 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new d23ebc22f3 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new 2e52e27a81 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 8ebcec3f1e 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 75f75f96d3 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 34d89a669b 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 684f1e35da 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new 8605852412 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 44168b35de 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new 52a2f408c8 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new 7feb32f02e 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new 8b8f2b9acb 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 88a7d31a7b 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 172ac9ece0 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 587d25e3d9 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new b1f1dcc603 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new babd59d766 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 8ac390642c 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new 01d418c105 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new b54893307c 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new 987027a6e6 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 31babdff1a 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new 85258ccff9 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new 87431b21bd 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 2de6f6b80f 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new f6b1f5c273 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 4ff617121d 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new add2c51983 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new 038471c3dc 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new 484ae2c794 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 87b0e3c357 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 9740779427 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new 11bbc344b6 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new d8b32d5e69 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new b083e206c3 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new d542fbea93 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new dc86e27d8b 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 57d210b78e 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 6fd64325b3 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 06c73b8406 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] 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 (14e7b7758a) \ 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 1764 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 31608 -> 31448 bytes 05-build_abe-stage1/console.log.xz | Bin 91792 -> 91556 bytes 07-build_abe-linux/console.log.xz | Bin 8780 -> 8732 bytes 08-build_abe-glibc/console.log.xz | Bin 236800 -> 236460 bytes 09-build_abe-stage2/console.log.xz | Bin 228700 -> 228232 bytes 10-build_abe-gdb/console.log.xz | Bin 39080 -> 38576 bytes 11-build_abe-qemu/console.log.xz | Bin 32028 -> 32544 bytes 12-check_regression/console.log.xz | Bin 4024 -> 3756 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ 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 | 34 +++++++++--------- 19 files changed, 58 insertions(+), 58 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-allmodconfig updated (99625d3577 -> 93289e7e7c)

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-allmodconfig in repository toolchain/ci/base-artifacts. from 99625d3577 54: onsuccess: #541: all: Success after binutils/llvm/linux/ [...] new 93289e7e7c 55: onsuccess: #542: all: 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 1768 -> 1984 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 32020 -> 32628 bytes 04-build_kernel_llvm/console.log.xz | Bin 65964 -> 66044 bytes 05-build_abe-qemu/console.log.xz | Bin 31524 -> 32996 bytes 06-build_linux/console.log.xz | Bin 3100 -> 3180 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4276 -> 4416 bytes 08-check_regression/mail-body.txt | 2 +- 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 +- 19 files changed, 26 insertions(+), 26 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_bootstrap/master-aarch64-bootstrap_O1 updated (1283038ed2 -> 5689da1ed2)

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_bootstrap/master-aarch64-bootstrap_O1 in repository toolchain/ci/base-artifacts. discards 1283038ed2 166: onsuccess: #571: 2: Success after binutils/gcc: 45 commits discards a970cddb4e 165: onsuccess: #570: 2: Success after binutils/gcc: 44 commits discards 4a2a0f5d6d 164: onsuccess: #569: 2: Success after binutils/gcc: 115 commits discards 8194461d10 163: onsuccess: #568: 2: Success after binutils/gcc: 4 commits discards 3c0036425d 162: onsuccess: #567: 2: Success after binutils/gcc: 6 commits discards 395e563cde 161: onsuccess: #566: 2: Success after binutils/gcc: 27 commits discards 2c03e63fab 160: onsuccess: #565: 2: Success after binutils/gcc: 51 commits discards 520fad1123 159: onsuccess: #564: 2: Success after binutils/gcc: 36 commits discards deb5eaa30b 158: onsuccess: #563: 2: Success after binutils/gcc: 53 commits discards 6576d06d7e 157: onsuccess: #562: 1: Success after gcc: 4 commits discards 3d21dc7fa3 156: force: #561: 1: Failure after basepoints/gcc-13-4953-g3 [...] discards 028fa0c4d4 155: force: #560: 2: Success after gcc: 6 commits discards f2ea6c81e3 154: onsuccess: #558: 2: Success after binutils: 19 commits discards 4c5f77aaac 153: onsuccess: #556: 2: Success after binutils/gcc: 18 commits discards d79782c7c0 152: onsuccess: #555: 2: Success after binutils/gcc: 18 commits discards 7d0807646f 151: onsuccess: #554: 2: Success after binutils/gcc: 11 commits discards 033b506a73 150: onsuccess: #553: 2: Success after binutils/gcc: 20 commits discards bbc38fc65a 149: onsuccess: #552: 2: Success after binutils/gcc: 8 commits discards d481a00bd8 148: onsuccess: #551: 2: Success after binutils/gcc: 30 commits discards fb7c020a0c 147: onsuccess: #550: 2: Success after binutils/gcc: 6 commits discards f35f906eff 146: onsuccess: #549: 2: Success after binutils/gcc: 24 commits discards 998f17a0c7 145: onsuccess: #548: 2: Success after binutils/gcc: 8 commits discards da0837ff6e 144: onsuccess: #547: 2: Success after binutils/gcc: 74 commits discards 892085a56f 143: onsuccess: #546: 2: Success after binutils/gcc: 58 commits discards 107882c7bd 142: onsuccess: #545: 2: Success after binutils/gcc: 67 commits discards 187b2696e3 141: onsuccess: #544: 2: Success after binutils/gcc: 14 commits discards 6b953eee40 140: onsuccess: #543: 2: Success after binutils/gcc: 56 commits discards a5af89f159 139: onsuccess: #542: 2: Success after binutils/gcc: 9 commits discards 38d7147bcd 138: onsuccess: #541: 2: Success after binutils/gcc: 14 commits discards 54206e011b 137: onsuccess: #540: 2: Success after binutils/gcc: 39 commits discards 04c3678389 136: onsuccess: #539: 1: Success after binutils/gcc: 72 commits discards be3cc01b31 135: onsuccess: #538: 1: Success after binutils: 10 commits discards db8e9757ba 134: force: #537: 1: Failure after gdb-12-branchpoint-3046-g [...] discards 254183e98d 133: force: #536: 2: Success after binutils: 4 commits discards 8d31082f85 132: onsuccess: #534: 2: Success after gcc: 66 commits discards d8d46af11f 131: onsuccess: #531: 2: Success after binutils/gcc: 47 commits discards fe2a8fc35e 130: onsuccess: #530: 2: Success after binutils/gcc: 12 commits discards ceee3ff970 129: onsuccess: #529: 2: Success after binutils/gcc: 3 commits discards f2b8f32bb5 128: onsuccess: #528: 2: Success after binutils/gcc: 31 commits discards 2223cffdb9 127: onsuccess: #527: 2: Success after binutils/gcc: 33 commits discards 3a726d47d2 126: onsuccess: #526: 2: Success after binutils/gcc: 27 commits discards 224184e39b 125: onsuccess: #525: 2: Success after binutils/gcc: 47 commits discards 7d57e7ea83 124: onsuccess: #524: 2: Success after binutils/gcc: 34 commits discards 84f0c22f80 123: onsuccess: #523: 2: Success after binutils/gcc: 13 commits discards e503b515bb 122: onsuccess: #522: 2: Success after binutils/gcc: 6 commits discards ba6c618cb3 121: onsuccess: #521: 2: Success after binutils/gcc: 31 commits discards cbe669eccf 120: onsuccess: #520: 2: Success after binutils/gcc: 54 commits discards 37e79a58a9 119: onsuccess: #519: 2: Success after binutils/gcc: 41 commits discards 9a4851e782 118: onsuccess: #518: 2: Success after binutils/gcc: 25 commits discards caae245a8f 117: onsuccess: #517: 2: Success after binutils/gcc: 117 commits discards a963d638df 116: onsuccess: #516: 2: Success after binutils/gcc: 7 commits discards 92d4c8b7a7 115: onsuccess: #515: 2: Success after binutils/gcc: 7 commits discards 5bbc79dc61 114: onsuccess: #514: 2: Success after binutils/gcc: 20 commits discards 307318fe35 113: onsuccess: #513: 2: Success after binutils/gcc: 43 commits discards b8d2b7e9c2 112: onsuccess: #512: 2: Success after binutils/gcc: 29 commits discards 95b131e27b 111: onsuccess: #511: 1: Success after gcc: 4 commits discards a1bf8c8e70 110: force: #510: 1: Failure after basepoints/gcc-13-4252-ga [...] discards c8f8220897 109: force: #509: 2: Success after gcc: 28 commits discards bdb6afcb3b 108: onsuccess: #507: 2: Success after binutils: 15 commits discards a601b03f2b 107: onsuccess: #505: 2: Success after binutils/gcc: 53 commits discards ad6d721591 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits discards 313dfa37dd 105: onsuccess: #503: 2: Success after binutils/gcc: 56 commits discards 9324376963 104: onsuccess: #501: 2: Success after binutils/gcc: 38 commits discards d5458ae847 103: onsuccess: #500: 2: Success after binutils/gcc: 65 commits discards 2d24097599 102: onsuccess: #498: 2: Success after binutils/gcc: 162 commits discards 61bc61e7b8 101: onsuccess: #497: 1: Success after binutils/gcc: 15 commits discards 67782a84fa 100: onsuccess: #496: 1: Success after binutils/gcc: 23 commits discards 0175f7dff7 99: onsuccess: #495: 1: Success after baseline build: no new [...] discards 3bb9118c1a 98: force: #494: 1: Failure after basepoints/gcc-13-3918-gba [...] discards 4889d3a919 97: force: #493: 2: Success after gcc: 32 commits discards 242430a265 96: onsuccess: #491: 2: Success after binutils: 25 commits discards 68fc28bdcd 95: onsuccess: #489: 2: Success after binutils/gcc: 49 commits discards 276a08566f 94: onsuccess: #488: 2: Success after binutils/gcc: 63 commits discards 6442cb02c0 93: onsuccess: #487: 2: Success after binutils/gcc: 66 commits discards 2b86d5397b 92: onsuccess: #486: 2: Success after binutils/gcc: 73 commits discards 2bf943cc38 91: onsuccess: #485: 2: Success after binutils/gcc: 12 commits discards fd2b26bda4 90: onsuccess: #484: 2: Success after binutils/gcc: 24 commits discards 8980227774 89: onsuccess: #483: 2: Success after binutils/gcc: 64 commits discards 73eef019d2 88: onsuccess: #482: 2: Success after binutils/gcc: 49 commits discards 976f3b343e 87: onsuccess: #481: 2: Success after binutils/gcc: 27 commits discards 80f2e1db0e 86: onsuccess: #480: 2: Success after binutils/gcc: 28 commits discards 80abb1dbec 85: onsuccess: #479: 2: Success after binutils/gcc: 43 commits discards 88981bbb9e 84: onsuccess: #478: 2: Success after binutils/gcc: 3 commits discards ccdf5c4b27 83: onsuccess: #477: 2: Success after binutils/gcc: 24 commits discards 19aad06aea 82: onsuccess: #476: 2: Success after binutils/gcc: 33 commits discards c0f5367aef 81: onsuccess: #475: 2: Success after binutils/gcc: 29 commits discards 4513678154 80: onsuccess: #474: 2: Success after binutils/gcc: 34 commits discards 72d4142a74 79: onsuccess: #473: 2: Success after binutils/gcc: 35 commits discards 625580b12e 78: onsuccess: #472: 2: Success after binutils/gcc: 43 commits discards cea398b384 77: onsuccess: #471: 2: Success after binutils/gcc: 6 commits discards 6874f65353 76: onsuccess: #470: 2: Success after binutils/gcc: 6 commits discards 4b97f8929d 75: onsuccess: #469: 2: Success after binutils/gcc: 38 commits discards cb7580ec58 74: onsuccess: #468: 2: Success after binutils/gcc: 46 commits discards b8ed9d26d7 73: onsuccess: #467: 2: Success after binutils/gcc: 49 commits discards 0503e036fd 72: onsuccess: #466: 2: Success after binutils/gcc: 43 commits discards 43b55a8313 71: onsuccess: #465: 2: Success after binutils/gcc: 46 commits discards 55f61ad66c 70: onsuccess: #464: 2: Success after binutils/gcc: 9 commits discards bb2a254daa 69: onsuccess: #463: 2: Success after binutils/gcc: 6 commits discards c5f1fe1cdc 68: onsuccess: #462: 2: Success after binutils/gcc: 53 commits discards effe842ca3 67: onsuccess: #461: 2: Success after binutils/gcc: 27 commits discards a7cfd65363 66: onsuccess: #460: 2: Success after binutils/gcc: 41 commits new afbd61c3f5 66: onsuccess: #460: 2: Success after binutils/gcc: 41 commits new 85c9850d4e 67: onsuccess: #461: 2: Success after binutils/gcc: 27 commits new 440dc5248a 68: onsuccess: #462: 2: Success after binutils/gcc: 53 commits new 28a542e109 69: onsuccess: #463: 2: Success after binutils/gcc: 6 commits new 5aa16fb513 70: onsuccess: #464: 2: Success after binutils/gcc: 9 commits new 41b94eaca7 71: onsuccess: #465: 2: Success after binutils/gcc: 46 commits new 09515a83c3 72: onsuccess: #466: 2: Success after binutils/gcc: 43 commits new 98760cf5b2 73: onsuccess: #467: 2: Success after binutils/gcc: 49 commits new 63109e68ad 74: onsuccess: #468: 2: Success after binutils/gcc: 46 commits new b41185af0f 75: onsuccess: #469: 2: Success after binutils/gcc: 38 commits new 3529ee0368 76: onsuccess: #470: 2: Success after binutils/gcc: 6 commits new b6330404e3 77: onsuccess: #471: 2: Success after binutils/gcc: 6 commits new 7a7cc48c33 78: onsuccess: #472: 2: Success after binutils/gcc: 43 commits new f09eb4602c 79: onsuccess: #473: 2: Success after binutils/gcc: 35 commits new c5ddd5315f 80: onsuccess: #474: 2: Success after binutils/gcc: 34 commits new 8537c378e3 81: onsuccess: #475: 2: Success after binutils/gcc: 29 commits new ee41da4416 82: onsuccess: #476: 2: Success after binutils/gcc: 33 commits new 023d0af310 83: onsuccess: #477: 2: Success after binutils/gcc: 24 commits new 5dd08d4daf 84: onsuccess: #478: 2: Success after binutils/gcc: 3 commits new a45464fc88 85: onsuccess: #479: 2: Success after binutils/gcc: 43 commits new e33b864a98 86: onsuccess: #480: 2: Success after binutils/gcc: 28 commits new 40258b4ba6 87: onsuccess: #481: 2: Success after binutils/gcc: 27 commits new d934835437 88: onsuccess: #482: 2: Success after binutils/gcc: 49 commits new a03480560b 89: onsuccess: #483: 2: Success after binutils/gcc: 64 commits new 1b71dca9c0 90: onsuccess: #484: 2: Success after binutils/gcc: 24 commits new 708e3a7c6d 91: onsuccess: #485: 2: Success after binutils/gcc: 12 commits new 26e834ef40 92: onsuccess: #486: 2: Success after binutils/gcc: 73 commits new fde297b8ae 93: onsuccess: #487: 2: Success after binutils/gcc: 66 commits new 954debbb80 94: onsuccess: #488: 2: Success after binutils/gcc: 63 commits new ef00d83cd3 95: onsuccess: #489: 2: Success after binutils/gcc: 49 commits new 0588c3cf2b 96: onsuccess: #491: 2: Success after binutils: 25 commits new c99689049a 97: force: #493: 2: Success after gcc: 32 commits new bceb174a56 98: force: #494: 1: Failure after basepoints/gcc-13-3918-gba [...] new 78359a56f8 99: onsuccess: #495: 1: Success after baseline build: no new [...] new e0dd5c78fe 100: onsuccess: #496: 1: Success after binutils/gcc: 23 commits new b93a55d527 101: onsuccess: #497: 1: Success after binutils/gcc: 15 commits new 55e746e38a 102: onsuccess: #498: 2: Success after binutils/gcc: 162 commits new 2d107c4df9 103: onsuccess: #500: 2: Success after binutils/gcc: 65 commits new a5fb7b6760 104: onsuccess: #501: 2: Success after binutils/gcc: 38 commits new 6e3f5b5622 105: onsuccess: #503: 2: Success after binutils/gcc: 56 commits new 155f00a984 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits new b4e24a3f83 107: onsuccess: #505: 2: Success after binutils/gcc: 53 commits new d7b4585745 108: onsuccess: #507: 2: Success after binutils: 15 commits new 4fd22b1f94 109: force: #509: 2: Success after gcc: 28 commits new 359f950509 110: force: #510: 1: Failure after basepoints/gcc-13-4252-ga [...] new 4579a83e88 111: onsuccess: #511: 1: Success after gcc: 4 commits new ae1fcef5f1 112: onsuccess: #512: 2: Success after binutils/gcc: 29 commits new 72c44c22fa 113: onsuccess: #513: 2: Success after binutils/gcc: 43 commits new 3e7bd2686f 114: onsuccess: #514: 2: Success after binutils/gcc: 20 commits new ba6dad3a6a 115: onsuccess: #515: 2: Success after binutils/gcc: 7 commits new 5f386d6e59 116: onsuccess: #516: 2: Success after binutils/gcc: 7 commits new 605e3caff1 117: onsuccess: #517: 2: Success after binutils/gcc: 117 commits new 57bbef022e 118: onsuccess: #518: 2: Success after binutils/gcc: 25 commits new 040c1bab31 119: onsuccess: #519: 2: Success after binutils/gcc: 41 commits new 34a51540b0 120: onsuccess: #520: 2: Success after binutils/gcc: 54 commits new 4bbaf81d52 121: onsuccess: #521: 2: Success after binutils/gcc: 31 commits new 82e57225ea 122: onsuccess: #522: 2: Success after binutils/gcc: 6 commits new d2c006e170 123: onsuccess: #523: 2: Success after binutils/gcc: 13 commits new 01153c5b87 124: onsuccess: #524: 2: Success after binutils/gcc: 34 commits new 2f6af0fa43 125: onsuccess: #525: 2: Success after binutils/gcc: 47 commits new 03db26dbb9 126: onsuccess: #526: 2: Success after binutils/gcc: 27 commits new 7ee94f5f11 127: onsuccess: #527: 2: Success after binutils/gcc: 33 commits new 891247b4d0 128: onsuccess: #528: 2: Success after binutils/gcc: 31 commits new 94e2001e5f 129: onsuccess: #529: 2: Success after binutils/gcc: 3 commits new 8b7ce1f5d4 130: onsuccess: #530: 2: Success after binutils/gcc: 12 commits new 8d0a7e3490 131: onsuccess: #531: 2: Success after binutils/gcc: 47 commits new 84cda4d3d1 132: onsuccess: #534: 2: Success after gcc: 66 commits new df06566688 133: force: #536: 2: Success after binutils: 4 commits new bdc1e91e9d 134: force: #537: 1: Failure after gdb-12-branchpoint-3046-g [...] new 0cecbd6863 135: onsuccess: #538: 1: Success after binutils: 10 commits new 06af8b72d3 136: onsuccess: #539: 1: Success after binutils/gcc: 72 commits new 8c7acc7ce7 137: onsuccess: #540: 2: Success after binutils/gcc: 39 commits new 2245e1f054 138: onsuccess: #541: 2: Success after binutils/gcc: 14 commits new 794bd67c91 139: onsuccess: #542: 2: Success after binutils/gcc: 9 commits new 1ff2af58ad 140: onsuccess: #543: 2: Success after binutils/gcc: 56 commits new e6d47e7e08 141: onsuccess: #544: 2: Success after binutils/gcc: 14 commits new 5bb9ddab29 142: onsuccess: #545: 2: Success after binutils/gcc: 67 commits new a21ae3fd95 143: onsuccess: #546: 2: Success after binutils/gcc: 58 commits new e97c5ba8bb 144: onsuccess: #547: 2: Success after binutils/gcc: 74 commits new bd40f179c2 145: onsuccess: #548: 2: Success after binutils/gcc: 8 commits new 57a9e433a4 146: onsuccess: #549: 2: Success after binutils/gcc: 24 commits new d7545de920 147: onsuccess: #550: 2: Success after binutils/gcc: 6 commits new 1dfbf69f34 148: onsuccess: #551: 2: Success after binutils/gcc: 30 commits new 34535f8303 149: onsuccess: #552: 2: Success after binutils/gcc: 8 commits new 4a2bc70905 150: onsuccess: #553: 2: Success after binutils/gcc: 20 commits new f352ea1d83 151: onsuccess: #554: 2: Success after binutils/gcc: 11 commits new 902b90ee1d 152: onsuccess: #555: 2: Success after binutils/gcc: 18 commits new 7eba757933 153: onsuccess: #556: 2: Success after binutils/gcc: 18 commits new db22ade31c 154: onsuccess: #558: 2: Success after binutils: 19 commits new 0200f9c517 155: force: #560: 2: Success after gcc: 6 commits new 4ca668ca08 156: force: #561: 1: Failure after basepoints/gcc-13-4953-g3 [...] new ab27a7fc14 157: onsuccess: #562: 1: Success after gcc: 4 commits new 17e6a015bf 158: onsuccess: #563: 2: Success after binutils/gcc: 53 commits new 2ae807c250 159: onsuccess: #564: 2: Success after binutils/gcc: 36 commits new 59b9b3ba68 160: onsuccess: #565: 2: Success after binutils/gcc: 51 commits new 34ec81ca00 161: onsuccess: #566: 2: Success after binutils/gcc: 27 commits new 01267607f4 162: onsuccess: #567: 2: Success after binutils/gcc: 6 commits new 2ef29a2c66 163: onsuccess: #568: 2: Success after binutils/gcc: 4 commits new 31427175a7 164: onsuccess: #569: 2: Success after binutils/gcc: 115 commits new b09f0745fc 165: onsuccess: #570: 2: Success after binutils/gcc: 44 commits new 34af7642e5 166: onsuccess: #571: 2: Success after binutils/gcc: 45 commits new 5689da1ed2 167: onsuccess: #572: 2: Success after binutils/gcc: 129 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 (1283038ed2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 39284 -> 39208 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 271688 -> 272280 bytes 06-check_regression/console.log.xz | Bin 3008 -> 2960 bytes 07-update_baseline/console.log | 38 +++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++-------- 13 files changed, 34 insertions(+), 34 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-release-arm-mainline-allyesconfig updated (fe1e4f1e50 -> 27edc277c7)

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-release-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from fe1e4f1e50 44: onsuccess: #485: 21032: Success after binutils/llvm/linu [...] new 27edc277c7 45: onsuccess: #486: 21034: Success after binutils/llvm/linu [...] 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 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30352 -> 30860 bytes 04-build_kernel_llvm/console.log.xz | Bin 63468 -> 64148 bytes 05-build_abe-qemu/console.log.xz | Bin 30920 -> 31704 bytes 06-build_linux/console.log.xz | Bin 3660 -> 3664 bytes 08-check_regression/console.log.xz | Bin 4076 -> 4104 bytes 08-check_regression/mail-body.txt | 2 +- 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 +- 18 files changed, 26 insertions(+), 26 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-release-arm-mainline-allnoconfig updated (a4e9fbaa12 -> 07fb094561)

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-arm-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from a4e9fbaa12 35: onsuccess: #388: all: Success after binutils/gcc/linux/q [...] new 07fb094561 36: onsuccess: #389: 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 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 30676 -> 31008 bytes 04-build_abe-stage1/console.log.xz | Bin 87680 -> 87196 bytes 05-build_abe-qemu/console.log.xz | Bin 31952 -> 32604 bytes 06-build_linux/console.log.xz | Bin 3264 -> 3208 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4196 -> 4176 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 +++++++++++++++--------------- 18 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_gnu_cross_check_gcc/master-arm updated (ad7835c275 -> 5ae7ff64a9)

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 ad7835c275 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 9fa920fbc1 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards ae6c03a58c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards ce94c84015 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 0fe7265970 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 084c8bea55 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards d943b2d137 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 76e617472c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 87aa472244 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 2f6c095734 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 4fbb25c4a2 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 49eb57d928 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 7905a69452 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 0b0d48d0c1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 34f2507d56 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards b67c46ee59 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 29256a1ada 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards a10bb00197 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards b9eede0ad4 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c819e5011d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 79973bd3ce 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 06144580d1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 353c376d2c 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 8e0ae871d6 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 5fed159209 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 9b41a732c8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 2a2112c9d3 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards defcda6d53 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards eb6c47b95a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards ad39ef1463 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 00bfb8203c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 58739e9067 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 6d0d9b19ec 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards cc5b4d086d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards e15271bf63 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 02edc3aaef 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards d223030b16 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 4becb8a471 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards a6b6c32b97 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 9630acfad3 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards daed8d1463 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards a1a04df0af 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 00d5f649e3 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards b467c49fe4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 01f22e56c3 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 2cf30786a8 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards a40edd813b 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 3b95545132 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 05b8e07158 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 32cd6c671b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards bcab69df1d 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 0a5e29b306 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 450e6638aa 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 2350f9244e 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards ccdb6659e4 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 423cc136cc 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 2d10320220 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards ebca23a63e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards f5d9e98a26 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 8e75379819 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 192ee8b633 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards c9e888e244 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 040031211b 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 745ec88705 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 89aba5ff87 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 2b9eb5d16f 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards e50509397f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards d9240b274f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards c1d559c88a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 75a845b69c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 17c788964b 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 988f69423b 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 12cbaa4883 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards e565441b0d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 4cf9499ed8 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards e9a741f895 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards beacf3d495 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards a7d170c22f 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 93041fb90e 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards fa4c1bc6d7 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 55e23c282c 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 80594229a6 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 005d3facca 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 59897e98cf 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 7284ca1105 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards ba0dcd4bdf 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 6e3f341e2e 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 98b4e70356 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards e96572125e 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 9e37e65eb8 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 5bf86f2546 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 9efadeff31 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards bb5cdaaaef 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards eecadeebc4 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 679745a2bf 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 4c180629d0 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 850d74d92f 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards b0d548a39b 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 3fcaa36307 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards d0903bbd75 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 3ff58db684 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new d0fe365bc2 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new d164b31494 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new cd39f6403a 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 5f1e15e42f 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new c0197ace4c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 59a4a2fb34 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new cb8cce3145 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new f40cfee96c 259: onsuccess: #2075: 1: Success after glibc: 2 commits new fd40f3ded0 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 6a7d08aa09 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 5482c101c7 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new f6815c99ca 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 292f1be58b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new b3cf99b57f 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 3080f4ab3f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 7f1f1dd62a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new b7c47dea38 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 606f344c2c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 12e6ad540b 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new d68bd21bda 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 9752ac849e 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new f36346c5bc 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new e8521a3a2a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 3c4f6497ef 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 260a24758d 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 39bc5e9cf7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 48fb606573 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 402d71e751 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 4a63f816a6 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 3e4fafe548 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 1dd02434f7 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new f8691b543b 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 5b8b8df07d 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 114a2377b1 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 00afd88e76 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new ae8348240f 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 3747081052 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new b79e480f19 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new db9c813656 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 7b673f0b1e 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new e30e52bba9 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new b604285ab3 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 5029b3a22b 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 4a8fa53af8 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 25878bd7f2 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 4bba4f2406 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new d4671f6601 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 376014573f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 81571f6656 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new e113bbccdb 301: onsuccess: #2118: 1: Success after linux: 16 commits new a7495bd211 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 82dab11056 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 1bf4224569 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 08bd99862b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new b1c740af36 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new e2f579ac5d 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 2dba1011c6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 6f7b7c5cc0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new e3fc8edbb0 310: onsuccess: #2129: 1: Success after binutils: 4 commits new be35cc2897 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 98b9740d85 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new ef790308e8 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 429f5b3859 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 4e6a2ba6f2 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new dac956f779 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 491f1bc6ae 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 6a2f0d1fab 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 641f382f18 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new bbe06a1e0e 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new ccdc3b9f7e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new b21319372c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 9ca9dceb49 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 81ea259355 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new da455c7e7e 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 75814287c9 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new d6ac12ddc2 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 8792cce1da 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new aaa8378978 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new bd126979ff 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 688c4323b1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 5e665521b5 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 9576cf4264 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 6fa7409453 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new acbdccb50c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d90604c7eb 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new fff0a4f88a 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 1ac3eccc38 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 434a3b8eea 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 832b817f66 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 0cbcec8abd 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new dbcf8397ff 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 4e24a2dab0 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 4c7a1f0e20 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 35c6767f2a 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 5434ba7116 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new f14ea69936 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new e28c724f07 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 95da556c09 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 432cc52821 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 91a4fc911a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 953b3397bd 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5ae7ff64a9 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] 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 (ad7835c275) \ 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 1764 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31820 -> 31544 bytes 04-build_abe-stage1/console.log.xz | Bin 92048 -> 91952 bytes 06-build_abe-linux/console.log.xz | Bin 8992 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 240168 -> 236496 bytes 08-build_abe-stage2/console.log.xz | Bin 229016 -> 228620 bytes 09-build_abe-gdb/console.log.xz | Bin 39204 -> 38908 bytes 10-build_abe-qemu/console.log.xz | Bin 32160 -> 31924 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2748 -> 2592 bytes 13-check_regression/console.log.xz | Bin 6452 -> 5620 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 21 +- 13-check_regression/results.compare2 | 42 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 26 - sumfiles/g++.log.xz | Bin 2692288 -> 2692108 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2241952 -> 2245452 bytes sumfiles/gcc.sum | 2156 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 896920 -> 895432 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213988 -> 214048 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 445344 -> 432016 bytes sumfiles/libstdc++.sum | 2 +- 42 files changed, 1209 insertions(+), 1299 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page: