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-arm-next-allnoconfig updated (99a9869e51 -> 6a6cc3b67e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from 99a9869e51 12: onsuccess: #401: all: Success after binutils/gcc/linux/q [...] new 6a6cc3b67e 13: onsuccess: #402: all: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 29888 -> 30112 bytes 04-build_abe-stage1/console.log.xz | Bin 90840 -> 91060 bytes 05-build_abe-qemu/console.log.xz | Bin 31468 -> 31472 bytes 06-build_linux/console.log.xz | Bin 4156 -> 3644 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4424 -> 4376 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch gdb-12-branch updated (ce2cb0f4db9 -> 01c9cd44d7e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-12-branch in repository binutils-gdb. from ce2cb0f4db9 Automatic date update in version.in new 01c9cd44d7e Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (0bce60ac7f1 -> fea044ba7b5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 0bce60ac7f1 Fix indentation in riscv-tdep.c new fea044ba7b5 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch binutils-2_39-branch updated (6cf955dbaa1 -> d99744ce4f3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_39-branch in repository binutils-gdb. from 6cf955dbaa1 Automatic date update in version.in new d99744ce4f3 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

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

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 bf043008c2 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits discards cdf395468b 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits discards a38b0161b0 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits discards 60224c26ce 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards b43722c62a 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards 695cd0fbd2 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards 421c9c60ad 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards bdac01a17f 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards 9ecaa5fea6 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards e27767b613 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards 2cd28e1e92 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards 8c06a82ecf 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards 15d4a9a20a 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards 4a75f6a6ed 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 5f60cf0cad 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards e04e733d76 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards ddc1f5d8b2 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 29c190423d 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards bff54ce1cd 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 174534f843 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards 77dc4dfb80 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 6f1bc94199 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards f4d3f20ac0 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 1788fe2fc5 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards cc9dd8dc6c 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards aa8a6becc4 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 3f091aa729 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 62b414451d 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards e572220c8b 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 80151a4efd 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards e1888298b7 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 0486b7a556 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards a619f96dcd 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards d67357b970 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 1c02f9f91f 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 7b2b335397 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 826f7e7428 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 5952e5b80f 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 870bf5f7e6 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 6f77175912 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 09248e729f 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 6b4ea31af9 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 4a97a93129 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 8ec890f654 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 7cee80c8eb 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards c285e05895 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 61dfab7531 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 352a573f36 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 06ca247738 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 2872febd57 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 5e0b4543fa 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 5784098ea7 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards b7420b7110 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 99fe3d6d58 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 2efe51d099 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 499228ba4f 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 648e7be93a 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 01933cf1c6 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 9d373b9730 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 807c4a34bf 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 9e387beed1 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards d543f94d6a 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards a4fc29c27a 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards aefb81a685 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards b4658856c2 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 51a2e2866b 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards d3665cc7b3 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 7a9a17f448 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 29d1eb0689 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards c668b60f89 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 9aecf7dee4 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 3d2ffd6ee6 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 237d1c4b2d 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards baa82bc208 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards d167ce1b79 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 7393873354 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 46eb4b0507 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 477def96aa 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards bf7d882330 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 0e800cc572 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards c334097859 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards d38cca5af2 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 85649b317f 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 36a58e5027 87: onsuccess: 1: Success after gcc: 6 commits discards f008aeca54 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards e23a351b0d 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 9ff190b983 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 03cac1d137 83: onsuccess: 1: Success after gcc: 14 commits discards 970565e355 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 220822b30e 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards c63dc2d615 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 3a35e02148 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards e0a80578ee 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 08ece4a7af 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards f9f7e01725 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards b06331061c 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 4fc3d7e186 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 69399dde4d 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards d6f98f71cb 72: onsuccess: 1: Successful build after baseline build: no [...] discards a03c58c9c5 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards d182a388d8 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new a533366c53 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 6fb6845c3f 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new e389572058 72: onsuccess: 1: Successful build after baseline build: no [...] new 57d5c828b6 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 7f3139dd7c 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 791208a31f 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 2f28efd4ef 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new e48e1920b2 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 3b08101e97 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 428b06c559 79: onsuccess: 1: Success after binutils/gcc: 23 commits new c0d5e7d296 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 8dd126d3fb 81: onsuccess: 1: Success after binutils/gcc: 8 commits new b80d420269 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 584a959bd6 83: onsuccess: 1: Success after gcc: 14 commits new 46ac1a246e 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 9dd5b06f21 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 0533d4cd61 86: onsuccess: 1: Success after binutils/gcc: 8 commits new ac7cfa4029 87: onsuccess: 1: Success after gcc: 6 commits new 158420e2fc 88: onsuccess: 1: Success after binutils/gcc: 2 commits new c950aa1b21 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 22a11f3a7d 90: onsuccess: #1645: 1: Success after gcc: 2 commits new b55aa7f2c3 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 238f197e5e 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new f38d5ece06 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 1bdba10588 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new ab743b1632 95: onsuccess: #1653: 1: Success after gcc: 13 commits new cf94245e29 96: onsuccess: #1654: 1: Success after gcc: 5 commits new bc77222acc 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new ea5f3c787f 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new e35f0f20ce 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 95ea75f42a 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 7176f0ca56 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new d7861acbbf 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 8afd0945b6 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new f2ff4c711c 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 082c69ca05 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new a5b19de115 106: onsuccess: #1702: 1: Success after gcc: 4 commits new f19b297a93 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 6ceb0b1783 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 0beb0c9b8c 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new c68099d727 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new e34524d3ea 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 9655e006c3 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new f6c59179b2 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 69bfe76fb0 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new e27621a578 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 9f678ac28e 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new e0a03ced8e 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new ba4fe0bf1f 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 6f7f7ace89 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 59d8e64356 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 69febd32d7 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 8de52fb287 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 518b624304 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 00894bdc20 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new b5a22d0fe8 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 25a2794a99 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new 2b81c746df 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 92488ccc65 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 3969b5189f 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new c128e336f7 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 64122bcbaa 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new a5c8c303e2 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new dcde094569 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 7803f566b7 134: onsuccess: #1736: 1: Success after binutils: 3 commits new d045550730 135: onsuccess: #1739: 1: Success after binutils: 4 commits new a5911fc861 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new f7c6393f14 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new cf6e7b265d 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 912bb29bcd 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 7d789c4344 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 449c1a60f7 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new e86d971784 142: onsuccess: #1761: 1: Success after gcc: 83 commits new d764e4cc7d 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 88d1ca9717 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 7c98d2f948 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new 00a1f87e58 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new a3da4a0cd7 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new cbf6468a47 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 214d7618fe 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 26df9e81ec 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 37f0c50cc6 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 9775c24f55 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new c78c11f45b 153: onsuccess: #1773: 1: Success after gcc: 4 commits new 65141c8fba 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new bcfa86308b 155: onsuccess: #1775: 1: Success after binutils: 2 commits new 8555da4261 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new ea0cdbf669 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new 25a7184b5e 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new 82d30abb8c 159: onsuccess: #1779: 1: Success after gcc: 2 commits new 692a218596 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new add1236f33 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new 89d9278dfd 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new 9a817d58a5 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new 14cdd1fb78 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new 2a3fd7a9db 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new 1fc89b1cf6 166: onsuccess: #1786: 1: Success after gcc: 10 commits new e6d4e23387 167: onsuccess: #1787: 1: Success after gcc: 8 commits new 9f7eaebb06 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits new b56f835a55 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits new 7abd34614d 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits new 2d2dda345c 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 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 (bf043008c2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (2d [...] 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 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 51960 -> 51396 bytes 04-build_abe-gcc/console.log.xz | Bin 234108 -> 234120 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3808 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3948 -> 2548 bytes 07-check_regression/console.log.xz | Bin 5552 -> 5016 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 122 +- 08-update_baseline/console.log | 38 +- 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 2800136 -> 2810652 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2360200 -> 2357732 bytes sumfiles/gcc.sum | 4860 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 913276 -> 909460 bytes sumfiles/gfortran.sum | 60 +- sumfiles/libatomic.log.xz | Bin 2164 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204440 -> 204876 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2536 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468624 -> 468208 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2622 insertions(+), 2662 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 (22218a2e5a -> 9cc049ddc2)

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 22218a2e5a 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 450f30d492 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 0d7e2f6455 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 6aba51a1fc 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 74f6a0bd04 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 9c342d0c84 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 62a1a770e5 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards bb9a26491f 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 0f8bd032cb 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 69666dc9a9 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 015a5b072f 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 1f492c06a1 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 2a26378aa2 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 6e43586169 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 78831c1cfd 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 16cd349383 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 37d6dcb946 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards ce98df23a9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 0d7c785a71 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 04af39b9f0 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards bd1270d101 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 1725cac99d 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 4dd9aa1f6a 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 3256fe5eee 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards c42f0a1812 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 0f4df8aec8 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards feb058d58f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 7a22e65646 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 80ad6e13b9 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 04b72780af 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 21264f1b13 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 3f2c606640 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 45719a330a 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 2a9a71a420 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards c073f9d3db 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 726025ac66 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards fe22393d59 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 39f4a1b798 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 9ded356e65 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 23f8204fbd 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards cfd06e24b0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards ff02477f4e 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 7bca415181 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 68847552db 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards f43cb6ff69 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 824de7865d 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards afbcd49a44 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0d7af62a22 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 1851c30f60 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards bc81afb17c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 3e277b0413 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 000c1e7f8c 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 52de90d588 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f49095129b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 5b74fa32ea 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards d207680feb 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 581a6cf96c 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 30f363efef 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards f88a00b2c4 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 5f95ec78fb 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 9061ae6acc 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 3464ddb026 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards f58f2c75e6 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 711ab3d832 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards cda2787f74 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 2874a33cec 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 09780ccfd5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards bf48ee3235 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards bb0000e4cf 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 5e83c280e8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 5b6809d7cf 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 88d4a4d1f8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards d4fbaa667a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1c1f8cbf86 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 1459ea44d1 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 18e303f8b1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 23c9d28d48 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 80de97cf78 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 132a0d11db 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4ae18547a3 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards c40cc1850d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards d21c55d731 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 4bb9c47cd0 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 35ccf06fbe 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 5c9f3b5221 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards f597b15025 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards de8c566ac0 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 83dc123e07 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards ad58a42a48 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards e3e3cabf96 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 274de1f6cb 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards acf3bf9e23 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2cf4006b6f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 2782b74b74 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 00bff74630 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5ad4e371c7 75: onsuccess: 1: Successful build after linux: 44 commits discards 4c8dae6a62 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 596dc1e4c5 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 516a96a491 72: onsuccess: 1: Successful build after linux: 12 commits discards 9911c3be18 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards b1b0957b27 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 3aaad0eb3b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 38c6028b1d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new a03c098fec 72: onsuccess: 1: Successful build after linux: 12 commits new ad1cde4aaf 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc768470cc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 51ae1faee6 75: onsuccess: 1: Successful build after linux: 44 commits new 13c26c26cf 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new feccadf3ef 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new c2a5319622 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 8ce6b3a502 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4da74eda18 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a1fe1256ad 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new bc67c34f64 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 764cd2bf89 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 1661cc2150 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 10b7e42fa3 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new ee6c374e81 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 95e31baa5a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new a6cb5bbca9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 1269991640 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new d1960f87b2 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 67c2f21834 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 32dc207869 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a004202215 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 3553982143 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 3bdefa4dd9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 4f64ebebbe 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 1b259620b5 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new f690b5452a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 5492f156ae 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 1c3762e792 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new d62d670f98 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 99015e63fd 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new b0b63fbb0b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new d0a0b92bad 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 0e5997b3cf 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new c014068a1e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 507f7b9151 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new cc4d5a1838 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new e9a164f6ba 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new fe41397130 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new dffecb1d22 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new e332748def 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 74b1301e96 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 8fef47ca9f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 7b82ab00c1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 42aab777de 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 683dc598d0 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 315e673f0f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new da0e62e672 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 956b7cd1e0 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 7d399113f0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5842eebac2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 3ac48cf542 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 1d00f27910 124: onsuccess: #2159: 1: Success after linux: 23 commits new 4feba58d50 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 4ab13254c5 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 0e15d94ca6 127: onsuccess: #2162: 1: Success after gcc: 9 commits new a12b970c40 128: onsuccess: #2163: 1: Success after linux: 23 commits new a576061e22 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 1049d360ea 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new ff3bb5ba7d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 96427b939a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 4e1d510c9b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 827a8e9af9 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new e56d500351 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new ca2f8474e9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 4008dc44c9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 46b713fbe0 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 4c341c1b28 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 75517dbb15 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 3d92732235 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 5b83db90d7 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 4f29b97e69 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 669a411ae7 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 2af70daf59 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 43f0b9b576 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new b62853d59c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 079eeaa5ce 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 0e5495707b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 36d0a79838 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 550918f1cd 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 0344969ff5 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new b966d8d40c 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new dc02457201 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 46864dbd32 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 12dd0c383f 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 5b55a6ed7d 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new dc45ac7bfa 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 3cdff9ecd4 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 84b5ea73c9 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 12f6f57c1b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new b92616319b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 2a2c291883 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 0aedc64490 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new ef1b6c4a09 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new a144d890b1 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 3e12cc140d 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new da43183c45 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 0b2f795704 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new bc660d614f 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 9cc049ddc2 171: onsuccess: #2206: 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 (22218a2e5a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30872 -> 30508 bytes 04-build_abe-stage1/console.log.xz | Bin 73836 -> 72864 bytes 06-build_abe-linux/console.log.xz | Bin 9484 -> 9024 bytes 07-build_abe-glibc/console.log.xz | Bin 239708 -> 239540 bytes 08-build_abe-stage2/console.log.xz | Bin 204500 -> 203100 bytes 09-build_abe-gdb/console.log.xz | Bin 38052 -> 37352 bytes 10-build_abe-qemu/console.log.xz | Bin 31656 -> 31716 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 4144 -> 2900 bytes 13-check_regression/console.log.xz | Bin 26556 -> 26296 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 346 +- 13-check_regression/mail-body.txt | 224 +- 13-check_regression/results.compare | 465 +- 13-check_regression/results.compare2 | 7353 +++++++++++++++++-------------- 13-check_regression/results.regressions | 154 +- 14-update_baseline/console.log | 68 +- 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 | 226 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 154 +- sumfiles/g++.log.xz | Bin 3400624 -> 3405488 bytes sumfiles/g++.sum | 5874 ++++++++++++++---------- sumfiles/gcc.log.xz | Bin 3007952 -> 3041640 bytes sumfiles/gcc.sum | 4842 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1035680 -> 1032700 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202704 -> 202256 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423672 -> 422684 bytes sumfiles/libstdc++.sum | 6 +- 44 files changed, 10597 insertions(+), 9208 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-aarch64-next-allnoconfig updated (1bf47fdc81 -> 9f1df652aa)

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-allnoconfig in repository toolchain/ci/base-artifacts. from 1bf47fdc81 12: onsuccess: #324: boot: Success after binutils/llvm/linux [...] new 9f1df652aa 13: onsuccess: #325: 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 1704 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30148 -> 30112 bytes 04-build_kernel_llvm/console.log.xz | Bin 63636 -> 63784 bytes 05-build_abe-qemu/console.log.xz | Bin 31636 -> 31856 bytes 06-build_linux/console.log.xz | Bin 3072 -> 3092 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4332 -> 4220 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-defconfig updated (64acf37887 -> bb28cd6c79)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-defconfig in repository toolchain/ci/base-artifacts. from 64acf37887 14: onsuccess: #431: boot: Success after binutils/llvm/linux [...] new bb28cd6c79 15: onsuccess: #432: 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29960 -> 30132 bytes 04-build_kernel_llvm/console.log.xz | Bin 65024 -> 64512 bytes 05-build_abe-qemu/console.log.xz | Bin 31688 -> 31828 bytes 06-build_linux/console.log.xz | Bin 4232 -> 3280 bytes 07-boot_linux/console.log.xz | Bin 5668 -> 5656 bytes 08-check_regression/console.log.xz | Bin 4352 -> 4508 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_kernel/llvm-master-aarch64-mainline-allmodconfig updated (4ef3c7d34d -> 28742c7d37)

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-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 4ef3c7d34d 23: onsuccess: #500: boot: Success after binutils/llvm/linux [...] new 28742c7d37 24: onsuccess: #501: 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 1720 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30264 -> 30676 bytes 04-build_kernel_llvm/console.log.xz | Bin 64148 -> 63844 bytes 05-build_abe-qemu/console.log.xz | Bin 31812 -> 32052 bytes 06-build_linux/console.log.xz | Bin 3096 -> 3140 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 4440 -> 4448 bytes 08-check_regression/mail-body.txt | 8 ++++++-- 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 | 10 +++++++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 37 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_gnu_native_check_gcc/master-arm updated (eee4783e9e -> dfb7685eba)

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-arm in repository toolchain/ci/base-artifacts. from eee4783e9e 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new dfb7685eba 59: onsuccess: #502: 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 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2708 bytes 03-build_abe-binutils/console.log.xz | Bin 50508 -> 51232 bytes 04-build_abe-gcc/console.log.xz | Bin 232932 -> 234540 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9480 -> 8988 bytes 07-build_abe-glibc/console.log.xz | Bin 231568 -> 233344 bytes 08-build_abe-gdb/console.log.xz | Bin 48432 -> 49472 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2472 -> 2620 bytes 11-check_regression/console.log.xz | Bin 7580 -> 8356 bytes 11-check_regression/results.compare | 30 +- 11-check_regression/results.compare2 | 578 ++-- 12-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 | 36 +- sumfiles/g++.log.xz | Bin 2878968 -> 2849980 bytes sumfiles/g++.sum | 362 ++- sumfiles/gcc.log.xz | Bin 2477456 -> 2532568 bytes sumfiles/gcc.sum | 4914 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 936988 -> 946472 bytes sumfiles/gfortran.sum | 62 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 218156 -> 218100 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 459680 -> 466028 bytes sumfiles/libstdc++.sum | 10 +- 38 files changed, 3283 insertions(+), 2762 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022