Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

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

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 824f8a1a2a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new e9f1a9fc7c 55: onsuccess: #534: 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 1672 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52508 -> 52244 bytes 04-build_abe-gcc/console.log.xz | Bin 234872 -> 236808 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9220 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 231948 -> 232772 bytes 08-build_abe-gdb/console.log.xz | Bin 49964 -> 49888 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2580 -> 2384 bytes 11-check_regression/console.log.xz | Bin 12948 -> 18916 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 58 +- 11-check_regression/mail-body.txt | 210 +- 11-check_regression/results.compare | 105 +- 11-check_regression/results.compare2 | 3324 ++++++++- 11-check_regression/results.regressions | 107 +- 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 | 212 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 107 +- sumfiles/gdb.log.xz | Bin 1719984 -> 1765268 bytes sumfiles/gdb.sum | 10914 ++++++++++++++---------------- 30 files changed, 8662 insertions(+), 6431 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch release/2.36/master updated (227c903587 -> 76e05613ee)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.36/master in repository glibc. from 227c903587 get_nscd_addresses: Fix subscript typos [BZ #29605] new 76e05613ee stdlib: Fix __getrandom_nocancel type and arc4random usage ( [...] 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: NEWS | 1 + stdlib/arc4random.c | 2 +- sysdeps/unix/sysv/linux/not-cancel.h | 2 +- 3 files changed, 3 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch master updated (8b10727a9a -> 609c9d0951)

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 glibc. from 8b10727a9a LoongArch: Add static PIE support new 13db9ee2cb stdlib: Fix __getrandom_nocancel type and arc4random usage ( [...] new 609c9d0951 malloc: Do not clobber errno on __getrandom_nocancel (BZ #29624) 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: stdlib/arc4random.c | 4 ++-- sysdeps/mach/hurd/not-cancel.h | 12 ++++++++++-- sysdeps/unix/sysv/linux/not-cancel.h | 4 ++-- 3 files changed, 14 insertions(+), 6 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_bmk_gnu_apm/gnu-master-aarch64-cpu2017-O3_VECT created (now 2631a7e52b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_apm/gnu-master-aarch64-cpu2017-O3_VECT in repository toolchain/ci/base-artifacts. at 2631a7e52b 0: init: #3: 1: [TCWG CI] No change after baseline build: no [...] This branch includes the following new commits: new 2631a7e52b 0: init: #3: 1: [TCWG CI] No change after baseline build: no [...] 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (e564021e4c2 -> b52b99b62df)

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 e564021e4c2 aarch64: Fix C++ ICEs with _Float16 and __fp16 [PR107080] new b52b99b62df diagnostics: Fix virtual location for -Wuninitialized [PR69543] 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/testsuite/c-c++-common/pr69543-3.c | 8 +--- gcc/testsuite/c-c++-common/pr69543-4.c | 8 +--- gcc/testsuite/c-c++-common/pragma-diag-16.c | 63 ++++++++++++++++++++++++++ gcc/testsuite/gcc.dg/cpp/pragma-diagnostic-2.c | 7 +-- gcc/tree-ssa-uninit.cc | 12 +---- 5 files changed, 73 insertions(+), 25 deletions(-) create mode 100644 gcc/testsuite/c-c++-common/pragma-diag-16.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (a6d8c61a498 -> e564021e4c2)

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 a6d8c61a498 i386, rs6000, ia64, s390: Fix C++ ICEs with _Float64x or _F [...] new e564021e4c2 aarch64: Fix C++ ICEs with _Float16 and __fp16 [PR107080] 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/config/aarch64/aarch64.cc | 2 ++ gcc/testsuite/g++.target/aarch64/pr107080.C | 19 +++++++++++++++++++ 2 files changed, 21 insertions(+) create mode 100644 gcc/testsuite/g++.target/aarch64/pr107080.C -- 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 (f575f2f612 -> 2498da7aca)

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 f575f2f612 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 23615e49e0 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards c231fff5db 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards b385c0e6e5 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards 238c920509 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 06bbeb4a30 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards fd2a0f2a9c 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards ad129bc60d 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards ff62208735 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 72224ed8e9 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 86d655fa2d 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 052b1f33e7 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 4f5dca0fc4 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards b659beed1d 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards d3941928c7 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards eb5691296f 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards fc4aabe19a 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards a2dad4b9a1 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 662819ff64 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 01b011ff5a 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 682f8b1964 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 6f59f86c82 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 0544bcea56 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 4bf504b7f0 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 6425ce8024 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 19f53bd443 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards eb662591fa 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 61e1a89b4c 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 649955cbce 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 78b844c000 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 578a28fa2f 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 6237782926 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 5cf3c5a150 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 918e9c86c7 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 8922b3cfc1 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 8e37e79bfa 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 67d8752f83 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards f8dbbeea07 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards ff2a843c95 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards bb3a7e8ff4 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 47e4d53db3 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards e6d9584d9b 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards d0ae46c28e 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards a6deea21c6 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards df2cd86eb4 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 198bef2a77 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 979d38a7f1 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 69f23cc4e9 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 1b3d0b7eca 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards fba4ad302d 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 3190fbde35 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 1b4987e48a 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards c7b3cc8cd6 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 46b006aefc 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards db84153942 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards f7c0c64a42 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 8158da6d85 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards fbd9882085 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 9799c5038c 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards b41cca659b 87: onsuccess: 1: Success after gcc: 6 commits discards 897ecabeed 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards d9aaffe09e 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards cda3a94518 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards cbf2c47578 83: onsuccess: 1: Success after gcc: 14 commits discards 007ca31868 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 2c9f50d9ce 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 3fb5348a3e 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 9f2f4ab0c8 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 8456d99d4f 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards dbca056fe8 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards bd4bce9bc4 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 260fb975a3 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 6955e1937c 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards e37c5656a9 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 851fb31c3b 72: onsuccess: 1: Successful build after baseline build: no [...] discards 7556c0c8b7 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 572c928421 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 7dc82b3ddd 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards e53e27dafc 68: onsuccess: 1: Successful build after gcc: 2 commits discards 26b31d9217 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 82f4797d7d 66: onsuccess: 1: Successful build after gcc: 4 commits discards 44159412c2 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards a971b99a49 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 4df002e232 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 76fa60d9c5 62: onsuccess: 1: Successful build after gcc: 4 commits discards b8ce706861 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 85c10f5277 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards fdaf01ed03 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 21ef42147a 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards 5f1664bafe 57: onsuccess: 1: Successful build after binutils: 2 commits discards 2a8c4a3f87 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards d1503a25c1 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 378530b53d 54: onsuccess: 1: Successful build after gcc: 5 commits discards a2f6ccd054 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 785ce21280 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards fb1f0df9b2 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 20f9471456 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 70be0ab538 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 0f946c08c8 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards b69eb77768 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards ce3c92fbb3 46: onsuccess: 1: Successful build after baseline build: no [...] new 99cfdfd4dc 46: onsuccess: 1: Successful build after baseline build: no [...] new 6c03538aac 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 72aaee5eca 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 94f9b800ea 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 25749f9b1f 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new b33a3f0617 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 6b5a99b931 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 6c85e8670d 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 8c02d8a071 54: onsuccess: 1: Successful build after gcc: 5 commits new 4bf6772bc5 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 5bbb486958 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 18b8b19943 57: onsuccess: 1: Successful build after binutils: 2 commits new e0c2e3e549 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new 3771424738 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new eb1c4916dd 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 2be80bcb1c 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new e12e85d6c4 62: onsuccess: 1: Successful build after gcc: 4 commits new 5be9b12caa 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new ffed515575 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 429f880de0 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 5aa18fbdb5 66: onsuccess: 1: Successful build after gcc: 4 commits new 53c2afcc95 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 2881b1282a 68: onsuccess: 1: Successful build after gcc: 2 commits new 4c376f3e24 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new eb94914a1d 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 28a214f08e 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 470f5030b5 72: onsuccess: 1: Successful build after baseline build: no [...] new 159d11f9b7 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 8bb8ea1621 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 03b7acdd4c 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new c8fea4af91 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 378295de9e 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new dbe385899e 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 28e11878fe 79: onsuccess: 1: Success after binutils/gcc: 23 commits new b97deac0da 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 79d96e6ec8 81: onsuccess: 1: Success after binutils/gcc: 8 commits new aefea9471b 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 3f11941b91 83: onsuccess: 1: Success after gcc: 14 commits new b69b9fd6b8 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 0fb5ca039f 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 7057dc60f4 86: onsuccess: 1: Success after binutils/gcc: 8 commits new faa8f603da 87: onsuccess: 1: Success after gcc: 6 commits new 39bb8cc39a 88: onsuccess: 1: Success after binutils/gcc: 2 commits new d445b9f10c 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new b7381a726a 90: onsuccess: #1645: 1: Success after gcc: 2 commits new 1f22dfae9d 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new ed7286224d 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 0f02242060 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 01e5d81526 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new ffe4bf704d 95: onsuccess: #1653: 1: Success after gcc: 13 commits new ddfe9e67d7 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 92289ef274 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 2b961ea3e4 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 402a73fefb 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 6e844b2ce2 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new f828abea1b 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new ce56539d6a 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 548843e245 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 3d13ff19fc 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 53691d8297 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new a591d45a47 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 9eaba0e148 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 8b07dd2226 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 5ddd106fca 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new d82b542cbf 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 1dc0e60e6c 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new cd78e5f285 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new a7cf36eead 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 9966c8fd49 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new e7c4eb64a4 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new e5d76e3676 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 5765c0ecb3 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new a6d9fbb99c 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 397040d8eb 119: onsuccess: #1715: 1: Success after binutils: 4 commits new c09eb0ba03 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 0d439c8262 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 3802435c64 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new e3fb59da1b 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new bb97593b4e 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new f3dea5dd37 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 2215c0112d 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new ee7f1d71c3 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new fc9d635d95 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 616bcb9a27 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 89904457e4 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 6ab2391de8 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 25590591fe 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new f6fb117416 133: onsuccess: #1733: 1: Success after binutils: 3 commits new d38c5a25fe 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 7d80e50990 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 2ed94b249f 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new e154696dee 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new f6eef0400d 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 7ff61a923f 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 28ef7126ea 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 1d0645c70d 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new 4c44e28b84 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 56977ef4f9 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new c63aafbd2a 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 5eaae58a39 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new 5bfd4805fd 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 2498da7aca 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 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 (f575f2f612) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (24 [...] 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 1660 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 50340 -> 51008 bytes 04-build_abe-gcc/console.log.xz | Bin 232720 -> 234864 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3816 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2684 -> 3408 bytes 07-check_regression/console.log.xz | Bin 5124 -> 5736 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 6 + 07-check_regression/mail-body.txt | 45 +- 07-check_regression/results.compare | 32 +- 07-check_regression/results.compare2 | 126 +- 07-check_regression/results.regressions | 26 + 08-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 47 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 26 + sumfiles/g++.log.xz | Bin 2782984 -> 2778128 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2357976 -> 2370648 bytes sumfiles/gcc.sum | 4584 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 911680 -> 919496 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2160 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204520 -> 204548 bytes sumfiles/libgomp.sum | 59 +- sumfiles/libitm.log.xz | Bin 2532 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 463804 -> 461448 bytes sumfiles/libstdc++.sum | 19 +- 36 files changed, 2697 insertions(+), 2548 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- 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 (19b7782e36 -> a7ce9ac3b6)

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 19b7782e36 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new a7ce9ac3b6 64: onsuccess: #467: 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 1660 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2700 bytes 04-build_abe-binutils/console.log.xz | Bin 51316 -> 51292 bytes 05-build_abe-gcc/console.log.xz | Bin 232312 -> 233996 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 9232 -> 8616 bytes 08-build_abe-glibc/console.log.xz | Bin 232324 -> 232520 bytes 09-build_abe-gdb/console.log.xz | Bin 50156 -> 49488 bytes 10-check_regression/console.log.xz | Bin 4672 -> 4340 bytes 10-check_regression/mail-body.txt | 8 +++++++- 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 | 10 +++++++-- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++------------------ 20 files changed, 42 insertions(+), 30 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 (2215e7f30b -> 13c1c1f7b9)

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 2215e7f30b 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 2d06ee2311 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 00b5a297ae 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 83b8444a9b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards d0f0ea2279 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 0fd7c8e4cd 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 4640c42d5b 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a1873116c7 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 488c7164e9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 34f6d3ceed 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards f53f625404 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 28f296f525 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards c9566ff76e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 0318f655ee 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 56da5b2424 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 057b30ba76 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards cb5b05b93b 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards dfa85ca827 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 41db5ca3ba 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 92beeec99c 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards afd72f6849 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 989a64da38 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards c7a803fbde 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0fb72c13f7 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards e0211ec63b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards e49f69bd77 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 804460c7a7 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 695f1e5ca3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 76f7a2420a 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5e5edfa25d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards ae140e38bd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 9734bad17a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards cf969cf480 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards dc7a58411c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 7dff448db6 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 8b7a16c9f8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 19aa25fadb 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards f6c395c20c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 4a2a8017aa 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 76a9633b1c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards e28b50f915 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 021b28098f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 1f8a394fcd 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ba3540a46f 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards cd91565b42 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards bad8bc65ca 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards a0933cf32e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 193b53cea9 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards b4dec405d7 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards bd672fd8eb 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 07b72a3121 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 2aab5aa631 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 670abe78f7 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards eb10c166e8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 3cb40ffd40 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 787fa0bb2f 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 5e023ffd5f 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 0ab04b094f 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 05c29611ad 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 44cbb6f96a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards e4d501029d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards f9deeebfde 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 6505f81338 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 499e525f55 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 735409b1c0 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 393f1385a3 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards bbb617d110 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b8548e5629 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a325b28438 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 1091bd92c2 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 0f218c61ae 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 088c8d79eb 75: onsuccess: 1: Successful build after linux: 44 commits discards f6031352a9 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b070241808 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 195c2dc6bf 72: onsuccess: 1: Successful build after linux: 12 commits discards 26559f8df7 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards a6ce167a72 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards ae485b8a65 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards aa8b0bcf5c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6b8d5f5fcb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 65b9da04d6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 65f4bb13b3 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4e30d63fcc 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0481103e1f 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 3adcfae811 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 856e9bd614 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards a7f482a89a 60: onsuccess: 1: Successful build after glibc: 2 commits discards a4bb5182b1 59: onsuccess: 1: Successful build after binutils: 2 commits discards 465b185a13 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 85ecac66dd 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2bb14a88c9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ca110a7e51 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 2624f828fa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 038acc2abe 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c477254496 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards b6edb5a4c3 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 83c3e83347 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e14194f051 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards cb99b1e51b 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5960da2622 47: onsuccess: 1: Successful build after linux: 10 commits discards a695757ec4 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new d936a1519f 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1e41ad3a7c 47: onsuccess: 1: Successful build after linux: 10 commits new 4f46e7c92a 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 396fc25fe0 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new fb46dd8c5b 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 29936f5577 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 38b4fc658d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 64dc3e6604 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new f38c61597d 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3a13b8af64 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 82b372510d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9674e3be45 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 092675cd0c 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 4dacd0e9ed 59: onsuccess: 1: Successful build after binutils: 2 commits new ae60a3b388 60: onsuccess: 1: Successful build after glibc: 2 commits new b397735a56 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1928758873 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 24e6b575a1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 79f0bbb01c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2b5c6ae328 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d60357b5bc 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new ad47832abc 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new d66b3527ee 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 59b4c34b68 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 8e73372571 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new a633428eef 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 196748fd59 72: onsuccess: 1: Successful build after linux: 12 commits new 2ba2318087 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8a6c5af2c4 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 837039dd4b 75: onsuccess: 1: Successful build after linux: 44 commits new 5fccc6273e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4d880fb0d6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 53f7a8f759 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0c0ea98c57 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c8576eb0e3 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e3b48ffa8a 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new b3903f5630 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new c41cae3cee 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 8814dcd848 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 61a7a2352c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new e774deda17 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 92b7f9389d 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 89428385dd 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 03e1dfd5f2 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 47c5d68fa6 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new d10e56dce8 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 8a91809c87 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8485818fb4 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new d110a81ee0 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new cde2ddd682 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 458719e7e9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new c1a357c909 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 77a2b5f611 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d6edde32f7 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 8db9aeee4d 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new e713e65776 101: onsuccess: #2130: 1: Success after binutils: 81 commits new b8548eb734 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new b968632727 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 35cf817ba2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 319ca2de33 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new fd4f21fc0a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 950e67d434 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new b4b0d15d47 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 6f81a6eebe 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 77dc245715 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 473950ccb1 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new ce9e9c52ff 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 4c4c8d2dd5 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7cea956e61 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 32c4367c2d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 8ac00b69a4 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 6af5ac97f4 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 9290b4abbe 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 07b99e482d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new d55a0a6ff5 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 7f20c13ec9 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5e0d6f6679 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 66212a6088 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new a4fd3915b9 124: onsuccess: #2159: 1: Success after linux: 23 commits new db97e25cb0 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 0276aefe3b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 491cab4ee4 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 585db4d589 128: onsuccess: #2163: 1: Success after linux: 23 commits new b523553c90 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 10af6eea4f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 37f2911991 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 1ef66303ef 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 702d6d42a5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 4c97fe176a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 76461ef814 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 4daec7bed9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new aa0f4e7174 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 902b7e4b15 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new aac120d405 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new a7aa5d9bb5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 509845db3c 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 3a69ee4c22 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 417b1bc9f3 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 44851faeab 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 32d2e1f1de 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 7c8f98333a 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 13c1c1f7b9 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] 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 (2215e7f30b) \ 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 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30304 -> 30532 bytes 04-build_abe-stage1/console.log.xz | Bin 72600 -> 72336 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 239776 -> 240032 bytes 08-build_abe-stage2/console.log.xz | Bin 203040 -> 203140 bytes 09-build_abe-gdb/console.log.xz | Bin 37412 -> 37644 bytes 10-build_abe-qemu/console.log.xz | Bin 31900 -> 31980 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2808 -> 2712 bytes 13-check_regression/console.log.xz | Bin 8132 -> 6644 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 134 +- 13-check_regression/results.compare | 84 +- 13-check_regression/results.compare2 | 435 +-- 13-check_regression/results.regressions | 87 - 14-update_baseline/console.log | 64 +- 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 | 136 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 87 - sumfiles/g++.log.xz | Bin 3408532 -> 3434876 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3029088 -> 3002148 bytes sumfiles/gcc.sum | 4494 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1028292 -> 1026064 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202120 -> 202196 bytes sumfiles/libgomp.sum | 59 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428316 -> 425152 bytes sumfiles/libstdc++.sum | 14 +- 43 files changed, 2579 insertions(+), 3268 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, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_ubsan updated (96746548d8 -> 236a7f19b6)

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-arm-bootstrap_ubsan in repository toolchain/ci/base-artifacts. from 96746548d8 58: onsuccess: #468: 2: Success after binutils/gcc: 51 commits new 236a7f19b6 59: onsuccess: #469: 2: Success after binutils/gcc: 53 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1668 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50976 -> 50520 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 530260 -> 530624 bytes 06-check_regression/console.log.xz | Bin 3140 -> 3224 bytes 06-check_regression/mail-body.txt | 2 +- 07-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 14 files changed, 19 insertions(+), 19 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 September 2022