Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig updated (2e1c686f03 -> 00a62f1e36)

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-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 2e1c686f03 24: onsuccess: #499: all: Success after binutils/llvm: 309 commits new 00a62f1e36 25: onsuccess: #500: all: Success after binutils/llvm/qemu: [...] 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 1964 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30672 -> 30376 bytes 04-build_kernel_llvm/console.log.xz | Bin 65828 -> 64660 bytes 05-build_abe-qemu/console.log.xz | Bin 32300 -> 32116 bytes 06-build_linux/console.log.xz | Bin 3532 -> 3436 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3732 -> 4064 bytes dashboard/dashboard-generate.sh | 4 ++-- git/binutils_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 | 28 ++++++++++++++-------------- 16 files changed, 22 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (05ffdefafb -> d3c2af1d74)

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-aarch64 in repository toolchain/ci/base-artifacts. from 05ffdefafb 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] new d3c2af1d74 75: onsuccess: #491: 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 1684 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38280 -> 38220 bytes 05-build_abe-gcc/console.log.xz | Bin 213812 -> 215712 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 9296 -> 8920 bytes 08-build_abe-glibc/console.log.xz | Bin 242972 -> 241544 bytes 09-build_abe-gdb/console.log.xz | Bin 38792 -> 38220 bytes 10-check_regression/console.log.xz | Bin 4428 -> 4688 bytes 11-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 4 ++-- 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 +++++++++++++++++------------------ 20 files changed, 37 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-allnoconfig updated (213e66a244 -> 4ecb64466a)

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-norov-allnoconfig in repository toolchain/ci/base-artifacts. from 213e66a244 12: onsuccess: #41: all: Success after binutils/gcc/linux/qe [...] new 4ecb64466a 13: onsuccess: #42: all: Success after binutils/gcc/qemu: 39 [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29976 -> 29936 bytes 04-build_abe-stage1/console.log.xz | Bin 90812 -> 90060 bytes 05-build_abe-qemu/console.log.xz | Bin 31504 -> 31412 bytes 06-build_linux/console.log.xz | Bin 4048 -> 4036 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4428 -> 3932 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 4 ++-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled updated (ae07b49edf -> edadc6afde)

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_profiled in repository toolchain/ci/base-artifacts. from ae07b49edf 64: onsuccess: #463: 2: Success after binutils/gcc: 91 commits new edadc6afde 65: onsuccess: #464: 2: Success after binutils/gcc: 37 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 1704 -> 1624 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 50948 -> 50516 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 937516 -> 938044 bytes 06-check_regression/console.log.xz | Bin 3148 -> 3208 bytes 06-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 4 ++-- 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 ++++++++++---------- 13 files changed, 19 insertions(+), 19 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (8dd6116793 -> f5e9dcbe0c)

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_O3 in repository toolchain/ci/base-artifacts. from 8dd6116793 66: onsuccess: #488: 2: Success after binutils/gcc: 51 commits new f5e9dcbe0c 67: onsuccess: #489: 2: Success after binutils/gcc: 23 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 1680 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 53444 -> 51192 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 464156 -> 463572 bytes 06-check_regression/console.log.xz | Bin 3156 -> 3152 bytes dashboard/dashboard-generate.sh | 4 ++-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-norov-defconfig updated (59014d6c6b -> 91b4abd66a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-norov-defconfig in repository toolchain/ci/base-artifacts. from 59014d6c6b 12: onsuccess: #41: boot: Success after binutils/gcc/linux/q [...] new 91b4abd66a 13: onsuccess: #42: boot: Success after binutils/gcc/qemu: 2 [...] 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30012 -> 30096 bytes 04-build_abe-stage1/console.log.xz | Bin 87136 -> 86448 bytes 05-build_abe-qemu/console.log.xz | Bin 31412 -> 31532 bytes 06-build_linux/console.log.xz | Bin 3468 -> 3460 bytes 07-boot_linux/console.log.xz | Bin 5656 -> 5644 bytes 08-check_regression/console.log.xz | Bin 4248 -> 3696 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 4 ++-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 18 files changed, 24 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (40a2190b94 -> 33f8f1e5b8)

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 40a2190b94 203: onsuccess: #1823: 1: Success after binutils/gcc: 3 commits discards d6a49f6998 202: onsuccess: #1822: 1: Success after binutils/gcc: 10 commits discards 45e9afa476 201: onsuccess: #1821: 1: Success after binutils/gcc: 19 commits discards 91f44fc71c 200: onsuccess: #1820: 1: Success after binutils/gcc: 19 commits discards 7ed5e4cccb 199: onsuccess: #1819: 1: Success after binutils/gcc: 5 commits discards a7284e553e 198: onsuccess: #1818: 1: Success after binutils/gcc: 5 commits discards 96e2a15bc8 197: onsuccess: #1817: 1: Success after gcc: 13 commits discards 105477802f 196: onsuccess: #1816: 1: Success after binutils/gcc: 5 commits discards 050e91598c 195: onsuccess: #1815: 1: Success after binutils/gcc: 4 commits discards 0f830e25d0 194: onsuccess: #1814: 1: Success after binutils/gcc: 8 commits discards 22878cd585 193: onsuccess: #1813: 1: Success after binutils/gcc: 17 commits discards e900bbdbc5 192: onsuccess: #1812: 1: Success after binutils/gcc: 11 commits discards 8de08d5023 191: onsuccess: #1811: 1: Success after binutils/gcc: 6 commits discards 16a63e2eec 190: onsuccess: #1810: 1: Success after binutils/gcc: 6 commits discards 67167ac3d1 189: onsuccess: #1809: 1: Success after binutils/gcc: 33 commits discards 49cd7457b4 188: onsuccess: #1808: 1: Success after binutils/gcc: 15 commits discards f49b1070f0 187: onsuccess: #1807: 1: Success after binutils/gcc: 7 commits discards 09b46af5e7 186: onsuccess: #1806: 1: Success after binutils/gcc: 11 commits discards 0677b0dd23 185: onsuccess: #1805: 1: Success after binutils/gcc: 18 commits discards 100d0c6a80 184: onsuccess: #1804: 1: Success after binutils/gcc: 16 commits discards a97b642538 183: onsuccess: #1803: 1: Success after binutils/gcc: 4 commits discards ac5c151c1c 182: onsuccess: #1802: 1: Success after gcc: 2 commits discards 620eff3a15 181: onsuccess: #1801: 1: Success after basepoints/gcc-13-31 [...] discards e8a57cb473 180: onsuccess: #1800: 1: Success after binutils/gcc: 2 commits discards 6319a3f21c 179: onsuccess: #1799: 1: Success after basepoints/gcc-13-31 [...] discards 9cb3a836a0 178: onsuccess: #1798: 1: Success after gdb-12-branchpoint-2 [...] discards eab70a0d4b 177: onsuccess: #1797: 1: Success after gdb-12-branchpoint-2 [...] discards 5f07f425f0 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits discards 456cf0fe83 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits discards e4eaee8874 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits discards c7cfea2c79 173: onsuccess: #1793: 1: Success after gcc: 12 commits discards a0bd4adbba 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits discards 32c9095b1f 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits discards 501e41de07 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits discards 83bb441eaf 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits discards 04222251f7 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits discards abdc978d86 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards 9152d2e368 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards 6c6b0fd11f 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards 352ccf432c 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards 6541aa1089 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards 308abfe5ff 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards 19250459ab 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards b45117d0ad 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards 33a8167bb4 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards bff55ec2ef 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards f13d46d4ba 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards a2af430c94 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards 2212f811b3 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards c1a6420483 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 8ce279ce30 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards 70dfe341bd 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 22324dd4e2 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards d7b15012ad 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards d011faae6c 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards 8299dc78c7 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 4af1fee9e2 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards c53680a000 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 8d7d2edb84 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards c9d655f5aa 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards ab8f7494a9 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards a78775194f 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 595932b42d 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards 68636ee507 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 7c10a96ba6 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards 06773dc642 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 3b16af6288 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 9bb80f1e0e 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards ce50a06e44 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 4b466f9d86 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 969e3ee63c 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards d7035c0d4e 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards e6d638db5f 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards b5c3b6d4cd 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 44ef10077a 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards d9bd17f0f4 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 17be7ec614 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards afe09d85b1 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 89ebb216a0 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards da0b3d2f8a 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards dc28f43269 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 35bbde4e54 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 6c78412e49 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 3a1d1c119d 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 9a9e6afed9 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 9b89940816 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 216e86e11e 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 13ffda7773 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 6173f9e6a8 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 7db843fd0d 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 7afd22e331 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 2f39ffc9f9 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards daf8fa2eac 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 14c91e71f6 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 893190d419 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 71ecbf47d3 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 5d4c5061ca 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 7d7b91af66 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 6811f9d43a 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards 42419f4eab 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards cc4e51979c 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 8f603668e0 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new d96a2c8c2c 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 2170fa3f0e 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 74e86c1bc2 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 44fee82c8a 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 2edb6976ad 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 09e2654939 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 5b10ec5301 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 225aa20c72 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new a5080d9f12 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new bc8054b842 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new eea2a07be9 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 5921291aa0 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 09cdf1de6f 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new a36f4abd2e 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new ad6832c4d4 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new a55f4fbc4f 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 17e550d890 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 760928799e 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 753f28dfd3 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new d650a9f0a3 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new aeffa1f33f 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 4b9c4c3a26 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new eac916dacd 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new a5ec0dde0d 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new a3a5b6a59d 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 56638a9b7d 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 34d3f2b301 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 6622eeed37 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 8f873080ae 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new b74f6f4140 133: onsuccess: #1733: 1: Success after binutils: 3 commits new b70ca7e86a 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 7f4cebafa7 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 5a864e5e08 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 90f7cdbb19 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 33759e8fbe 138: onsuccess: #1749: 1: Success after binutils: 5 commits new d5967e2d19 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 75f929114d 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 997b767268 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new 7d3f426b13 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 97954b07d5 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 597b927075 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new ca0ea047b4 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new 907a2b805c 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new e4425fcac3 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new 5da22c0012 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 0f8a7710c1 149: onsuccess: #1769: 1: Success after gcc: 3 commits new b8485ecb73 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new f7e4443088 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new a0c3ca747c 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 5dd66f2eb4 153: onsuccess: #1773: 1: Success after gcc: 4 commits new 9af196909f 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new 1796d21aa0 155: onsuccess: #1775: 1: Success after binutils: 2 commits new 253b654311 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new 456f76ed95 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new f480cff20f 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new 87f34c1b82 159: onsuccess: #1779: 1: Success after gcc: 2 commits new 80ed8fd30f 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new 9f4fb3987d 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new 3e7bff299b 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new 820fbb6579 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new 0c9fdd4268 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new 0434a3e289 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new 56cd1a5904 166: onsuccess: #1786: 1: Success after gcc: 10 commits new f96a6415cb 167: onsuccess: #1787: 1: Success after gcc: 8 commits new 691a1076ad 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits new bf998b7c70 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits new 1d637638a5 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits new 0221cdb25d 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits new 8c4273f0f1 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits new 6a4630bc81 173: onsuccess: #1793: 1: Success after gcc: 12 commits new 7745b048cc 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits new dfb2ab08a2 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits new 8e4f8e57f1 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits new 4dd6d0c653 177: onsuccess: #1797: 1: Success after gdb-12-branchpoint-2 [...] new 98a8fb27c7 178: onsuccess: #1798: 1: Success after gdb-12-branchpoint-2 [...] new f08f0e16fd 179: onsuccess: #1799: 1: Success after basepoints/gcc-13-31 [...] new 6cda0ed05e 180: onsuccess: #1800: 1: Success after binutils/gcc: 2 commits new 00a97fdbd5 181: onsuccess: #1801: 1: Success after basepoints/gcc-13-31 [...] new 55e952c6ea 182: onsuccess: #1802: 1: Success after gcc: 2 commits new 47de459388 183: onsuccess: #1803: 1: Success after binutils/gcc: 4 commits new fae726cd61 184: onsuccess: #1804: 1: Success after binutils/gcc: 16 commits new 996649dd13 185: onsuccess: #1805: 1: Success after binutils/gcc: 18 commits new 79d3abaadc 186: onsuccess: #1806: 1: Success after binutils/gcc: 11 commits new 54735faa01 187: onsuccess: #1807: 1: Success after binutils/gcc: 7 commits new 45ef1c1aec 188: onsuccess: #1808: 1: Success after binutils/gcc: 15 commits new ae38ebc8de 189: onsuccess: #1809: 1: Success after binutils/gcc: 33 commits new b3594abca8 190: onsuccess: #1810: 1: Success after binutils/gcc: 6 commits new db2ffd44ae 191: onsuccess: #1811: 1: Success after binutils/gcc: 6 commits new ae09326cb1 192: onsuccess: #1812: 1: Success after binutils/gcc: 11 commits new dd5cd802ce 193: onsuccess: #1813: 1: Success after binutils/gcc: 17 commits new 2cb5badc09 194: onsuccess: #1814: 1: Success after binutils/gcc: 8 commits new 583f4a6228 195: onsuccess: #1815: 1: Success after binutils/gcc: 4 commits new 6a18986e8b 196: onsuccess: #1816: 1: Success after binutils/gcc: 5 commits new 162dcb41c2 197: onsuccess: #1817: 1: Success after gcc: 13 commits new 6a816ab514 198: onsuccess: #1818: 1: Success after binutils/gcc: 5 commits new 6d8447fe93 199: onsuccess: #1819: 1: Success after binutils/gcc: 5 commits new 56dd6f6a58 200: onsuccess: #1820: 1: Success after binutils/gcc: 19 commits new fd89385f48 201: onsuccess: #1821: 1: Success after binutils/gcc: 19 commits new ee643d94ed 202: onsuccess: #1822: 1: Success after binutils/gcc: 10 commits new a86ccf49fa 203: onsuccess: #1823: 1: Success after binutils/gcc: 3 commits new 33f8f1e5b8 204: onsuccess: #1824: 1: Success after gdb-12-branchpoint-2 [...] 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 (40a2190b94) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (33 [...] 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 1720 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 50416 -> 50824 bytes 04-build_abe-gcc/console.log.xz | Bin 233120 -> 233208 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3848 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2384 -> 2372 bytes 07-check_regression/console.log.xz | Bin 5044 -> 4804 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 25 +- 07-check_regression/results.compare2 | 65 +- 07-check_regression/results.regressions | 27 - 08-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 4 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 27 - sumfiles/g++.log.xz | Bin 2790316 -> 2796344 bytes sumfiles/g++.sum | 114 +- sumfiles/gcc.log.xz | Bin 2391932 -> 2367032 bytes sumfiles/gcc.sum | 4248 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 904048 -> 921132 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206292 -> 206056 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 467640 -> 467800 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2314 insertions(+), 2386 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-norov-allyesconfig updated (edeeeedcbe -> b93cb903af)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-norov-allyesconfig in repository toolchain/ci/base-artifacts. from edeeeedcbe 21: onsuccess: #74: 20991: Success after binutils/llvm/linux [...] new b93cb903af 22: onsuccess: #75: 20991: Success after binutils/llvm/qemu: [...] 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30548 -> 30060 bytes 04-build_kernel_llvm/console.log.xz | Bin 65340 -> 65740 bytes 05-build_abe-qemu/console.log.xz | Bin 31484 -> 31492 bytes 06-build_linux/console.log.xz | Bin 5164 -> 5184 bytes 08-check_regression/console.log.xz | Bin 4508 -> 4088 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 4 ++-- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (374433c471 -> e44d3c7f73)

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 374433c471 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards a24eae5c79 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 0f8ee11b16 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards fdcf8cbd03 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 7bf376107a 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 4422cd83f2 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards e608eb1bc7 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 46e3d848d7 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 05d156c474 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 04d6c0cef2 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 9ab627b4c7 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 74cfa6b1b3 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 22de9b460a 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards e2bb80b4a7 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 50cf8c3a15 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 51565caee4 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards c242a7adb7 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 26653cee21 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 2e75ab752f 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards ea9b0e6a18 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 6686584975 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 1a3d86db7e 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 79db62ddb8 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 630cb522cd 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 4661598829 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards c77e1ccb46 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 6512c13a40 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 2a2062d213 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 179c332ef0 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 7b8b528b92 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards b52c847998 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards ff039a889a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards fad5c53acb 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards b6e8fbb567 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 3e175b18fc 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 7918b94d88 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 61e8ceda6e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards c622c10288 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 6e2b53c280 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 34eddc4bb3 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 71216323d2 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 0e01eb92dc 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards d5feff19ad 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards c0bba27ded 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards f6d0100305 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 131068fd79 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 33158c8b0e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 6884700a56 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards bd2363b5f9 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1d24009fa5 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards fe9ac06d3e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards be7f7a0537 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards c8eb7a82ac 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 9133fa3a5f 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 808849064a 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 110c03f9aa 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 36372f1a2a 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d8a14fc173 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards e0c58e1613 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 00d1f747cd 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards af4c2229fc 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 043663f30d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 304ae489e3 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 7eb6ac4e9b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 30b91d4353 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 1f57b0a7e9 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 9d23c68f12 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 3d69e52ee9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 4027501687 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards f0b999c8ac 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 6cb2dd28c0 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 33eeb5bff9 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 42a968ef93 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards d0a1eccdcb 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards f9121bb434 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 0dc0726766 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 560a19a62e 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 8cec83cc56 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards a097e826a9 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 3b03554fb8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 8639163402 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 913676a0de 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 2ac8372764 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 08cd48ef31 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 61a40b79cf 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards d8f4ea7a1c 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards dc996d1964 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 28455f1bf0 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 14bbb72dce 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards acaf0c5f7e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 3bddda2518 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards a5a422dcb1 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 0775d22207 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 508fa6a451 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards fe710e93ed 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 971e4149f0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 51cc57ec13 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7e752020cc 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards b7974004f4 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 65ca128afc 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 8629e193d9 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new afaefdd6ba 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6ca2b04014 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ca9e6d5849 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 4836253c2d 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new b98f3db292 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a7e73376e5 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new ac0f9fd402 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3df8fafd81 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 8d46ce6379 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 4f60183750 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new b0f58a9863 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 99bb46f774 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 5ed3a3d43c 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b40c27fd77 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 67a3d655ab 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 9da5f973f4 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new abde820bfd 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new c35d5a6976 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 0c87afd334 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new aea5504c78 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new e8f145c73f 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 1eedbd956f 101: onsuccess: #2130: 1: Success after binutils: 81 commits new a67a74ac84 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 4693962198 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 517b02951e 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new cc08468e90 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 93cd3735e6 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 4023b7ae4a 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 40e61a19d7 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new c878385a89 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new c9a174a677 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new b2a3a66825 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 9c46636cb4 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 3d0a1bb961 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new ac4ac089e0 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 8e271e87ee 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 76b128627a 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 93dd77eed4 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new fa6e6f68fe 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 86bc991d51 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new f2d8ef04bb 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 9c3c93425a 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 72727ad3da 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 252ee380db 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new f6b726a35b 124: onsuccess: #2159: 1: Success after linux: 23 commits new 51d723a223 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 1bd56deaa6 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 2787e963b6 127: onsuccess: #2162: 1: Success after gcc: 9 commits new b34067ea0a 128: onsuccess: #2163: 1: Success after linux: 23 commits new 2914471fef 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new ce306dc617 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 8724a774d4 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new c10ef7f7fa 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new f9b2cc0260 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 94e51d143b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 998b89eb7f 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 9915b8965a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 145e3ba69b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 1f5fedeb9e 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 912bec68b5 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new bec1deea4a 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 7a078112f0 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 5faa33ab5e 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 022d7861e7 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 4f53cdfc0c 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 048b03c6c1 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9cb5a02b7e 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 3b1c131f5b 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new a246f8eb73 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 5014e7d5da 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new bcd023ee08 150: onsuccess: #2185: 1: Success after gcc: 3 commits new ff45d9f1b5 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 9eef59cc10 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new bed9285855 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 862cc6f423 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new ba5ad6f318 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new f331e9c876 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 380baefb9a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new d5084f2fbf 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new c96e2511c9 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 9e06181faf 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new ce85efbe51 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 681197b148 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 6fb9fa27f3 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 32e8b56ba4 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 968e17a7ca 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 66fc539544 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 76d57c66d7 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 47d3bd0d81 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 740eae5ceb 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 5f523565c0 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 6e02cc82cc 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 4e19132949 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new f67b7b441b 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 68f3e96245 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 9b08390563 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new f602f2fea5 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 95bf095452 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 2bfb1a407c 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 7c9c6cb486 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new dfdb8ed559 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new e44d3c7f73 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] 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 (374433c471) \ 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 1732 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 31020 -> 30244 bytes 04-build_abe-stage1/console.log.xz | Bin 72812 -> 72452 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8812 -> 8820 bytes 07-build_abe-glibc/console.log.xz | Bin 239588 -> 239312 bytes 08-build_abe-stage2/console.log.xz | Bin 204876 -> 204344 bytes 09-build_abe-gdb/console.log.xz | Bin 37984 -> 37620 bytes 10-build_abe-qemu/console.log.xz | Bin 31692 -> 31968 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2860 -> 2608 bytes 13-check_regression/console.log.xz | Bin 7660 -> 9780 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 96 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 91 +- 13-check_regression/results.compare2 | 439 ++- 13-check_regression/results.regressions | 94 +- 14-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 4 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 94 +- sumfiles/g++.log.xz | Bin 3434820 -> 3406660 bytes sumfiles/g++.sum | 224 +- sumfiles/gcc.log.xz | Bin 3024176 -> 3039020 bytes sumfiles/gcc.sum | 5552 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1034648 -> 1036160 bytes sumfiles/gfortran.sum | 131 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202680 -> 203724 bytes sumfiles/libgomp.sum | 102 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 421780 -> 416724 bytes sumfiles/libstdc++.sum | 16 +- 46 files changed, 3938 insertions(+), 3509 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allyesconfig updated (b4768db4f0 -> 22cb9a46f6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from b4768db4f0 19: onsuccess: #417: all: Success after binutils/gcc/linux: [...] new 22cb9a46f6 20: onsuccess: #418: all: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30092 -> 29876 bytes 04-build_abe-stage1/console.log.xz | Bin 86668 -> 86580 bytes 05-build_abe-qemu/console.log.xz | Bin 31516 -> 32276 bytes 06-build_linux/console.log.xz | Bin 3292 -> 3300 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3744 -> 4148 bytes 08-check_regression/mail-body.txt | 6 ++++-- dashboard/dashboard-generate.sh | 4 ++-- 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 | 8 +++++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 34 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 7 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022