Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (e9f1a9fc7c -> dd4dd8e5b9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from e9f1a9fc7c 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new dd4dd8e5b9 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] 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 1740 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 52244 -> 51960 bytes 04-build_abe-gcc/console.log.xz | Bin 236808 -> 233716 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8896 bytes 07-build_abe-glibc/console.log.xz | Bin 232772 -> 234588 bytes 08-build_abe-gdb/console.log.xz | Bin 49888 -> 49900 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3864 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2384 -> 2128 bytes 11-check_regression/console.log.xz | Bin 18916 -> 18956 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 62 +- 11-check_regression/mail-body.txt | 221 +- 11-check_regression/results.compare | 114 +- 11-check_regression/results.compare2 | 6694 +++++++++---------- 11-check_regression/results.regressions | 114 +- 12-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 223 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 114 +- sumfiles/gdb.log.xz | Bin 1765268 -> 1646508 bytes sumfiles/gdb.sum | 10549 ++++++++++++++++-------------- 31 files changed, 9400 insertions(+), 8754 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch releases/gcc-10 updated (b17648c7d5f -> 8c583871e70)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from b17648c7d5f Daily bump. new 8c583871e70 Fortran: Fix function attributes [PR100132] 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: gcc/fortran/trans-types.c | 15 ++++++- gcc/testsuite/gfortran.dg/PR100132.f90 | 75 ++++++++++++++++++++++++++++++++++ 2 files changed, 88 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/PR100132.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch releases/gcc-11 updated (24f55a3fe48 -> cd13cc012e0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 24f55a3fe48 Daily bump. new cd13cc012e0 Fortran: Fix function attributes [PR100132] 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: gcc/fortran/trans-types.c | 15 ++++++- gcc/testsuite/gfortran.dg/PR100132.f90 | 75 ++++++++++++++++++++++++++++++++++ 2 files changed, 88 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/PR100132.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig updated (d1d02719ad -> be2d739ade)

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-allmodconfig in repository toolchain/ci/base-artifacts. from d1d02719ad 12: onsuccess: #418: all: Success after binutils/gcc/linux/q [...] new be2d739ade 13: onsuccess: #419: 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 1720 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30724 -> 30024 bytes 04-build_abe-stage1/console.log.xz | Bin 87440 -> 86584 bytes 05-build_abe-qemu/console.log.xz | Bin 30968 -> 31412 bytes 06-build_linux/console.log.xz | Bin 3036 -> 3284 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4244 -> 4412 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 | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allnoconfig updated (4f35dd019a -> d47eb65ed2)

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-arm-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from 4f35dd019a 12: onsuccess: #424: all: Success after binutils/llvm/linux/ [...] new d47eb65ed2 13: onsuccess: #425: 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 1704 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29928 -> 30060 bytes 04-build_kernel_llvm/console.log.xz | Bin 62476 -> 64320 bytes 05-build_abe-qemu/console.log.xz | Bin 31308 -> 31548 bytes 06-build_linux/console.log.xz | Bin 656084 -> 3128 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4580 -> 4476 bytes 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch releases/gcc-12 updated (1aa9ec7a030 -> 56275fd23e3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 1aa9ec7a030 Daily bump. new 9de83c0939d Fortran: Fix function attributes [PR100132] new 56275fd23e3 Fortran: Fix automatic reallocation inside select rank [PR100103] 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: gcc/fortran/trans-array.cc | 4 +- gcc/fortran/trans-types.cc | 15 ++++++- gcc/testsuite/gfortran.dg/PR100103.f90 | 76 ++++++++++++++++++++++++++++++++++ gcc/testsuite/gfortran.dg/PR100132.f90 | 75 +++++++++++++++++++++++++++++++++ 4 files changed, 166 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/PR100103.f90 create mode 100644 gcc/testsuite/gfortran.dg/PR100132.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (c051060ade8 -> 5299155bb80)

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 gcc. from c051060ade8 c++: make some cp_trait_kind switch statements exhaustive new 5299155bb80 Fortran: Fix ICE and wrong code for assumed-rank arrays [PR [...] 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: gcc/fortran/trans-expr.cc | 48 +++++++++++++++++++--------------- gcc/testsuite/gfortran.dg/PR100029.f90 | 22 ++++++++++++++++ gcc/testsuite/gfortran.dg/PR100040.f90 | 36 +++++++++++++++++++++++++ 3 files changed, 85 insertions(+), 21 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/PR100029.f90 create mode 100644 gcc/testsuite/gfortran.dg/PR100040.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (a7ce9ac3b6 -> 4055ad88d0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-arm in repository toolchain/ci/base-artifacts. from a7ce9ac3b6 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 4055ad88d0 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] 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 1664 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2700 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 51292 -> 50340 bytes 05-build_abe-gcc/console.log.xz | Bin 233996 -> 233508 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8616 -> 8880 bytes 08-build_abe-glibc/console.log.xz | Bin 232520 -> 233312 bytes 09-build_abe-gdb/console.log.xz | Bin 49488 -> 49820 bytes 10-check_regression/console.log.xz | Bin 4340 -> 4208 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++------------------ 19 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (480886c62a -> 2ac5ce1b8e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards 480886c62a 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards d20dcf0443 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards d4ea277c1f 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards 2f2ceb67ef 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards ee506ab77c 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 77643e47f9 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 180b7bff79 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards faa54fd011 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 6c5ff0e01f 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards dfa2ba3835 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards ed57c9d81d 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards 5cc3693c46 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards fd32604a23 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 969181cf97 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards c9e14df03f 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards f930083bf9 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 1969e74f31 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 41bcd54ea5 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 2f6abfc435 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 5df42490d9 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 5543694ab2 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards dec7d57c32 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 6f6648ee9b 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards f34c073621 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards b3e030f4c6 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 4796b61aaa 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 875a31236b 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 0be8a0cc5b 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 0c5f74379a 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 2393a57e48 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 8a0651a2d3 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 1d71eb09c4 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 98fa9d3762 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 5a985a6970 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 155f4fa155 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards e2e7055e22 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards f6db764afe 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 8afd4c566e 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards f633070d23 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 0625e7c231 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 9c70b6b4b3 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards afe78ff989 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 752eb09ca9 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 8ed28723d6 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards c129d76ce2 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards 34ebeafecb 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 5a7b436655 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards e7be46809a 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 0a9e78770b 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 47cfad71e8 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 3c78e0035f 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 78ff72cb59 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 0efc2c3481 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards d3773b62a3 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards c149721273 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 1071273851 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 4cd1bb4b60 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 5423cc0210 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards a771ab0a0e 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 0462a4a18b 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 7986d18bf1 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards cf7e2784a6 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 51759969a7 87: onsuccess: 1: Success after gcc: 6 commits discards 820848def1 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 420d1c73ba 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 51b5dea19c 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 51ba76533c 83: onsuccess: 1: Success after gcc: 14 commits discards 793e44cf4d 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards cc4e8f28ca 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 52c97b508f 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 03eaa6c8a2 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 28481b7e65 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 223c674207 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards c28eb7680d 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 95060b0a02 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards b1a49bcf8d 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards ddcbc3e68d 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards df53c9c885 72: onsuccess: 1: Successful build after baseline build: no [...] discards 3cd38e71cc 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards ef45c0081e 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 456971a36b 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards 5cc97fe869 68: onsuccess: 1: Successful build after gcc: 2 commits discards e5fbc0ba49 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 99fc76596d 66: onsuccess: 1: Successful build after gcc: 4 commits discards 1330fc6a74 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 74e77ebde2 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards dd382afef8 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 903952e31a 62: onsuccess: 1: Successful build after gcc: 4 commits discards d1658ca8cc 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards c7102c8ba0 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards e54cbae059 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards de7a103dbb 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards 591b3f53de 57: onsuccess: 1: Successful build after binutils: 2 commits discards 04213c90b6 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 27419e0b2c 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 57da6ccdf6 54: onsuccess: 1: Successful build after gcc: 5 commits discards f6c765ce44 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 03e2d5ed36 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 8d8aee0533 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards b95c1a971c 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 35d0113b79 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 717994a932 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 1a2de760e5 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 4c9bfad595 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new ffb25ce2f8 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 6c77ea39ee 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 5d9f5d80ab 54: onsuccess: 1: Successful build after gcc: 5 commits new 2763692e68 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 37d516fd75 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new c9c3492b8e 57: onsuccess: 1: Successful build after binutils: 2 commits new 0d469dd76b 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new 7566dfb793 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new 1131868960 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new cf3f0362b6 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 4c41da5845 62: onsuccess: 1: Successful build after gcc: 4 commits new fc0667105a 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 3a426ff3bb 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 580097dfd6 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 11840fe018 66: onsuccess: 1: Successful build after gcc: 4 commits new 06a9c238f1 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 0e140aaf07 68: onsuccess: 1: Successful build after gcc: 2 commits new d6b77bbc47 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new d2d7bc6e5f 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 51a223ac0c 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 4218f74da8 72: onsuccess: 1: Successful build after baseline build: no [...] new 43fd712c91 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new e1ac1e2f15 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 004a7d8459 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 38840e6591 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 25ef63ec09 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 71265270c3 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 85d610458b 79: onsuccess: 1: Success after binutils/gcc: 23 commits new aae67f1013 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 305886de78 81: onsuccess: 1: Success after binutils/gcc: 8 commits new c4c84a9723 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 8971e6f23c 83: onsuccess: 1: Success after gcc: 14 commits new f4a0212584 84: onsuccess: 1: Success after binutils/gcc: 2 commits new a4df7a023a 85: onsuccess: 1: Success after binutils/gcc: 19 commits new fb6aee0b83 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 70bc6134ae 87: onsuccess: 1: Success after gcc: 6 commits new 8fc05fdad7 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 2a8660c1c5 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new f7a4b3e3b0 90: onsuccess: #1645: 1: Success after gcc: 2 commits new ff2f0025a3 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new b43c4b1fb6 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new e98a464d58 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 27ac58bd00 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 5dffc74a7c 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 74c3c868b5 96: onsuccess: #1654: 1: Success after gcc: 5 commits new c1ce389e79 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 624367e711 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 4b460ced55 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new acf389e13d 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 29b0014b66 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 94e381563e 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new be43dcc824 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 18614a4d36 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 936283142d 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new da378f930c 106: onsuccess: #1702: 1: Success after gcc: 4 commits new f72268e5d9 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 9cc51ef2f6 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 1388bb18bd 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 3b3d3d17f8 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new e5cc6d0a68 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new bc5b1cebbf 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new ad41295a92 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 756e582fc4 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 53bc4af2e7 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 80e09b395b 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new a9090065d1 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new f40152f9c1 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 87647a93ae 119: onsuccess: #1715: 1: Success after binutils: 4 commits new d7a484dacf 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new fb6c03cb6c 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 6265cd1642 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new b3a899cf74 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new c97a3c4e71 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 5d4e90b16d 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 3ca8308c4f 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new e5f568694e 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 7b46c6d68c 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 22f25d731c 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 1919048838 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 1d19059d70 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 11efad646c 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 91400bedf9 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 2b3a7ba163 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 49d4c7855a 135: onsuccess: #1739: 1: Success after binutils: 4 commits new fc80d705b4 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 5e66b4d1e3 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new f21966f8e7 138: onsuccess: #1749: 1: Success after binutils: 5 commits new ad692ccb6d 139: onsuccess: #1753: 1: Success after binutils: 5 commits new c14417dbd4 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 03c8fb9b33 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new ccc766bd28 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 30ebe219b9 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 34d37ef84c 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 0fe26985b9 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new ebe3834494 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 4529d6ad97 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new b0d553bd14 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 750b3e72bb 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 2ac5ce1b8e 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] 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 (480886c62a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (2a [...] 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 1664 -> 1644 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 50516 -> 50620 bytes 04-build_abe-gcc/console.log.xz | Bin 232040 -> 233228 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3816 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2736 -> 2644 bytes 07-check_regression/console.log.xz | Bin 4864 -> 4396 bytes 07-check_regression/mail-body.txt | 40 - 07-check_regression/results.compare | 40 +- 07-check_regression/results.compare2 | 29 +- 08-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 2780096 -> 2815440 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 2368616 -> 2372740 bytes sumfiles/gcc.sum | 4342 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 906480 -> 904396 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2160 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204720 -> 205052 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 463488 -> 465744 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2319 insertions(+), 2438 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (eb7339a4a8 -> e6438df687)

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 eb7339a4a8 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 697ed8a9f4 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 6e487becd9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards ce48f072de 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 6ed5438594 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 92922a2be4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards bc88c36c91 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 5c729a4148 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 82ca4ef3f1 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards ff73a233e8 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards d7f59292e3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a53fcf24bd 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 5c67743b47 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards cd0672b5e3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 004503ef06 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards daf83f037a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards b80a5d451f 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 1ffa4d04b3 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards e0da216d0a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 6c2d745882 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 2ede3446c9 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 48179d035d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards bdcb0c95fb 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 75185f98fe 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 66062a554e 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards f6df9c3ca4 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards bef18d16d2 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 630493ff38 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards d1b9630fd5 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards acda6ae050 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards e16a53816e 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 6aa4b0c4a7 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards a6190937e9 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 8fa47ff213 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 360e13b317 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 4826b13519 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards e79d998d25 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 7eeeb50521 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards d8b11c088a 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 429c75f84a 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards d288051c76 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 89a2c0cfa3 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 6c768c41a6 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards dd71f1dd68 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 49ead43d56 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 3ad84f798a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards bac7e0a175 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 96b6900835 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 3ca01c611f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards eb695b2f24 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards e4ac5a1057 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 2d0c22adca 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards b53a59fc91 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards a5fb4df8ea 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 007eb97a94 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 430fe56d7b 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 5315b08ee1 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards a6a106682d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards e1dd9bcd5c 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7568a0ef46 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 8071ac88cf 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 6f284d9e77 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 1874b03c00 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 176499303d 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards ae6a318a53 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards a7f4188a9f 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 3bae85608b 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards dbd5806d13 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 7753741514 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 1a4abe82a5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 284c5e82ce 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 504de0a5ef 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0dfdb94337 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards d0f83ac534 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards d6aca2f47d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9b524b84c 75: onsuccess: 1: Successful build after linux: 44 commits discards c43b276759 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 833b96fa17 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9ed50c670e 72: onsuccess: 1: Successful build after linux: 12 commits discards cbb626bd1d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 944a208bcf 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 7d3089ac2e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards d012719d99 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8cf5b5f510 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 8a51a66269 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 87ab95e678 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b408306f95 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 164d95d30b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards d763481550 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 79815bb43f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e349a63a86 60: onsuccess: 1: Successful build after glibc: 2 commits discards cf66ffc8b0 59: onsuccess: 1: Successful build after binutils: 2 commits discards 08ed925a2b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards ea4ba54f2f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cd764bfc0b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2ec0641d1a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards fea7f4cc50 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 884ef541cd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 5673f96610 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards e502a4213b 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 48f2206bbe 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e0f9fc0c8c 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0bf7feca28 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3a2507915 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 08743b3fdd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 43b9d4a9b6 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c275f03fb4 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 88915b49f7 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 59655c07ec 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 60443b2561 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 577e843f00 59: onsuccess: 1: Successful build after binutils: 2 commits new 3ff75e1fdf 60: onsuccess: 1: Successful build after glibc: 2 commits new dcf44eff59 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new fc00e91859 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new fe184a6add 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3e57bc0e0b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e05ef882e9 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b410f816a6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 1b02fbe001 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 14585422cc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a8d51ec456 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new d69c299ed5 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new c9e14f5f52 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 7bf7b52fb3 72: onsuccess: 1: Successful build after linux: 12 commits new 9c3e447af1 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f50420b867 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 92fdb6add9 75: onsuccess: 1: Successful build after linux: 44 commits new b5a6625b93 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 26e49df14a 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new f3761975d2 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new ce537a1ca0 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8513f6306f 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4b5d78e4a5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 7f7c600717 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a328704a65 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new fb22afbf7d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new fda7541c8c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new cd8c03396b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new b731a62853 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new f2e9c352d7 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new d3653ccfc4 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new ee20939a8a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 60e1688217 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 5e282f3b8a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 93c83a4f89 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new fe21c4113c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new d31ce8d33e 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 764e790fd7 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 9d8875decb 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new b20db61f5d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 16bd20a9f3 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 82543d9b4b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 1bd70fdbe8 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 1fa98d81a3 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new a94519ca0b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1a00e6566f 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 23bbb22461 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new c4b843f500 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new fca395bc31 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 0b921c00ce 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 14aead96a8 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new b8552d8f41 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 4f09e584e0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 8e118c9b3d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 52108643d0 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 2e67d1c7f2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 8c0b6e2f75 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new e653209cb1 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 16770253ac 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new c45308d954 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6cca899bee 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 87740866b4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new dc5a37d7a8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f281393b0c 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new ecac712530 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 9336ab6f63 124: onsuccess: #2159: 1: Success after linux: 23 commits new 116c2d91c3 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 23f66441df 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 899185f3db 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 9e88a336eb 128: onsuccess: #2163: 1: Success after linux: 23 commits new 5ad8f3420c 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 5618709d8f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 5e61f8e71e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 1acc64abd2 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new ef9712fcc0 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 7dfd0ce638 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new c3172eb8b0 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 9da815801b 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 32f5482ab3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 99c6da183c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 36622b15c3 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new a33ded6894 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new bfaee73947 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 0746420734 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new f3bf294a8c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 4a1f24a92e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new e1e13951b5 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 6e26704665 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 81952a59ca 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 2eb2e09f04 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 3781117740 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new c186696221 150: onsuccess: #2185: 1: Success after gcc: 3 commits new e6438df687 151: onsuccess: #2186: 1: Success after gcc: 2 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 (eb7339a4a8) \ 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 1700 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30124 -> 30292 bytes 04-build_abe-stage1/console.log.xz | Bin 72704 -> 72612 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 240396 -> 239464 bytes 08-build_abe-stage2/console.log.xz | Bin 203216 -> 203232 bytes 09-build_abe-gdb/console.log.xz | Bin 37508 -> 37504 bytes 10-build_abe-qemu/console.log.xz | Bin 32036 -> 31836 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2856 -> 2848 bytes 13-check_regression/console.log.xz | Bin 9344 -> 9660 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 152 +- 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 72 +- 13-check_regression/results.compare2 | 622 ++-- 13-check_regression/results.regressions | 124 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 124 +- sumfiles/g++.log.xz | Bin 3426616 -> 3405440 bytes sumfiles/g++.sum | 184 +- sumfiles/gcc.log.xz | Bin 3032264 -> 3026724 bytes sumfiles/gcc.sum | 6026 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1038696 -> 1030676 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202728 -> 202360 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2660 -> 2652 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427560 -> 421788 bytes sumfiles/libstdc++.sum | 14 +- 41 files changed, 3857 insertions(+), 3896 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022