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_gcc/master-aarch64 updated (9be30e6001 -> a5d94ff1d9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. from 9be30e6001 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new a5d94ff1d9 53: onsuccess: #790: 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 1728 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 37724 -> 39560 bytes 04-build_abe-gcc/console.log.xz | Bin 213112 -> 212420 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8824 -> 8452 bytes 07-build_abe-glibc/console.log.xz | Bin 240008 -> 239776 bytes 08-build_abe-gdb/console.log.xz | Bin 37336 -> 39060 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3824 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2640 -> 2500 bytes 11-check_regression/console.log.xz | Bin 7580 -> 6780 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 73 +- 11-check_regression/results.compare | 45 +- 11-check_regression/results.compare2 | 271 +- 11-check_regression/results.regressions | 27 + 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 | 75 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 27 + sumfiles/g++.log.xz | Bin 3712896 -> 3717500 bytes sumfiles/g++.sum | 108 +- sumfiles/gcc.log.xz | Bin 3261440 -> 3258964 bytes sumfiles/gcc.sum | 4196 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1065064 -> 1071612 bytes sumfiles/gfortran.sum | 74 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219696 -> 220656 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 452904 -> 450292 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 2424 insertions(+), 2570 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-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_kernel/llvm-release-arm-lts-defconfig updated (5a3bb9c0d7 -> c7a0bdf7b7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-defconfig in repository toolchain/ci/base-artifacts. from 5a3bb9c0d7 11: onsuccess: #264: boot: Success after binutils/llvm/linux [...] new c7a0bdf7b7 12: onsuccess: #265: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 30036 -> 30080 bytes 04-build_kernel_llvm/console.log.xz | Bin 63796 -> 64260 bytes 05-build_abe-qemu/console.log.xz | Bin 31508 -> 32040 bytes 06-build_linux/console.log.xz | Bin 3468 -> 3452 bytes 07-boot_linux/console.log.xz | Bin 5892 -> 5824 bytes 08-check_regression/console.log.xz | Bin 4308 -> 4284 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 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_gcc_bootstrap/release-arm-bootstrap_profiled_lto updated (f43acfa486 -> e7392355cb)

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/release-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. from f43acfa486 14: onsuccess: #125: 2: Success after binutils/gcc: 20 commits new e7392355cb 15: onsuccess: #126: 2: Success after binutils/gcc: 24 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 52668 -> 51872 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 945764 -> 946500 bytes 06-check_regression/console.log.xz | Bin 2888 -> 2940 bytes 07-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 13 files changed, 16 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (c3d64d467d4 -> 4cfa9edb357)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from c3d64d467d4 gdb/testsuite: handle invalid .exp names passed in TESTS new 4cfa9edb357 [gdb/testsuite] Fix waitpid testing in next-fork-other-thread.c 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: gdb/testsuite/gdb.threads/next-fork-other-thread.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 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 (31e6ba536b -> 2a80c4e5bb)

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 31e6ba536b 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards 8bb84c7be5 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 0e935b4f3c 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards b6235fabf6 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 0f9df77b60 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards 29a1f14da6 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 94c6f136c9 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards 58573cfb37 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards b823f87825 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 55aa4fdcf2 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards d53025339b 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards 8f65444302 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 3eb61be910 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards da9ec8c55c 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 6720f7329b 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards 0caa604db7 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 28bbd795d9 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 8b3d895648 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 89f60a2fd3 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards d62e5a8c6c 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards cbb0727d53 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 132aac01af 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards b119129858 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 3ef1860272 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards d333d65a1f 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards f9d6a1c1c3 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 2a6ba0e93e 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 3d572071f6 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 9656fe61cc 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 31a01e3c2b 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 8a2ea87b70 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards a968d6f809 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 387530af09 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards dd0104d844 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 6a72b1fb4c 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 0cf0d6c636 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 65b68fedb8 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 81bfc0ca5c 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 4e6cb83261 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 8263c05c32 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 4ef645c809 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 68a3237e13 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 8e46c93e59 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 602b579f30 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 1fe712750f 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards d7b75d16f4 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 56f7fe1605 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 8944c1bb7a 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 38d80a7fe7 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards edc122f1a1 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards c70923a166 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 4203e56d04 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards ed5b88c9b3 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards ed11afcb84 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 87d8d73208 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 5b84f89339 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards adf21d9028 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 0205f3ed18 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 23d22dad38 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 4c8980bd6e 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards bff705f8d2 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 24477d407b 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 4e5ba91680 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards c4d8ce1723 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 08a4071242 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 8520e1906f 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 1f33cdabc0 87: onsuccess: 1: Success after gcc: 6 commits discards 24895a7dae 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards c88cd843b3 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 0e8ba0dcfa 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 9c685b4cdc 83: onsuccess: 1: Success after gcc: 14 commits discards ff941c54fb 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 42299d4ad4 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 4310eb2281 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards e553a21ea1 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards f3ab4b612d 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 78d2d7a650 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards e8074eb838 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 4cfea266b1 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards f922988b18 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards e7521ef6c5 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 19b8e22035 72: onsuccess: 1: Successful build after baseline build: no [...] discards 5e2c982314 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards a14d8074c9 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 0e76b5f6d2 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards 103d054508 68: onsuccess: 1: Successful build after gcc: 2 commits discards 5ff00415bb 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 7c911a56d2 66: onsuccess: 1: Successful build after gcc: 4 commits discards c402750a5a 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 3aa91fa805 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards c74c2e7b6d 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards f237b7d0a7 62: onsuccess: 1: Successful build after gcc: 4 commits discards a71112fc02 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 17d1dcb4b2 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards edf4e4a201 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 5a9c2a1305 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards 8fc1413ab3 57: onsuccess: 1: Successful build after binutils: 2 commits discards dc606f411b 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards a62ddb7232 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 41d38d5de9 54: onsuccess: 1: Successful build after gcc: 5 commits discards 9aa7441f7e 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 766b353230 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 590188d492 54: onsuccess: 1: Successful build after gcc: 5 commits new bf4d1c134c 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new fe2b38a410 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new a841c6252e 57: onsuccess: 1: Successful build after binutils: 2 commits new 8133ace96d 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new a3615b43f6 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new 410ec1fb3a 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 94a2df9a96 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 7e1c01f82f 62: onsuccess: 1: Successful build after gcc: 4 commits new fc789cd32d 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 3cfc5a3c01 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 63eb33d289 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 9bf66e23a1 66: onsuccess: 1: Successful build after gcc: 4 commits new 51e9d94d89 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 34685cdf33 68: onsuccess: 1: Successful build after gcc: 2 commits new 4c305f91f9 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new 5e58a13050 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 9555b38113 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new d40b5914df 72: onsuccess: 1: Successful build after baseline build: no [...] new 512060a184 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new e875bb056a 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 3e8141265b 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 2b30a8d8f1 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 679f31b62d 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 65d8663718 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 0debbc48e6 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 8a11de90da 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 44bc1d5b19 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 932ac604d1 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 2e831e9391 83: onsuccess: 1: Success after gcc: 14 commits new 185d5f4a4d 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 282a8a74a4 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 9bb97a1bce 86: onsuccess: 1: Success after binutils/gcc: 8 commits new cafebc5383 87: onsuccess: 1: Success after gcc: 6 commits new 3cb2dce4f6 88: onsuccess: 1: Success after binutils/gcc: 2 commits new e59abcddb3 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new ecc737c4a8 90: onsuccess: #1645: 1: Success after gcc: 2 commits new 154f8085d2 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 8b47e62626 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new ad2edc06dd 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 60dc792795 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 7a4c04c752 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 14d44ddedf 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 30bcbcf97b 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 39399840ac 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new e6c9e133dc 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new d5c61ca7ac 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 604dd807ed 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 6e68c478de 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 404a34910a 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new bd290a77a9 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 7a9baa2656 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 1e47416acc 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 7cf87960b7 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new acb2516d38 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new d445856f17 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new d7e16defe1 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 106c87da0f 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 9851e30220 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 9019b37cb5 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new bf69f8352d 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new c4f3fd5467 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 8fc8ee4410 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 3ffef7c51f 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 714d5cd41d 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 4e75328ed8 119: onsuccess: #1715: 1: Success after binutils: 4 commits new b9f9d4c0e2 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 8c64df0545 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 3435ad197a 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new b36d7376df 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 281691771b 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new d533c68c36 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new b64cedcae0 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new d2a6f03533 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new b50f1acfd6 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 13d9a61ecb 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 6407ed8abf 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 978b65d196 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 9623b9aaa3 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 6871e1470e 133: onsuccess: #1733: 1: Success after binutils: 3 commits new ebd259e8c0 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 00f5bc5baa 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 03cafda7cd 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new c998823cd4 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 0072028b33 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 0f3dbe4a3e 139: onsuccess: #1753: 1: Success after binutils: 5 commits new ce5a469ae4 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 5bc804a0a9 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new 9c64f65513 142: onsuccess: #1761: 1: Success after gcc: 83 commits new ed08ce8701 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new c2bd0f06b7 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 6e437d97b7 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new bf25e292f9 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new c7c9cf714c 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new 527eee9530 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 49d5491d2b 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 673a7c8231 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 901712799d 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 4c00da7161 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 2202bd4a52 153: onsuccess: #1773: 1: Success after gcc: 4 commits new 2a80c4e5bb 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 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 (31e6ba536b) \ 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 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 50440 -> 53448 bytes 04-build_abe-gcc/console.log.xz | Bin 235420 -> 233364 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3808 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2820 -> 2528 bytes 07-check_regression/console.log.xz | Bin 4572 -> 5252 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 27 + 07-check_regression/results.compare | 26 +- 07-check_regression/results.compare2 | 40 +- 07-check_regression/results.regressions | 27 + 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 27 + sumfiles/g++.log.xz | Bin 2775480 -> 2762656 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 2387876 -> 2357212 bytes sumfiles/gcc.sum | 4512 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 907240 -> 910320 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204648 -> 204648 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 467232 -> 465100 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 2567 insertions(+), 2419 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_kernel/llvm-master-aarch64-stable-defconfig updated (9cec77fb8e -> ac7b4e4a8f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from 9cec77fb8e 13: onsuccess: #467: boot: Success after binutils/llvm/linux [...] new ac7b4e4a8f 14: onsuccess: #468: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1692 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30380 -> 30992 bytes 04-build_kernel_llvm/console.log.xz | Bin 65804 -> 66164 bytes 05-build_abe-qemu/console.log.xz | Bin 31484 -> 31756 bytes 06-build_linux/console.log.xz | Bin 22106980 -> 3352 bytes 07-boot_linux/console.log.xz | Bin 6284 -> 6288 bytes 08-check_regression/console.log.xz | Bin 4364 -> 4388 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 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_gnu_native_build/master-arm updated (4055ad88d0 -> e9404eb8bf)

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 4055ad88d0 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new e9404eb8bf 66: onsuccess: #469: 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 1676 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 50340 -> 52856 bytes 05-build_abe-gcc/console.log.xz | Bin 233508 -> 233800 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8880 -> 8488 bytes 08-build_abe-glibc/console.log.xz | Bin 233312 -> 232104 bytes 09-build_abe-gdb/console.log.xz | Bin 49820 -> 50956 bytes 10-check_regression/console.log.xz | Bin 4208 -> 4504 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_gnu_cross_check_gcc/master-aarch64 updated (c974eec8c9 -> 71f554bdb1)

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 c974eec8c9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards aaae8b9a98 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards eb0d2c2eb5 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 5e9ce2c692 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 67748ddce0 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 5037f3e509 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 47b3157434 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards f6f45ca686 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards ded5e9f481 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 2698a1617f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 66950a863c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards eb30d469e4 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 2b19bb66b6 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 4d72c7ac9d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards c294c6389d 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 72a938d90a 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards e640b68e9a 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 2e8c41fad0 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards c375c087fb 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards f4ef12ff19 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 2e4ea7bf31 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 45793d8734 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 7f766c23ac 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 259714adf3 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 0a89644c38 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 211e72c40f 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 44a311f1af 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 388f8e822f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards ca431d4021 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards feb7775395 124: onsuccess: #2159: 1: Success after linux: 23 commits discards c28effc580 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards f1b2e9923b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 9abdb76c14 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 9c434c2b37 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards b1c2e1657a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5fb91f1dd7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ce68806775 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards c61b3e5c94 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards af63e90745 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 7f8b2b5ed4 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 7c44c50b57 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8169b717df 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 3280b6a0b9 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 53c3ccb96b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards d84776fa4d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 1b252bc42f 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 1361dbb1f8 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 8069f52b3b 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards e851ef1544 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 17a724f0a0 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 795d96a765 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards cb931c623f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 2130e3b186 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 8369a8e0a3 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 50068afd4c 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards c837e522c2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1e2d6e079d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards e500a09daf 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 5ee2928305 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 10d78a0fab 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards a504260c24 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 39c355949b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 245c27491c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 355fa83df9 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 889d0699cc 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 65b97bca9c 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards c922711f71 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 3e7e4e7c33 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards bb23acee08 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 25b45f26e7 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7da9e9f1f8 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards a9e2080c11 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 35387dc2e7 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 81b44c860c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3fbb8d9cf6 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d21361a0ce 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 09e92d6465 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards ad5e9d3917 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb0cd6d0c5 75: onsuccess: 1: Successful build after linux: 44 commits discards 190b13b4ba 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 1c77c8c483 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ea23afa0e7 72: onsuccess: 1: Successful build after linux: 12 commits discards 9924ecf8d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 7c74861e72 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fa3cb83ba5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards a4d4532fd4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f44f50819e 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 4745c3dcb1 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 035093f380 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aefa48c3c6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 44ba1ba40d 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ceed1fdcff 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 7da0537923 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f3aaef0df4 60: onsuccess: 1: Successful build after glibc: 2 commits discards 73715f6186 59: onsuccess: 1: Successful build after binutils: 2 commits discards 93bf971ed4 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 7350e54aa3 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ad390a4e72 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ee3f07c7df 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 2d9302893b 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 1f1ca48756 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new f9894b2526 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 34ca317eef 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2b11c3cbe1 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 4d23312c09 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 48a6a6ebaa 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 61447effca 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 8ad950b6f9 59: onsuccess: 1: Successful build after binutils: 2 commits new 8890bfccff 60: onsuccess: 1: Successful build after glibc: 2 commits new 556572c05d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 0791c14d58 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 00c5a29a07 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new fc01bf115c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8d217635b6 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 48b5bd8c40 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 7e83936eb8 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new e064d825eb 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c04746aba0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new feb063d296 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new fb88d81a54 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new ce233d5e6b 72: onsuccess: 1: Successful build after linux: 12 commits new cbc8a6ee89 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8a32fc4488 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 74734d50ee 75: onsuccess: 1: Successful build after linux: 44 commits new 5c8ff8f4d5 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8f5c8cd4ff 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 5f9cb89224 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 3239c67024 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 390e1e966e 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8d364e5b6d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 5b62c17768 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new eca1677e17 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 79b23630d5 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new e5f153c843 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 27090cdfab 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new dbfc541e4b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 4d82e1c116 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 7030de2c24 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 7d8fd5fc42 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 702d6b42a3 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 4778ac950e 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 728856177d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 8a365cf2a5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new d1b2427d67 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new a82cf3602c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 3c0c6d495e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 6ebd5dadf6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 4c69320477 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 350d4713e0 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 628325fa6a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 24e54cb662 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 6d89c82827 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new b7dc133863 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 7e8e336a57 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new ab6208f50d 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new fc1155c886 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 487fe1ff7a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 25fb2ace23 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 12fae94892 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 0fc7da07e8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 08e4d4814f 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new fbc1b40a3d 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new fd488ab35c 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 213acea74c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 93e8cfecbd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new b85803a92f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 5dc4416720 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b9e067cf8a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 87eb4bce48 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 87870cea6c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 796dd6cfbc 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 4cde71f5fe 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 6ce8802fd0 124: onsuccess: #2159: 1: Success after linux: 23 commits new 18e91df37e 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 13d18aac66 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new a4a18fe655 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 09b1c5ba75 128: onsuccess: #2163: 1: Success after linux: 23 commits new cc9b35b3b1 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new a2cbf0188f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new abf11365a2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 9a56e7436f 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new fefeaae2cc 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new fa84d0d547 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 539572a8d3 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new df2d235808 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 30e5ede381 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 2bfe33c0af 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 6b19e634cf 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 3cb57b59bb 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 516568f786 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 68f3ff84c8 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new a07bcdb306 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 650dcc5464 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new a813b5b6a1 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new b3db7cc387 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 84dc5a2b68 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new bbbf11ee45 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new a2a347de9f 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 2edc7eea38 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 864296c798 151: onsuccess: #2186: 1: Success after gcc: 2 commits new f6c92d1503 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 25cc411511 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 71f554bdb1 154: onsuccess: #2189: 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 (c974eec8c9) \ 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 1704 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30232 -> 30832 bytes 04-build_abe-stage1/console.log.xz | Bin 72116 -> 72680 bytes 06-build_abe-linux/console.log.xz | Bin 8944 -> 8928 bytes 07-build_abe-glibc/console.log.xz | Bin 239304 -> 240008 bytes 08-build_abe-stage2/console.log.xz | Bin 202832 -> 203648 bytes 09-build_abe-gdb/console.log.xz | Bin 37484 -> 38152 bytes 10-build_abe-qemu/console.log.xz | Bin 31944 -> 31844 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3956 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2448 -> 2880 bytes 13-check_regression/console.log.xz | Bin 31100 -> 18844 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 308 +- 13-check_regression/mail-body.txt | 206 +- 13-check_regression/results.compare | 313 +- 13-check_regression/results.compare2 | 8066 +++++++++---------------------- 13-check_regression/results.regressions | 46 +- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 208 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 46 +- sumfiles/g++.log.xz | Bin 3433428 -> 3415412 bytes sumfiles/g++.sum | 92 +- sumfiles/gcc.log.xz | Bin 2999004 -> 3030792 bytes sumfiles/gcc.sum | 7486 +++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 1029608 -> 1029700 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202576 -> 202448 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423868 -> 423268 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 6766 insertions(+), 10146 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/gnu-master-arm-mainline-allmodconfig updated (583bc91aae -> 9b0eca1a58)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 583bc91aae 18: onsuccess: #567: 33: Success after binutils: 22 commits new 9b0eca1a58 19: onsuccess: #569: 33: Success after binutils/gcc/linux/qe [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1652 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29912 -> 31656 bytes 04-build_abe-stage1/console.log.xz | Bin 90160 -> 90312 bytes 05-build_abe-qemu/console.log.xz | Bin 31872 -> 31616 bytes 06-build_linux/console.log.xz | Bin 4508 -> 3568 bytes 08-check_regression/console.log.xz | Bin 3016 -> 4504 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- 17 files changed, 34 insertions(+), 22 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_native_check_gcc/release-aarch64 updated (318c4bcf00 -> 6b93735c88)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/release-aarch64 in repository toolchain/ci/base-artifacts. from 318c4bcf00 15: onsuccess: #197: 1: Success after binutils/gcc/gdb: 9 commits new 6b93735c88 16: onsuccess: #198: 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 1700 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 38508 -> 38104 bytes 04-build_abe-gcc/console.log.xz | Bin 208420 -> 208544 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8604 bytes 07-build_abe-glibc/console.log.xz | Bin 240736 -> 239328 bytes 08-build_abe-gdb/console.log.xz | Bin 36708 -> 36840 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3852 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2448 -> 2456 bytes 11-check_regression/console.log.xz | Bin 5712 -> 7176 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 7 +- 11-check_regression/mail-body.txt | 65 +- 11-check_regression/results.compare | 33 +- 11-check_regression/results.compare2 | 107 +- 11-check_regression/results.regressions | 33 +- 12-update_baseline/console.log | 2 +- 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 | 67 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 33 +- sumfiles/g++.log.xz | Bin 3668224 -> 3683476 bytes sumfiles/g++.sum | 156 +- sumfiles/gcc.log.xz | Bin 3165728 -> 3172888 bytes sumfiles/gcc.sum | 4846 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1073064 -> 1065624 bytes sumfiles/gfortran.sum | 72 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214572 -> 214200 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 437708 -> 434344 bytes sumfiles/libstdc++.sum | 24 +- 43 files changed, 2798 insertions(+), 2729 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