Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O1 updated (8e7057de77 -> 9e9b17c31d)

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_O1 in repository toolchain/ci/base-artifacts. from 8e7057de77 56: onsuccess: #448: 2: Success after binutils/gcc: 33 commits new 9e9b17c31d 57: onsuccess: #449: 2: Success after binutils/gcc: 50 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 1688 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 51708 -> 50980 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 470032 -> 469040 bytes 06-check_regression/console.log.xz | Bin 3068 -> 3068 bytes 07-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allmodconfig updated (96498e9044 -> c5706a2c9c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 96498e9044 17: onsuccess: #261: 22763: Success after binutils/llvm/linu [...] new c5706a2c9c 18: onsuccess: #262: 22763: Success after binutils/llvm/linu [...] 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 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29728 -> 29660 bytes 04-build_kernel_llvm/console.log.xz | Bin 64964 -> 62756 bytes 05-build_abe-qemu/console.log.xz | Bin 31388 -> 31472 bytes 06-build_linux/console.log.xz | Bin 4576 -> 4720 bytes 08-check_regression/console.log.xz | Bin 4344 -> 4256 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (121dd2c060 -> 4a333928cb)

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-aarch64 in repository toolchain/ci/base-artifacts. from 121dd2c060 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 4a333928cb 53: onsuccess: #827: 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 1680 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 37772 -> 39540 bytes 04-build_abe-gcc/console.log.xz | Bin 212476 -> 214712 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9400 -> 8480 bytes 07-build_abe-glibc/console.log.xz | Bin 239296 -> 239492 bytes 08-build_abe-gdb/console.log.xz | Bin 37692 -> 38020 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2232 -> 2568 bytes 11-check_regression/console.log.xz | Bin 13184 -> 10936 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 32 +- 11-check_regression/mail-body.txt | 158 +- 11-check_regression/results.compare | 69 +- 11-check_regression/results.compare2 | 4555 +++++++++--------------- 11-check_regression/results.regressions | 69 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 160 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 69 +- sumfiles/gdb.log.xz | Bin 1903096 -> 1872964 bytes sumfiles/gdb.sum | 5862 ++++++++++++------------------- 30 files changed, 4067 insertions(+), 6961 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (2d2dda345c -> 3a169d8be8)

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 2d2dda345c 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits discards 7abd34614d 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits discards b56f835a55 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits discards 9f7eaebb06 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits discards e6d4e23387 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards 1fc89b1cf6 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards 2a3fd7a9db 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards 14cdd1fb78 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards 9a817d58a5 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards 89d9278dfd 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards add1236f33 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards 692a218596 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards 82d30abb8c 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards 25a7184b5e 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards ea0cdbf669 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 8555da4261 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards bcfa86308b 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards 65141c8fba 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards c78c11f45b 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards 9775c24f55 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 37f0c50cc6 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards 26df9e81ec 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 214d7618fe 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards cbf6468a47 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards a3da4a0cd7 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards 00a1f87e58 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 7c98d2f948 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 88d1ca9717 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards d764e4cc7d 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards e86d971784 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 449c1a60f7 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards 7d789c4344 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 912bb29bcd 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards cf6e7b265d 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards f7c6393f14 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards a5911fc861 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards d045550730 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 7803f566b7 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards dcde094569 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards a5c8c303e2 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 64122bcbaa 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards c128e336f7 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 3969b5189f 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 92488ccc65 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 2b81c746df 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 25a2794a99 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards b5a22d0fe8 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 00894bdc20 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 518b624304 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 8de52fb287 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 69febd32d7 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 59d8e64356 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 6f7f7ace89 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards ba4fe0bf1f 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards e0a03ced8e 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 9f678ac28e 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards e27621a578 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 69bfe76fb0 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards f6c59179b2 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 9655e006c3 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards e34524d3ea 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards c68099d727 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 0beb0c9b8c 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 6ceb0b1783 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards f19b297a93 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards a5b19de115 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 082c69ca05 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards f2ff4c711c 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 8afd0945b6 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards d7861acbbf 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 7176f0ca56 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 95ea75f42a 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards e35f0f20ce 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards ea5f3c787f 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards bc77222acc 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards cf94245e29 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards ab743b1632 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 1bdba10588 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards f38d5ece06 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 238f197e5e 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards b55aa7f2c3 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 22a11f3a7d 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards c950aa1b21 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 158420e2fc 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards ac7cfa4029 87: onsuccess: 1: Success after gcc: 6 commits discards 0533d4cd61 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 9dd5b06f21 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 46ac1a246e 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 584a959bd6 83: onsuccess: 1: Success after gcc: 14 commits discards b80d420269 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 8dd126d3fb 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards c0d5e7d296 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 428b06c559 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 3b08101e97 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards e48e1920b2 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 2f28efd4ef 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 791208a31f 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 7f3139dd7c 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 57d5c828b6 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards e389572058 72: onsuccess: 1: Successful build after baseline build: no [...] discards 6fb6845c3f 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 43a6ddca94 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 439409e22d 72: onsuccess: 1: Successful build after baseline build: no [...] new 6afba848ab 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 15546f328f 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new ed1d6f97d6 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 916e19e9a4 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 771e3a3e2d 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new a1586835d8 78: onsuccess: 1: Success after binutils/gcc: 17 commits new d1611a012f 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 57fdbc96fd 80: onsuccess: 1: Success after binutils/gcc: 8 commits new ee0ef5796d 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 8d644eed66 82: onsuccess: 1: Success after binutils/gcc: 9 commits new faa9e2d97e 83: onsuccess: 1: Success after gcc: 14 commits new f5af0ac95d 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 2dd95a4b89 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 42265181b0 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 14d2d4078d 87: onsuccess: 1: Success after gcc: 6 commits new 8dd5fa3024 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 985f72c262 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 6fbedae9f2 90: onsuccess: #1645: 1: Success after gcc: 2 commits new 78ae39aa36 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 613de955cf 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new dafb52b117 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new d8c87e96f2 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new e927335710 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 4f98c8da99 96: onsuccess: #1654: 1: Success after gcc: 5 commits new b419a9bd27 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 9d2a2477ae 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 3c6eaa27cc 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 8056d92dd8 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new a6ee949595 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new e22075e6fd 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new feb489bd1b 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 1a3fd4ed3b 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 4e3b401028 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 4ac538bba6 106: onsuccess: #1702: 1: Success after gcc: 4 commits new a597ccfa8b 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 47c6c3af0f 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 6aca71bd7e 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 4af99d9ebb 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new d6b606d4af 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new ba3ff648ff 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new bac40dd05c 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 19f866e31e 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 6ae80e785b 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new ae89cadaa2 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 9eaacd91b4 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new a260365944 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 65ddae7db4 119: onsuccess: #1715: 1: Success after binutils: 4 commits new d8d26e7864 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new ab79452dfb 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 241be53ff2 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 44f080b800 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 00979f291b 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 1684fa1c04 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new dac744a794 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new a4bbef8ffc 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 5e96ef0394 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new f904a20613 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new d1c1d8c120 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 5a7eae638e 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 6f97000d77 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 06c4cca805 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 0c83118522 134: onsuccess: #1736: 1: Success after binutils: 3 commits new efa28e1d3a 135: onsuccess: #1739: 1: Success after binutils: 4 commits new d15e4c72dc 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new c5f7b775b1 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 29c4e2d366 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 693be61003 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 794ae942cf 140: onsuccess: #1756: 1: Success after binutils: 3 commits new c2890144c1 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new 841a5aaa79 142: onsuccess: #1761: 1: Success after gcc: 83 commits new ca004de0f4 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new d80b399435 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new b29187c22a 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new 879b07530c 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 7b55a0b6e7 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new 369abb2b83 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 21ca3a882b 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 2bd875cff8 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 26df9ee625 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 809d0d1ce0 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 2fa3c99617 153: onsuccess: #1773: 1: Success after gcc: 4 commits new 90ca6db140 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new 9c862d8917 155: onsuccess: #1775: 1: Success after binutils: 2 commits new a7f8d13834 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new 7c92a5b03f 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new 545c13c270 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new 8aea1a1b2b 159: onsuccess: #1779: 1: Success after gcc: 2 commits new f1d6c4834d 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new b5ee9d6f83 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new 4adf678b82 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new 2d46de7cd6 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new b21305f723 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new 5aa295823c 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new 2680e3bec6 166: onsuccess: #1786: 1: Success after gcc: 10 commits new 4a3357e327 167: onsuccess: #1787: 1: Success after gcc: 8 commits new b005b654ed 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits new 39161ae68e 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits new b114bf2460 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits new 3bcca2e241 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits new 3a169d8be8 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 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 (2d2dda345c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (3a [...] 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 1668 -> 1652 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 51396 -> 50792 bytes 04-build_abe-gcc/console.log.xz | Bin 234120 -> 232676 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3844 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2548 -> 2584 bytes 07-check_regression/console.log.xz | Bin 5016 -> 4484 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 47 +- 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2810652 -> 2774132 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2357732 -> 2390548 bytes sumfiles/gcc.sum | 4834 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 909460 -> 913032 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204876 -> 204520 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2536 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468208 -> 468312 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2582 insertions(+), 2615 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (9cc049ddc2 -> 90ff28182c)

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 9cc049ddc2 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards bc660d614f 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 0b2f795704 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards da43183c45 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 3e12cc140d 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards a144d890b1 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards ef1b6c4a09 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 0aedc64490 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 2a2c291883 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards b92616319b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 12f6f57c1b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 84b5ea73c9 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 3cdff9ecd4 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards dc45ac7bfa 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5b55a6ed7d 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 12dd0c383f 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 46864dbd32 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards dc02457201 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards b966d8d40c 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 0344969ff5 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 550918f1cd 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 36d0a79838 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 0e5495707b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 079eeaa5ce 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards b62853d59c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 43f0b9b576 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 2af70daf59 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 669a411ae7 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 4f29b97e69 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 5b83db90d7 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 3d92732235 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 75517dbb15 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 4c341c1b28 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 46b713fbe0 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 4008dc44c9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards ca2f8474e9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards e56d500351 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 827a8e9af9 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 4e1d510c9b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 96427b939a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards ff3bb5ba7d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 1049d360ea 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards a576061e22 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards a12b970c40 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 0e15d94ca6 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 4ab13254c5 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 4feba58d50 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 1d00f27910 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 3ac48cf542 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 5842eebac2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 7d399113f0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 956b7cd1e0 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards da0e62e672 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 315e673f0f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 683dc598d0 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 42aab777de 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 7b82ab00c1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 8fef47ca9f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 74b1301e96 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards e332748def 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards dffecb1d22 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards fe41397130 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards e9a164f6ba 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards cc4d5a1838 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 507f7b9151 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards c014068a1e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 0e5997b3cf 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards d0a0b92bad 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards b0b63fbb0b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 99015e63fd 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards d62d670f98 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 1c3762e792 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 5492f156ae 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards f690b5452a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1b259620b5 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 4f64ebebbe 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 3bdefa4dd9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 3553982143 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards a004202215 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 32dc207869 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 67c2f21834 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards d1960f87b2 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 1269991640 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards a6cb5bbca9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 95e31baa5a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards ee6c374e81 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 10b7e42fa3 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 1661cc2150 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 764cd2bf89 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards bc67c34f64 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards a1fe1256ad 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 4da74eda18 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8ce6b3a502 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c2a5319622 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards feccadf3ef 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 13c26c26cf 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 51ae1faee6 75: onsuccess: 1: Successful build after linux: 44 commits discards fc768470cc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ad1cde4aaf 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a03c098fec 72: onsuccess: 1: Successful build after linux: 12 commits discards 38c6028b1d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 2fadb9bee7 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new c335784d66 72: onsuccess: 1: Successful build after linux: 12 commits new 2fbd69b2a6 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3f3f728471 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 825a053775 75: onsuccess: 1: Successful build after linux: 44 commits new d6006ad73f 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e036e2089 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 0101894773 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 59c423e429 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 10750cc932 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 525adb350f 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 272a8f3207 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 28243755f9 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 98801c9dff 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 5ef426bbdb 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new f41a959a0d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 8ef6ed65e5 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new c650e47634 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new f01f9df4a9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 60196e991a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new c589f779fc 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 103f6f737c 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a9227657d0 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new f81726939b 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new b9e2e7bef9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 35387944bf 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new cfa17dbe98 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new ac25e9d8fd 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 7d99696c4b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 65d809ef33 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new ec312fdcf2 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 17a593a1fd 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new c65dc656f9 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 69bafb7891 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 59f7b4bd79 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 0aa25e9127 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new d499270000 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 9ae80015ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 5fcda510bb 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new a15e81b6e4 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 5a0bd61c84 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 73fe7ab3fa 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 1c7291f439 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 9cb434d79e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new c77c641641 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 38e8f46fc6 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new aa81e4dad1 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 820a3d9e08 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new d7ca793d10 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 2d3e0c97fc 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new d43919a076 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e69a2e0da4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 82c45aa40f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 5103a3e987 124: onsuccess: #2159: 1: Success after linux: 23 commits new eb357676a9 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 1df0b2fb6f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new d11f48cede 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 9f436cfd20 128: onsuccess: #2163: 1: Success after linux: 23 commits new 19c99490ea 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 91860e4c31 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 4b65b9c787 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 73eef4066a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 34bed7f669 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new bb33f82c94 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 71782058c0 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 0900dfd3fb 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 7461a8884b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new d41f45ef03 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 653e4aa71b 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new fe95e9fd29 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 99a3ffe21e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new b01a867064 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 2d4705111c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 96df226891 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new aac8cd95c4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 0c43773f53 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 68771b79b2 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new adfc360083 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new e87f0c31ed 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new ba73217d1f 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 1b0cfa2e10 151: onsuccess: #2186: 1: Success after gcc: 2 commits new c402964017 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 0ce799a743 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 7e21a0f4d6 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 4ea84b2061 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new a3459fb57c 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 8f4e4eb41b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 09c43b0bd2 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 276e0420f9 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 58d8db1c39 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 983ca60edf 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 44d50f2139 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new c1f20cc8eb 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new ab430c1f9f 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new ad93c4ad88 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 5803a1f853 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 882bc23060 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 606c83301c 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 5d9ea963aa 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 2caaab12a5 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 2078a43226 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 90ff28182c 172: onsuccess: #2207: 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 (9cc049ddc2) \ 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 1744 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30508 -> 30740 bytes 04-build_abe-stage1/console.log.xz | Bin 72864 -> 72672 bytes 06-build_abe-linux/console.log.xz | Bin 9024 -> 8544 bytes 07-build_abe-glibc/console.log.xz | Bin 239540 -> 238996 bytes 08-build_abe-stage2/console.log.xz | Bin 203100 -> 202920 bytes 09-build_abe-gdb/console.log.xz | Bin 37352 -> 37920 bytes 10-build_abe-qemu/console.log.xz | Bin 31716 -> 31968 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2900 -> 2808 bytes 13-check_regression/console.log.xz | Bin 26296 -> 16704 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 45 +- 13-check_regression/mail-body.txt | 215 +- 13-check_regression/results.compare | 93 +- 13-check_regression/results.compare2 | 5608 +++++++++---------------------- 13-check_regression/results.regressions | 93 +- 14-update_baseline/console.log | 78 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 217 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 93 +- sumfiles/g++.log.xz | Bin 3405488 -> 3411232 bytes sumfiles/g++.sum | 2996 ++++++++--------- sumfiles/gcc.log.xz | Bin 3041640 -> 3037936 bytes sumfiles/gcc.sum | 4465 ++++++++++++------------ sumfiles/gfortran.log.xz | Bin 1032700 -> 1029596 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202256 -> 202428 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422684 -> 428700 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 5555 insertions(+), 8426 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/release-arm updated (7ea896ce3e -> 665e0a9122)

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/release-arm in repository toolchain/ci/base-artifacts. from 7ea896ce3e 19: onsuccess: #127: 6: Success after binutils/gcc/glibc/gdb [...] new 665e0a9122 20: onsuccess: #128: 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 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 51444 -> 51884 bytes 05-build_abe-gcc/console.log.xz | Bin 230852 -> 229292 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8840 -> 8800 bytes 08-build_abe-glibc/console.log.xz | Bin 234876 -> 234652 bytes 09-build_abe-gdb/console.log.xz | Bin 46544 -> 47600 bytes 10-check_regression/console.log.xz | Bin 3956 -> 4072 bytes 11-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++------------------ 20 files changed, 37 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-defconfig updated (dba0364a47 -> fd38c70242)

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-next-defconfig in repository toolchain/ci/base-artifacts. from dba0364a47 12: onsuccess: #477: boot: Success after binutils/llvm/linux [...] new fd38c70242 13: onsuccess: #478: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30196 -> 30820 bytes 04-build_kernel_llvm/console.log.xz | Bin 66092 -> 64932 bytes 05-build_abe-qemu/console.log.xz | Bin 31952 -> 32012 bytes 06-build_linux/console.log.xz | Bin 3108 -> 3120 bytes 07-boot_linux/console.log.xz | Bin 6144 -> 6132 bytes 08-check_regression/console.log.xz | Bin 4436 -> 4428 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/release-arm updated (2b105211cd -> 6b60a990f0)

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/release-arm in repository toolchain/ci/base-artifacts. from 2b105211cd 19: onsuccess: #182: 1: Success after binutils/gcc: 9 commits new 6b60a990f0 20: onsuccess: #183: 1: 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 1652 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 50764 -> 50920 bytes 04-build_abe-gcc/console.log.xz | Bin 229168 -> 229168 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3804 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2824 -> 2336 bytes 07-check_regression/console.log.xz | Bin 4916 -> 4548 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 43 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 2773192 -> 2775848 bytes sumfiles/g++.sum | 114 +- sumfiles/gcc.log.xz | Bin 2353440 -> 2385304 bytes sumfiles/gcc.sum | 4602 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 898108 -> 908208 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2160 -> 2168 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 199608 -> 199756 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 460480 -> 463956 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2428 insertions(+), 2459 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-defconfig updated (013d585ddd -> 927b5671c4)

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-next-defconfig in repository toolchain/ci/base-artifacts. from 013d585ddd 11: onsuccess: #384: boot: Success after binutils/gcc/linux/ [...] new 927b5671c4 12: onsuccess: #385: 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 1712 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29708 -> 29828 bytes 04-build_abe-stage1/console.log.xz | Bin 86076 -> 87060 bytes 05-build_abe-qemu/console.log.xz | Bin 31520 -> 31104 bytes 06-build_linux/console.log.xz | Bin 4080 -> 3060 bytes 07-boot_linux/console.log.xz | Bin 5644 -> 5648 bytes 08-check_regression/console.log.xz | Bin 4164 -> 4100 bytes 08-check_regression/mail-body.txt | 4 ++-- 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 20 files changed, 38 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_tx1/llvm-release-aarch64-spec2k6-O3_LTO updated (82b304bf2b -> cfda138968)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_llvm_tx1/llvm-release-aarch64-spec2k6-O3_LTO in repository toolchain/ci/base-artifacts. from 82b304bf2b 7: onsuccess: #187: 1: [TCWG CI] No change after binutils/gc [...] new cfda138968 8: onsuccess: #189: 1: [TCWG CI] 401.bzip2 built and run OK [...] 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 1784 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30288 -> 30208 bytes 04-build_abe-stage1/console.log.xz | Bin 68396 -> 68528 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8648 bytes 07-build_abe-glibc/console.log.xz | Bin 235856 -> 236232 bytes 08-build_abe-stage2/console.log.xz | Bin 173132 -> 172520 bytes 09-build_llvm-true-false-/console.log.xz | Bin 0 -> 62916 bytes 09-build_llvm-true/console.log.xz | Bin 62660 -> 0 bytes 10-benchmark/benchmark-build.log | 122 +- 10-benchmark/benchmark.log | 120 +- 10-benchmark/console.log.xz | Bin 4040 -> 4032 bytes 11-check_regression/console.log.xz | Bin 7400 -> 7712 bytes 11-check_regression/csv-results-0/perf.csv | 89 +- 11-check_regression/csv-results-0/results.csv | 14699 +-- 11-check_regression/csv-results-0/size.csv | 119726 ++++++++--------- 11-check_regression/csv-results-0/vect.csv | 9720 +- 11-check_regression/csv-results-1/perf.csv | 85 +- 11-check_regression/csv-results-1/results.csv | 6523 +- 11-check_regression/csv-results-1/size.csv | 121065 +++++++++--------- 11-check_regression/csv-results-1/vect.csv | 21147 +-- 11-check_regression/exe.improvement | 1 + 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 3 + 11-check_regression/mail-body.txt | 3 + 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-brief.csv | 40 +- 11-check_regression/results-compare.csv | 4 +- 11-check_regression/results-full.csv | 100 +- 11-check_regression/results-internal.csv | 49 +- 11-check_regression/results.csv | 49 +- 11-check_regression/results.log | 783 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 18 +- dashboard/squad/400.perlbench/results-metrics.json | 2 +- dashboard/squad/401.bzip2/results-functional.json | 4 +- dashboard/squad/401.bzip2/results-metadata.json | 18 +- dashboard/squad/401.bzip2/results-metrics.json | 3 + dashboard/squad/403.gcc/results-metadata.json | 18 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 18 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 18 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 18 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 18 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 18 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 18 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 18 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 18 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 18 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 18 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 18 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 18 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 18 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 18 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/Mean/results-functional.json | 4 - dashboard/squad/Mean/results-metadata.json | 13 - dashboard/squad/Mean/results-metrics.json | 5 - dashboard/squad/dashboard-push-squad.sh | 77 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 62 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 2 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 400360 -> 400352 bytes save-temps/401.bzip2.tar.xz | Bin 0 -> 44492 bytes save-temps/403.gcc.tar.xz | Bin 1206360 -> 1209700 bytes save-temps/429.mcf.tar.xz | Bin 22816 -> 22812 bytes save-temps/444.namd.tar.xz | Bin 47004 -> 46684 bytes save-temps/445.gobmk.tar.xz | Bin 615692 -> 616840 bytes save-temps/447.dealII.tar.xz | Bin 936536 -> 913896 bytes save-temps/450.soplex.tar.xz | Bin 203840 -> 205292 bytes save-temps/453.povray.tar.xz | Bin 463392 -> 477356 bytes save-temps/456.hmmer.tar.xz | Bin 124684 -> 125264 bytes save-temps/458.sjeng.tar.xz | Bin 52560 -> 52536 bytes save-temps/462.libquantum.tar.xz | Bin 24148 -> 24236 bytes save-temps/470.lbm.tar.xz | Bin 16036 -> 16044 bytes save-temps/471.omnetpp.tar.xz | Bin 323960 -> 327900 bytes save-temps/473.astar.tar.xz | Bin 43820 -> 43852 bytes save-temps/482.sphinx3.tar.xz | Bin 95664 -> 95828 bytes save-temps/483.xalancbmk.tar.xz | Bin 3320984 -> 3193564 bytes 100 files changed, 142847 insertions(+), 152113 deletions(-) create mode 100644 09-build_llvm-true-false-/console.log.xz delete mode 100644 09-build_llvm-true/console.log.xz create mode 100644 11-check_regression/exe.improvement delete mode 100644 dashboard/squad/Mean/results-functional.json delete mode 100644 dashboard/squad/Mean/results-metadata.json delete mode 100644 dashboard/squad/Mean/results-metrics.json create mode 100644 save-temps/401.bzip2.tar.xz -- 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