Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig updated (e8e78a9be8 -> 83bb732c5f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from e8e78a9be8 18: onsuccess: #490: 33: Success after binutils/gcc/linux/qe [...] new 83bb732c5f 19: onsuccess: #491: 33: Success after binutils/gcc/qemu: 16 [...] 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 1708 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 31196 -> 30312 bytes 04-build_abe-stage1/console.log.xz | Bin 73612 -> 72932 bytes 05-build_abe-qemu/console.log.xz | Bin 31604 -> 32132 bytes 06-build_linux/console.log.xz | Bin 3728 -> 3684 bytes 08-check_regression/console.log.xz | Bin 4388 -> 4088 bytes dashboard/dashboard-generate.sh | 12 ++++++++- dashboard/dashboard-push.sh | 5 ++++ .../results-functional.json | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 5 ++++ mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++----------- 18 files changed, 41 insertions(+), 21 deletions(-) copy dashboard/{squad => squad-vs-first}/results-functional.json (100%) -- 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_gdb/master-arm updated (a715603601 -> a710bf23fb)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from a715603601 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new a710bf23fb 64: onsuccess: #543: 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 1688 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52684 -> 52224 bytes 04-build_abe-gcc/console.log.xz | Bin 237000 -> 234192 bytes 06-build_abe-linux/console.log.xz | Bin 9176 -> 8756 bytes 07-build_abe-glibc/console.log.xz | Bin 234744 -> 233348 bytes 08-build_abe-gdb/console.log.xz | Bin 50200 -> 49396 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2296 -> 2140 bytes 11-check_regression/console.log.xz | Bin 14420 -> 15956 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 38 +- 11-check_regression/mail-body.txt | 180 +- 11-check_regression/results.compare | 82 +- 11-check_regression/results.compare2 | 4389 +++++++++++-------- 11-check_regression/results.regressions | 82 +- 12-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 12 +- dashboard/dashboard-push.sh | 5 + .../score/results-functional.json | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 5 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 182 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 82 +- sumfiles/gdb.log.xz | Bin 1752828 -> 1722692 bytes sumfiles/gdb.sum | 4514 +------------------- 33 files changed, 3114 insertions(+), 6520 deletions(-) copy dashboard/{squad => squad-vs-first}/score/results-functional.json (100%) -- 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/master-aarch64 updated (f2128a43c0 -> 24d3d8aae4)

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 f2128a43c0 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 24d3d8aae4 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] 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 1712 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 38408 -> 37980 bytes 04-build_abe-gcc/console.log.xz | Bin 215640 -> 213580 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8720 bytes 07-build_abe-glibc/console.log.xz | Bin 241108 -> 241700 bytes 08-build_abe-gdb/console.log.xz | Bin 37812 -> 37388 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3476 -> 2692 bytes 11-check_regression/console.log.xz | Bin 6580 -> 6132 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 53 +- 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 145 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 12 +- dashboard/dashboard-push.sh | 5 + .../score/results-functional.json | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- jenkins/dashboard-push.sh | 5 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 55 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 27 + sumfiles/g++.log.xz | Bin 3705940 -> 3712136 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 3246000 -> 3257152 bytes sumfiles/gcc.sum | 4382 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1084764 -> 1078708 bytes sumfiles/gfortran.sum | 132 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219724 -> 220048 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 449116 -> 445568 bytes sumfiles/libstdc++.sum | 12 +- 45 files changed, 2608 insertions(+), 2496 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 copy dashboard/{squad => squad-vs-first}/score/results-functional.json (100%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 95b6a60050 14: onsuccess: #420: all: Success after binutils/gcc/linux/q [...] new a2ea12a077 15: onsuccess: #421: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1708 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30564 -> 29952 bytes 04-build_abe-stage1/console.log.xz | Bin 87700 -> 86172 bytes 05-build_abe-qemu/console.log.xz | Bin 31184 -> 31496 bytes 06-build_linux/console.log.xz | Bin 3304 -> 3272 bytes 07-boot_linux/console.log.xz | Bin 496 -> 480 bytes 08-check_regression/console.log.xz | Bin 4096 -> 4136 bytes 08-check_regression/mail-body.txt | 6 ++-- dashboard/dashboard-generate.sh | 12 +++++++- dashboard/dashboard-push.sh | 5 ++++ .../results-functional.json | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 5 ++++ mail/jira-body.txt | 2 +- mail/mail-body.txt | 8 ++++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++----------- results | 4 ++- 22 files changed, 55 insertions(+), 29 deletions(-) copy dashboard/{squad => squad-vs-first}/results-functional.json (100%) -- 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 (e80dfb8e8d -> 4a0398c13f)

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 e80dfb8e8d 181: onsuccess: #1801: 1: Success after basepoints/gcc-13-31 [...] discards ab346977f0 180: onsuccess: #1800: 1: Success after binutils/gcc: 2 commits discards da1dc1b2ce 179: onsuccess: #1799: 1: Success after basepoints/gcc-13-31 [...] discards fdfe498369 178: onsuccess: #1798: 1: Success after gdb-12-branchpoint-2 [...] discards 2cd5237a36 177: onsuccess: #1797: 1: Success after gdb-12-branchpoint-2 [...] discards a91d2f7ad7 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits discards 339d46cea7 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits discards 55b0b87fc2 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits discards 3f6079b24c 173: onsuccess: #1793: 1: Success after gcc: 12 commits discards b251e33c12 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits discards 863195b81b 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits discards 69c4b5a0b0 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits discards 4eafc8c94f 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits discards 5ad28b9c97 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits discards b2c9739e73 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards ee0dd3c7f7 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards 96a1ca6239 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards 9a724ada6c 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards ac18bf3fba 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards 050b1171f1 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards 907b206f69 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards 3ae0b7f645 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards 9ec3e626e2 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards 23706cfadc 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards 1e66d13586 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 1d47512ea0 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards a8991cb973 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards 7439a92b15 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 02f006a971 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards b9d0fdabe0 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 49a008cd2d 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards d45f145900 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards c1c93ee9c3 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards 7c4cd4e027 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 6e8c4527f4 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards 01cc3550ef 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards c8730da9e3 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 9ff504ab08 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 741109437c 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards 4a5d50ed1f 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 636cef8945 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards c38420e497 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards b2be9c7a56 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards e1f0dbeb7d 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 0d794e7042 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards afdd5a8c71 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards b95cafa0a9 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 1f1a40233b 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards beef996d18 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 5a51f04fda 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards cd07a77056 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 198d360645 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 7264b3a765 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 263d686866 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 67c4df7bf2 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 51c4e46529 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards c6f99b18c2 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards fbaa219abf 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards e5b5ec6a35 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 4209b6e72e 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 7d4cfa2068 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 55c8711718 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards abee33d1c2 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards c9ab17561d 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 5e93f18589 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 88cedf35d6 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 8f24d2cb92 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 110ebb2e60 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards b653182eb0 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 20a3c4462d 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 2ff8226ed1 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 91274c6b5a 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 6b9f39b1ad 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 4ca00b90bb 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards d570431826 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards dd93e78ae7 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 198f9300b3 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards 3f4e35efbd 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 4fb381e5cd 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 5f59f15141 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards b3c79fc520 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 36b230fa62 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards e18b46d026 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 3dce9a7f7d 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 487c2d78df 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 68efc467ff 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards b5722df5ef 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 6a95cfecbc 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards d559265987 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 44207f2374 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 638dec7b3b 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 505da25378 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 6798d9ecc4 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 35c4065487 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 995bacb9fc 87: onsuccess: 1: Success after gcc: 6 commits discards 9670ea392f 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards a782259a45 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards d2a0b33c13 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 58eddb1d51 83: onsuccess: 1: Success after gcc: 14 commits discards f7c03cc4e9 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 5b69d9d594 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 1e0e62c62a 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 0b38e97a3c 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 1689dd58e3 83: onsuccess: 1: Success after gcc: 14 commits new 0ac652cb7e 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 080c61e80d 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 7344b1dec7 86: onsuccess: 1: Success after binutils/gcc: 8 commits new e26baeedf5 87: onsuccess: 1: Success after gcc: 6 commits new eddcd3cf2b 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 71d05cdc30 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 631fa5e4f7 90: onsuccess: #1645: 1: Success after gcc: 2 commits new ce3f1a1fef 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new e753fb25da 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 66014ac26f 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new b544d7268c 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new cc9e0f3b4a 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 4ab85ade72 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 3db6554668 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 84f053dc10 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new a4ad0daf76 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new e7af811ce4 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 0d6985c3fd 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 7900c40ea2 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 37e3aadd58 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 3b65bf0935 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 1f3a6b4678 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 2a067e1612 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 4828bf80ab 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 5ef1376d5c 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new b60f8a365a 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 202c9b2d37 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new e1ceae815f 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new d39429da46 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 70f3053e63 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 7c567cceb3 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 596b742408 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 75595be68b 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new ec9c990be8 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new c3938dc339 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 30f3c9d4e4 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 70110764d6 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new b65a32266b 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new d1cbd5e805 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 383ef6d4db 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 2275faf29f 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 09f6cd18f5 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new e26208a043 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new cdc855bdcd 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 3115a64272 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new ebc28ae6f4 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 3e08d5b6a2 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 922908012d 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 7b5e3e4648 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 796632e319 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 3d37c2cdbc 134: onsuccess: #1736: 1: Success after binutils: 3 commits new cf7119ac30 135: onsuccess: #1739: 1: Success after binutils: 4 commits new a628b00dd2 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 2391f32a5f 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new edc1c9c15a 138: onsuccess: #1749: 1: Success after binutils: 5 commits new eb681e11e1 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 052b09ce5b 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 7f453e5e22 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new c5c7c5715a 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 2af0b844e0 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 65f8be8138 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 4fc8e74390 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new df8241071a 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 2593860ddc 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new f114bd1c62 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new b9c238524e 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 9e459f85a2 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 56905cb347 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 96d9836956 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 8fffb3cd7e 153: onsuccess: #1773: 1: Success after gcc: 4 commits new 8e55870769 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new f52bf2b794 155: onsuccess: #1775: 1: Success after binutils: 2 commits new e1ed675ccd 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new c5a7842306 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new 233375413f 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new 828100073a 159: onsuccess: #1779: 1: Success after gcc: 2 commits new c3c1a4dd39 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new 9fbebbb71c 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new e3c95a9223 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new 205580585c 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new 44d2d3ec3b 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new c220e372c0 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new 82fa7100eb 166: onsuccess: #1786: 1: Success after gcc: 10 commits new 44173cd2da 167: onsuccess: #1787: 1: Success after gcc: 8 commits new c7d75bb635 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits new 4a4863ed28 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits new 470a8a0766 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits new 61af6a4dbc 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits new d0568413d7 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits new d1d1e058f1 173: onsuccess: #1793: 1: Success after gcc: 12 commits new c9aa2440d3 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits new c3b75136bc 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits new eecfa0553c 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits new 4b873686dd 177: onsuccess: #1797: 1: Success after gdb-12-branchpoint-2 [...] new 90238e1d54 178: onsuccess: #1798: 1: Success after gdb-12-branchpoint-2 [...] new be5cb4f05b 179: onsuccess: #1799: 1: Success after basepoints/gcc-13-31 [...] new f615af4195 180: onsuccess: #1800: 1: Success after binutils/gcc: 2 commits new 0a0229e867 181: onsuccess: #1801: 1: Success after basepoints/gcc-13-31 [...] new 4a0398c13f 182: onsuccess: #1802: 1: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e80dfb8e8d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (4a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1660 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 50556 -> 51448 bytes 04-build_abe-gcc/console.log.xz | Bin 232296 -> 235800 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3808 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2704 -> 2648 bytes 07-check_regression/console.log.xz | Bin 5148 -> 4940 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 | 52 +- 07-check_regression/results.regressions | 27 - 08-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 4 +- git/gcc_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 2769448 -> 2804592 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2351400 -> 2358124 bytes sumfiles/gcc.sum | 4570 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 911060 -> 921064 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2168 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204684 -> 204484 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 470240 -> 466492 bytes sumfiles/libstdc++.sum | 12 +- 35 files changed, 2513 insertions(+), 2566 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, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allmodconfig updated (3ebd22b840 -> 5675669b2f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from 3ebd22b840 21: onsuccess: #463: all: Success after binutils/llvm/qemu: [...] new 5675669b2f 22: onsuccess: #466: all: Success after binutils/qemu: 83 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 1716 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30232 -> 30828 bytes 04-build_kernel_llvm/console.log.xz | Bin 65684 -> 63340 bytes 05-build_abe-qemu/console.log.xz | Bin 31976 -> 32444 bytes 06-build_linux/console.log.xz | Bin 3268 -> 3252 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3784 -> 3248 bytes dashboard/dashboard-generate.sh | 12 ++++++++- dashboard/dashboard-push.sh | 5 ++++ .../results-functional.json | 0 git/binutils_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 5 ++++ mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 ++++++++++----------- 18 files changed, 39 insertions(+), 20 deletions(-) copy dashboard/{squad => squad-vs-first}/results-functional.json (100%) -- 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 (aa9587ab4b -> 3f7827b818)

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 aa9587ab4b 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 3f7827b818 73: onsuccess: #476: 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 2760 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 52160 -> 51812 bytes 05-build_abe-gcc/console.log.xz | Bin 236580 -> 234064 bytes 07-build_abe-linux/console.log.xz | Bin 9264 -> 8856 bytes 08-build_abe-glibc/console.log.xz | Bin 234332 -> 233152 bytes 09-build_abe-gdb/console.log.xz | Bin 49140 -> 49272 bytes 10-check_regression/console.log.xz | Bin 4332 -> 4140 bytes 11-update_baseline/console.log | 9 ----- dashboard/dashboard-generate.sh | 12 ++++++- dashboard/dashboard-push.sh | 5 +++ .../score/results-functional.json | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 5 +++ mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++----------- 22 files changed, 48 insertions(+), 37 deletions(-) copy dashboard/{squad => squad-vs-first}/score/results-functional.json (100%) -- 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_O3 updated (974efc1f99 -> ae9b7c4937)

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_O3 in repository toolchain/ci/base-artifacts. from 974efc1f99 18: onsuccess: #127: 2: Success after binutils/gcc: 7 commits new ae9b7c4937 19: onsuccess: #128: 2: Success after binutils/gcc: 7 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1668 -> 1652 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 51696 -> 52576 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 460484 -> 461416 bytes 06-check_regression/console.log.xz | Bin 2832 -> 2804 bytes dashboard/dashboard-generate.sh | 12 +++++++++++- dashboard/dashboard-push.sh | 5 +++++ .../score/results-functional.json | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- jenkins/dashboard-push.sh | 5 +++++ manifest.sh | 20 ++++++++++---------- 12 files changed, 33 insertions(+), 13 deletions(-) copy dashboard/{squad => squad-vs-first}/score/results-functional.json (100%) -- 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_bootstrap/master-aarch64-check_bootstrap_lto updated (4cfe26daf5 -> 5ea3c41d16)

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_bootstrap/master-aarch64-check_bootstrap_lto in repository toolchain/ci/base-artifacts. from 4cfe26daf5 58: onsuccess: #601: 1: Success after binutils: 5 commits new 5ea3c41d16 59: onsuccess: #604: 1: Success after gdb-12-branchpoint-214 [...] 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 1648 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2712 bytes 03-build_abe-binutils/console.log.xz | Bin 37448 -> 37632 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 275324 -> 276284 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3820 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2572 -> 2596 bytes 07-check_regression/console.log.xz | Bin 4492 -> 4332 bytes 07-check_regression/mail-body.txt | 26 - 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 08-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 12 +- dashboard/dashboard-push.sh | 5 + .../score/results-functional.json | 0 git/binutils_rev | 2 +- jenkins/dashboard-push.sh | 5 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- sumfiles/g++.log.xz | Bin 3634108 -> 3622176 bytes sumfiles/g++.sum | 142 +- sumfiles/gcc.log.xz | Bin 3213976 -> 3213380 bytes sumfiles/gcc.sum | 4408 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1083588 -> 1089024 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2356 -> 2344 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213756 -> 213636 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2732 -> 2736 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 461600 -> 470584 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2359 insertions(+), 2391 deletions(-) copy dashboard/{squad => squad-vs-first}/score/results-functional.json (100%) -- 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 (202d8774df -> a7a6fc434d)

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 202d8774df 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards e405efcf88 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards c38af139f9 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 5f95b7308d 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards b722228722 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 931deb5cff 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards f83af64af2 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 3543f72128 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards f873501e2d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 5aa70db960 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 8282eb35ac 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 4ac278687f 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards b180d8567d 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 4a7e5e6f1b 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards fd87d7001b 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 1394c43443 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 785fa9f16b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 73e56aa0aa 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 69e7a39532 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards baded9400d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 71e2980184 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards e0186f38ec 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 87a311925b 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards ae1cfcabd0 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 6ea8bedc6b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards d4eb458162 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 5544098cf2 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 3eea3b175c 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards f1c36e269a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 4ca2fef580 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 1555df62c5 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards f53f7276a8 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards ed2f59dfa6 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 54dc3b769e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 6d7118e39f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 9003597a4d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 344f852c0e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 4a685d5495 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards c984aed774 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards e37a7c3ffa 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 43264a1f7b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 8313847b31 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 67594c5078 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 9e576be037 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards c548940ec2 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 512c1e87b4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards c1aaa1a202 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards a6c892fc5b 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 50d65417af 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 0e6729a30b 128: onsuccess: #2163: 1: Success after linux: 23 commits discards fb4988aeff 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 03de3d50e0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards fe033e7896 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards d13464a4de 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d3908de23f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards a6cbd98d74 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards c9aaa3a76d 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 03baa9368a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards fd2b14c14f 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 3b5d248844 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 1cb3821203 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 61ae6c428b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards a486eee2ef 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards a5671ab8c4 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards fc519d413c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8cfb8f8a52 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 072847d0d0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards a5585a0179 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 7aa2c22165 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 4fd60c3cc4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 6b1572d10d 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 0f16dd621f 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards b6baa39fb6 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards ca859bc6c5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 2216852a9b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 848d3e334a 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards bb728033bf 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards f3c9c31e7c 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards bbe627138f 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards d04bea00bb 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards c2186e7398 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 1e25e8c42f 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 1a45308ed5 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 594c19f8f5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards fa73eae87a 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 136de1e7dc 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 746689909e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards c0043cafcc 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards caa037ed8d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 46fd6a46c2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards d095f3d3d0 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 0ca0f15e88 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards f65b4ad853 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards a99138df2e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards ce582a9267 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 282d176f7c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d390159fd2 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 0a1f988dee 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b50991bf43 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 478799528a 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 81c8430e17 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 6d0066368f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new bbf8897a79 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 59b7536566 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 603eb9eb43 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a5c98ea97c 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 0b67b906bc 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3cbe04a504 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new f63df8cdc1 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d22a3510ea 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 433dadb65a 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 971d404bee 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 702c731fbf 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 1b773b1db5 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 8f0c56c055 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 4f0e328fcc 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 44853dc61b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6b70bc4fd4 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new ea7233ebc0 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 08b0dee645 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 80d8f66a1a 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 287bde0d09 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 56bcdd4243 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 5d52fa7197 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 67253a8746 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new af9b2281e5 101: onsuccess: #2130: 1: Success after binutils: 81 commits new f8582b6f0b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new a7eef1b58d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new eb9f7ebdc3 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 95b50c96ee 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 52ddb911f3 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 56657a7720 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 24b020c463 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 649be33574 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new a7ea7e4481 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 0f8337a53d 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 604aed54a0 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 4f104a97cd 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 88fb918d72 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 01a6741cc2 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new fb782813df 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new bc664c6ce7 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new e100de033e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new e253333fb1 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 7343097423 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 2124d052c3 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e46da7073e 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 3433f3a1d6 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new c42a2565cd 124: onsuccess: #2159: 1: Success after linux: 23 commits new 7b45685545 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 747ef3f036 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 692fd15d4d 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 29dc90400f 128: onsuccess: #2163: 1: Success after linux: 23 commits new 35c2d14d96 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 68159f4cac 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new a60d736051 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new db55c27560 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 119e3c98cd 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new a096fc44d1 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new b955be125c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new d15204685c 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new ec28bb362e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 02f86bd504 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new c08d260eeb 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 3bc9c1ca39 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 154b242f5a 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 24ff2f28ea 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 8c8ce9a89e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 4b13c6ee3f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 6965a11cbb 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 5fab152da5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 545099ab2c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new d9f997227f 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 4793452a63 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 89ced19d3a 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 98e19edc16 151: onsuccess: #2186: 1: Success after gcc: 2 commits new c3341dffc3 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 93afa7320b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 6dc89eb77a 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new d447b100d7 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 0355975c36 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 3c52daee51 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 0165f7b116 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new b994eb506b 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 9d871cd282 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 712ca4a7e8 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 9de70dc6d3 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 4e4f34745e 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new abcc38b52b 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new b6b0d3ffbe 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 4e8022c949 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 1a71222bd1 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new b9018c5676 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new aeffc4a9a8 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new f335abbcdf 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new d2626d9ed5 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new ccaff6cee2 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new cc7a5afaac 173: onsuccess: #2208: 1: Success after gcc: 10 commits new bf9e7ee6b6 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new a8975b60e9 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e686b1818c 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 28b6957fe4 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new a7a6fc434d 178: onsuccess: #2217: 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 (202d8774df) \ 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 1716 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30876 -> 30684 bytes 04-build_abe-stage1/console.log.xz | Bin 73548 -> 72916 bytes 06-build_abe-linux/console.log.xz | Bin 9168 -> 8756 bytes 07-build_abe-glibc/console.log.xz | Bin 240512 -> 240472 bytes 08-build_abe-stage2/console.log.xz | Bin 204252 -> 203252 bytes 09-build_abe-gdb/console.log.xz | Bin 38004 -> 37212 bytes 10-build_abe-qemu/console.log.xz | Bin 32008 -> 32464 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3932 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3680 -> 2840 bytes 13-check_regression/console.log.xz | Bin 5692 -> 14308 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 194 +- 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 212 +- 13-check_regression/results.compare2 | 1662 +++++- 13-check_regression/results.regressions | 102 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 12 +- dashboard/dashboard-push.sh | 5 + .../score/results-functional.json | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 5 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 102 +- sumfiles/g++.log.xz | Bin 3413608 -> 3415380 bytes sumfiles/g++.sum | 62 +- sumfiles/gcc.log.xz | Bin 3031992 -> 3014812 bytes sumfiles/gcc.sum | 5810 +++++++++----------- sumfiles/gfortran.log.xz | Bin 1035388 -> 1029312 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202480 -> 202328 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428752 -> 421428 bytes sumfiles/libstdc++.sum | 8 +- 47 files changed, 5134 insertions(+), 3530 deletions(-) copy dashboard/{squad => squad-vs-first}/score/results-functional.json (100%) -- 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