Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig updated (5ae1986649 -> bc0c816892)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 5ae1986649 14: onsuccess: #462: boot: Success after binutils/llvm/linux [...] new bc0c816892 15: onsuccess: #463: 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 1724 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30388 -> 30404 bytes 04-build_kernel_llvm/console.log.xz | Bin 65340 -> 66084 bytes 05-build_abe-qemu/console.log.xz | Bin 32484 -> 31868 bytes 06-build_linux/console.log.xz | Bin 1319564 -> 3340 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4412 -> 4480 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (ebccba794d -> f740145c1e)

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-arm in repository toolchain/ci/base-artifacts. discards ebccba794d 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 9af2fa35c8 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 62d59b4e77 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 1cd151a29d 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards fabfa1ac5e 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 3a84a02c5b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards dcfcbb4533 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards dd8390e727 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 6348b003eb 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards afaabcc932 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 2b2c3b52d1 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 9f57a6cd68 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards e337db5fce 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 1b777fe23b 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards e882f855b6 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 0c777cc9cb 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards fa09e80cb4 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 3beebe4241 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards a1088150c6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 553467d5c5 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e41b02d3ad 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards d06f5f0aba 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards a2f8477937 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 49652ca0f5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards da93af8e04 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 65929ff61f 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 9cae6bef7d 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 7bcad40a59 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 2d9ff1f765 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 85f401c44a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards a6b05eee0b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 809b2f0401 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards ca36de303c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 9b6387d3ca 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 3c0032822e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards a3e97142c5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 6de7ad4fc2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 185600ea17 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 06c6b51e1c 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards ed681e6fbd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards bc99b41690 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards a20147f819 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards a33ce18f1f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 26df55c527 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 5e440d9da4 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 7135137f33 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3f30ad3e83 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 5301abe0b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards f1d8afdf6c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 52af317d70 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 7cac034bd5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 379d2fc911 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 4e323516b4 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards f136f97440 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b20af5dd17 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards b28e5da168 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards aeb5bfb8f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 079e9018b8 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards a65b879e18 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards e1579594d5 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards b79f965a52 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 7e7dfb3787 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards dc8197d646 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 78367c3d1d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 9b06b11a67 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 6e48fe47cc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 6799706386 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2762a9c258 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3be5d40b63 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards eed676315e 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards c9c5729a86 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards f8c5b3f397 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards e1324f9c99 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 7008d1464e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 96f0f69f72 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards baf77675ba 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 29de8d109c 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 4a97824bd5 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 54bbdd9ed9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 12effb090d 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fafbe541dd 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards e4622fe5a2 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards da50b2ab01 74: onsuccess: 1: Successful build after linux: 44 commits discards ebfa0dd5df 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9572351a85 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1ff93305a6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 37947d456b 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards b1205e8f33 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards ee8eb078e6 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ca05f5fd8f 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f907217910 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0249e4d029 65: onsuccess: 1: Successful build after gcc: 4 commits discards baa3f1cf7e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fa861a46ed 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 268335eaf3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 874dfe7435 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3b05677f0f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b2e49a621c 59: onsuccess: 1: Successful build after glibc: 2 commits discards 08086c420d 58: onsuccess: 1: Successful build after binutils: 2 commits discards 56daf03552 57: onsuccess: 1: Successful build after gcc: 7 commits discards 84c6ccb287 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2d3b1a39a9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5668360fe0 57: onsuccess: 1: Successful build after gcc: 7 commits new 45294a07b5 58: onsuccess: 1: Successful build after binutils: 2 commits new d5c654dd7d 59: onsuccess: 1: Successful build after glibc: 2 commits new f5e0f6d887 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8766b9982d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 0bd234bbaf 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 1567f0b79f 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aea51986cf 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c93a6cebed 65: onsuccess: 1: Successful build after gcc: 4 commits new 886a88ec46 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ce8cb66de0 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9edd0d1d03 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e0afcd4e53 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 4c39bcd74b 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 8920c9dd7a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 1a3f0baa64 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3544a24dd2 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new deb1ef4af0 74: onsuccess: 1: Successful build after linux: 44 commits new 1b179d1fdd 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5df569e563 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 8d63ce45f0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5b3a19e5ff 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a895817304 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2f26b37c3b 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new bc64bff956 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 03029ca8aa 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new fe79e20ce7 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 3d16d80b30 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 40da81c920 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 56abce38e1 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2adb753fe8 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 6ea96986da 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 4255c80f5d 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3afbfdaafc 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3f784b01a4 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d632a4d99e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new d46cc3da38 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 886129b699 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new c7c41a21ba 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 9c6742eab6 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ce6fa07c3a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 357926a576 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 722e7ec551 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 44f24b26f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 8f706581ba 101: onsuccess: #1693: 1: Success after glibc: 14 commits new c4bb99fdc6 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new b9dd739de6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new b909bb8fea 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 13a14ffab5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 6394d41002 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 90f5d4cbac 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 660168e940 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 8bc646729a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new a5475a242b 110: onsuccess: #1703: 1: Success after gcc: 6 commits new b17fdd341a 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2f491d33d0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 68fe4b45b3 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 2404fb0813 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new e16ddc3a9c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 2217732be8 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 290a5e15f0 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 4b772ca222 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 6d68a4c99d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 9086b73b7d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 1abc3ef5bb 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new f4eb9e27e4 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 0abb50db5b 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 03b73a43a1 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 668872cbcc 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 80b117d534 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 9d7b9c42a0 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 7be11d9954 128: onsuccess: #1723: 1: Success after linux: 12 commits new 822cb98a20 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new a0e5265358 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new b5420abb87 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 9e6005598e 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 382579a31b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 718719eace 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 6914395f41 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 86b7c1f7ef 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 0ba633710c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a88998f3b9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 01008fadd6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 88b80a1030 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new b0f79df819 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new b7c59dcb72 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 001d9b0533 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new d19d6e37c1 144: onsuccess: #1743: 1: Success after glibc: 2 commits new f3a36367ad 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 875fe07cb0 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 928a584857 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 1b3c2b66df 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new ff770dc302 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 457b485c2d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new af219a0ec7 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 858a6ee4c4 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new e5e8b84557 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 37970634b0 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new c51b96d517 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new d9b7b677f5 156: onsuccess: #1757: 1: Success after gcc: 4 commits new f740145c1e 157: onsuccess: #1758: 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 (ebccba794d) \ 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 1700 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30076 -> 30184 bytes 04-build_abe-stage1/console.log.xz | Bin 90648 -> 90880 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8956 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 233936 -> 233852 bytes 08-build_abe-stage2/console.log.xz | Bin 223468 -> 222592 bytes 09-build_abe-gdb/console.log.xz | Bin 37192 -> 37328 bytes 10-build_abe-qemu/console.log.xz | Bin 32072 -> 31272 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2872 -> 2564 bytes 13-check_regression/console.log.xz | Bin 5688 -> 6160 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 44 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 37 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 64 +- 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 | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 - sumfiles/g++.log.xz | Bin 2696696 -> 2655104 bytes sumfiles/g++.sum | 142 +- sumfiles/gcc.log.xz | Bin 2205840 -> 2234564 bytes sumfiles/gcc.sum | 2560 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 887700 -> 882444 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201532 -> 201476 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432028 -> 428400 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 1501 insertions(+), 1620 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (d3ae91fcad -> 22b11c8e6e)

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-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards d3ae91fcad 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits discards 19b8b76708 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits discards f71716f44d 152: onsuccess: #1579: 2: Success after gcc: 2 commits discards 39cf0ddd4f 151: onsuccess: #1578: 2: Success after gcc: 2 commits discards 2f2a62bcc1 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards af969bf87f 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards ccd4351a42 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards d82df82df5 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards fe70e1b1f5 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards b6630ceede 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 5cd242c93a 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards 532eee14a5 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 66008454f7 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 658f6aa45a 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards e9bbe6e0ea 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards a61dc54e1c 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 530503ec6f 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards d9c80a1dae 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards bf02087697 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 320d3653c8 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 1cb2bbe1c6 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards d45f8caaa0 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards f21fa521cb 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 97f4184d4d 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards e679b908d8 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards d4c7890642 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards b383a5e16c 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 67b37a4d56 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards aff2f02cf7 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards b437aa3189 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards c49efd27ae 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 0b3c41ae27 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards cbb4026bd3 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 6292b51fc5 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards a36bbec7f2 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards e5f2a20b36 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 35e75ddb85 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 06839a6dda 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards a6e181df01 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 7fbbe6c66a 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 6718e90894 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 0489ca1a90 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 63fcf97377 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 66daaca269 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards b068c5a142 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 832ac4a487 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards af4225f443 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards b26e3e7247 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards b88442ae5b 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 802d5be8ea 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards a0a2020516 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 93d33074b1 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards bc452583c0 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 0d37c77103 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards f8b4e8daa6 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards dadcc68ef1 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 582389ff00 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 7bf1444ada 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 6a5055defe 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 5d0811c839 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 7364cf79c2 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 0e89437239 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 4513824fe5 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 61f24f4d3a 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards eb965aa03d 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 8b5c8af771 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards a3f2840ae6 88: onsuccess: 1: Success after gcc: 20 commits discards d26a77d116 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 0c4cff0d27 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards ad31a3f518 85: onsuccess: 2: Success after binutils: 4 commits discards 5abbf3bd40 84: onsuccess: 2: Success after gcc: 9 commits discards 161da0f08c 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards e27be0a2e7 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards eadd1e1c61 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 4ef1c655cc 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 2fbcd8b731 79: onsuccess: 1: Successful build after gcc: 3 commits discards 495932f879 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards cd864cb72d 77: force: 2: Successful build after gcc: 32 commits discards a1af02045a 76: onsuccess: 2: Successful build after binutils: 10 commits discards 561025b851 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a4fc167be3 74: onsuccess: 2: Successful build after gcc: 13 commits discards 0d31871bc7 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards fe3d82abaf 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 1274b745e3 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1f95a93f6a 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 410e18a434 69: onsuccess: 2: Successful build after baseline build: no [...] discards d9af3b2852 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 3cc02a7509 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 27563f0545 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards da458845dd 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 1f0ea1ee6e 64: onsuccess: 2: Successful build after gcc: 7 commits discards f686baa13c 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 6b2a944e54 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 057beeac22 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 7622a11a32 60: onsuccess: 1: Successful build after gcc: 15 commits discards 40f39bf50c 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 086d97b460 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 0495418cde 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards a3a402743b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 529bdce97b 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9e6b133af7 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 339e743a6b 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 40d358c4eb 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f41574a4db 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 9aa137682b 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new ab5cf88ef2 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 693d4b8166 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 7b0878f999 60: onsuccess: 1: Successful build after gcc: 15 commits new b34723e8e4 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 91fd0175ee 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 615fe50c95 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 004b376701 64: onsuccess: 2: Successful build after gcc: 7 commits new ca9bc11b58 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new f9cd98eec0 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 556df20d5a 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b899ab7e92 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b3656ac48d 69: onsuccess: 2: Successful build after baseline build: no [...] new 4dceb06e2f 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 430279652e 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c2d204422c 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 2129f3ef0d 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new f26458c516 74: onsuccess: 2: Successful build after gcc: 13 commits new 5de7dfe935 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new b24e3077a2 76: onsuccess: 2: Successful build after binutils: 10 commits new aa4fe7e4f1 77: force: 2: Successful build after gcc: 32 commits new 25161b7830 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 075d40893d 79: onsuccess: 1: Successful build after gcc: 3 commits new a69b9c9f94 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 73aa3c4f3e 81: onsuccess: 2: Success after binutils/gcc: 16 commits new c421cff2b1 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 0c9773cd8b 83: onsuccess: 2: Success after binutils/gcc: 7 commits new fa38cca73c 84: onsuccess: 2: Success after gcc: 9 commits new d774004794 85: onsuccess: 2: Success after binutils: 4 commits new 0d4352ec61 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new b1ecd35dfd 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new bb14680457 88: onsuccess: 1: Success after gcc: 20 commits new 5ab19a073a 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 67a468cc38 90: onsuccess: #1472: 2: Success after gcc: 2 commits new a92c253280 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 672a654ad4 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 6b4fe9eaf9 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 9cc667a70f 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new af9f972d9e 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 5d11342ca5 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new be280762a5 97: onsuccess: #1481: 2: Success after gcc: 8 commits new e7c3ea92f2 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 626c72826f 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 02147de5aa 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 8841ba1786 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 01cf4f7baf 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new dfd67ecca5 103: onsuccess: #1524: 2: Success after gcc: 2 commits new a71881fa3b 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 8ac56721e6 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 34e8e375db 106: onsuccess: #1527: 2: Success after gcc: 2 commits new c1454feabc 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 1d806b567d 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new f3c8f15074 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 309a26be30 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 19f39a9058 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new e75f8687fc 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 7f8a966a55 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new aad77732c3 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new e60104e452 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 947589be93 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 4628b6c3f3 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new d9f59c3827 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new eeaa7d5e49 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 07451cdcad 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new dca7b4634d 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new fe94950d16 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 0e45d967b9 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 9f67dbd66c 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 29da3a6b10 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 3d574ce457 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new f6ff834254 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 97b198803f 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 4a39755e81 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 6853aeaaba 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 7b72e4ccee 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 46cc46e40c 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new c1a562f907 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new e65c93ac55 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 35471273eb 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 454d36de67 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 09ffe02491 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 2d69bdee5d 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new d587544d2a 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 345c85ed3b 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 247bf5fe63 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new c3450b73c9 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new e519141755 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 8e9f819905 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new f12cfb182e 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new b3a0e0eb3a 146: onsuccess: #1573: 2: Success after binutils: 7 commits new df5a817195 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new 79dd2176ec 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new 6fd4e5d935 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new cd2fdc90cd 150: onsuccess: #1577: 2: Success after gcc: 3 commits new d003c4eff8 151: onsuccess: #1578: 2: Success after gcc: 2 commits new 0da65ecc7b 152: onsuccess: #1579: 2: Success after gcc: 2 commits new fc723ebd27 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits new 17230b9af5 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits new 22b11c8e6e 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 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 (d3ae91fcad) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1672 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38216 -> 37672 bytes 05-build_abe-bootstrap/console.log.xz | Bin 270628 -> 269692 bytes 06-check_regression/console.log.xz | Bin 3024 -> 2880 bytes 07-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 +++++----- 13 files changed, 47 insertions(+), 47 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 (6d219ffe67 -> 64acf37887)

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 6d219ffe67 13: onsuccess: #430: boot: Success after binutils/llvm/linux [...] new 64acf37887 14: onsuccess: #431: 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 1716 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30996 -> 29960 bytes 04-build_kernel_llvm/console.log.xz | Bin 63148 -> 65024 bytes 05-build_abe-qemu/console.log.xz | Bin 32168 -> 31688 bytes 06-build_linux/console.log.xz | Bin 6080644 -> 4232 bytes 07-boot_linux/console.log.xz | Bin 5688 -> 5668 bytes 08-check_regression/console.log.xz | Bin 4600 -> 4352 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_gnu_cross_build/master-arm updated (7e73ab5066 -> e11b990255)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 7e73ab5066 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards 1701088e33 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards bcd26242bb 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 839cdeced4 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards c6612840ef 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 7f328d7c8f 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards 1ac2d6e841 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 0fa7c06b83 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 4ca2da5710 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards f9d5cbed53 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards bd8303db12 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards dbb9f48324 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards c0ea47b995 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 6d2998a4c3 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards a803702533 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards b8bdd13243 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 22e345f38d 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 1c19605622 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards d0c43e9192 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards e2d9e22b89 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 7fc241f3bf 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 95e387365a 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 1150cd89c1 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 221fd7d3a9 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards ec7ae68788 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards e373206256 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 882eb2f18e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 75c0af8031 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 6736a89f7a 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 35e62d7167 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 3fa6a3c028 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 7089616024 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards adfa47e84d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards e1bfb2fd3f 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 51b4415095 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 58ace28472 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards fe09bd97d7 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 45dc69ae26 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards d79b8e77be 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 91909f1019 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 1d0e854441 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards c1ac5df4e7 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards f1e71cdd87 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 92defe93b9 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 1fe4ab3767 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 5c107d5bd0 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards d0d4898a7c 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards d568b59611 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards d7a453d7c9 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 6b01cb23c7 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 999eb53f16 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 545e96a0e0 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 2772cd2496 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 96973cf7f4 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 1a6508fe8d 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards de53fb8c85 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards ed7ed91536 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards d23704bc00 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards edc3a28a8d 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 1a9cca7e28 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards fe9a61579a 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 99a81ad410 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards c2c3a4b900 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 732d3514f2 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 45665e521b 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 7b144dbae0 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 313bfb2176 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 8220bb8f71 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 5a681c4cf7 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 97d5f89354 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards a8e3f39417 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards af8cbf9556 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards ca609c3418 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards dd9159b84c 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 5ec3059fe7 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 48b4efc901 85: onsuccess: 7: Success after gcc: 9 commits discards 2934fcb684 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards ee8e8b6ac2 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 1946df345a 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 30aea6aa01 81: onsuccess: 7: Successful build after gcc: 2 commits discards 41699e62e4 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 87e41ca8b9 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7ff96c8a0c 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ee471ca07f 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards af79f5011b 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 33bbb2a971 75: onsuccess: 7: Successful build after linux: 44 commits discards dd1f5f2e99 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 0593ff11e8 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 758ccd4cbd 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards f6fa4583e2 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 795ad8bab0 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards d73671ba06 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards ada926e41e 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8cfb060ddc 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 3b47ac3346 66: onsuccess: 7: Successful build after gcc: 3 commits discards 9af4a7e7c8 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 39ec9d363f 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9279d55d0e 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards eefb4c7cb2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 9d47d14e8d 61: onsuccess: 4: Successful build after gcc: 15 commits discards f781dd7177 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new b9a59599a3 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 9953ff8ac5 61: onsuccess: 4: Successful build after gcc: 15 commits new 44ae4e9f8e 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new cbbf8e3ec6 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new fed89f2f9d 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4cdf4408d4 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a44a2dfd57 66: onsuccess: 7: Successful build after gcc: 3 commits new 71589c026a 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 387cc9bcbb 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3fa9b08bd4 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 78e6aee410 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 0cd8fa9e2a 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 6baa688f5b 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 9a68ee3a60 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f7af90ddb7 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 1dab418676 75: onsuccess: 7: Successful build after linux: 44 commits new 7758e7a84d 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b0584d89cc 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 359cae1f6d 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c872234740 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9592f60ca3 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new b4d17ff78e 81: onsuccess: 7: Successful build after gcc: 2 commits new 8c419d8de4 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 9faf3fc9bd 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 5e5a973041 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new b5d7150d23 85: onsuccess: 7: Success after gcc: 9 commits new 68e9a60510 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 74d3bb4ff2 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new f379b4599d 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 946fee573c 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new e8dfe1710e 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d240d62ec5 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 85dad9617d 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 210500f23b 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new a6c3cd593e 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 97b38b8112 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 144254ebf7 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 6415e0936b 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 239fd223eb 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 49a53011ac 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new a32bd95868 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new cdedf97e28 101: onsuccess: #1609: 7: Success after binutils: 78 commits new fbc8953e6d 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new a7f7a694ca 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 4aa1a53eb4 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 651d6df521 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 5ea4988cfb 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 8a4cf6108d 107: onsuccess: #1618: 7: Success after gcc: 2 commits new e3cc1d0881 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 5337360819 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 17dbfb9706 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 539e0a666d 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 44a43a295b 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 1e18d1440d 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 6c930756a1 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 3a61df6950 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 15432b249e 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new ee5f3a97cf 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 6939374619 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new ea8c80867a 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 7cecb9c69b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 4c449b33c2 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new e234da3411 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 8e5cbaa3ca 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 19d04e3c95 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 5841ff80f6 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 32a05d55e0 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 676293c595 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 2fd0490736 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new e78a7cc0f3 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new e861f06571 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 54fd24fcae 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 6ac2d34e0b 132: onsuccess: #1645: 7: Success after linux: 23 commits new f37bc54713 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 60da4cee2b 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 96765c13a1 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new c68020be2f 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 2d1c14d099 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 2a4a9e16a5 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 90d8c6c72d 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 6c06dae84f 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new d3e3f287cb 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 913b2f0534 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 390ae6bccf 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 6f26098541 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 9bcf5c318c 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 849bf278b2 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 2b8e94be9f 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 02502ae1e7 148: onsuccess: #1663: 7: Success after glibc: 2 commits new e265e7a19e 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 240b4aca52 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new d050438f89 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 51bb85f231 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 02a379e7ee 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 9309e9109f 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 3c31bcac4b 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 0a95bc69d5 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 4d61c7dec3 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 25f49d1c92 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 67efe6c568 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new 8de402f62b 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new e11b990255 161: onsuccess: #1676: 7: 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 (7e73ab5066) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1696 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30628 -> 30100 bytes 05-build_abe-stage1/console.log.xz | Bin 90728 -> 90848 bytes 07-build_abe-linux/console.log.xz | Bin 8908 -> 8512 bytes 08-build_abe-glibc/console.log.xz | Bin 233472 -> 233736 bytes 09-build_abe-stage2/console.log.xz | Bin 225116 -> 223688 bytes 10-build_abe-gdb/console.log.xz | Bin 37948 -> 37420 bytes 11-build_abe-qemu/console.log.xz | Bin 31496 -> 31360 bytes 12-check_regression/console.log.xz | Bin 3756 -> 4276 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++---------- 20 files changed, 59 insertions(+), 59 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-allmodconfig updated (a35c908ac0 -> 72873361af)

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-allmodconfig in repository toolchain/ci/base-artifacts. from a35c908ac0 25: onsuccess: #552: 36: Success after llvm: 118 commits new 72873361af 26: onsuccess: #553: all: 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 1772 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30368 -> 30348 bytes 04-build_kernel_llvm/console.log.xz | Bin 65720 -> 64272 bytes 05-build_abe-qemu/console.log.xz | Bin 31768 -> 31844 bytes 06-build_linux/console.log.xz | Bin 3568 -> 3108 bytes 07-boot_linux/console.log.xz | Bin 0 -> 504 bytes 08-check_regression/console.log.xz | Bin 3064 -> 4536 bytes 08-check_regression/mail-body.txt | 11 +++-------- 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 | 13 ++++--------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 4 +++- 19 files changed, 34 insertions(+), 39 deletions(-) create mode 100644 07-boot_linux/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-defconfig updated (45a207971d -> 3c9f3b9899)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from 45a207971d 11: onsuccess: #487: boot: Success after binutils/gcc/linux/ [...] new 3c9f3b9899 12: onsuccess: #488: 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 1704 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30432 -> 30572 bytes 04-build_abe-stage1/console.log.xz | Bin 72620 -> 72292 bytes 05-build_abe-qemu/console.log.xz | Bin 32272 -> 31908 bytes 06-build_linux/console.log.xz | Bin 5640 -> 5632 bytes 07-boot_linux/console.log.xz | Bin 6252 -> 6248 bytes 08-check_regression/console.log.xz | Bin 4436 -> 4456 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

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (60a3cd7a06 -> 91bebf899e)

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_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 60a3cd7a06 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards f923e4f6da 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards 4225951f76 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 1ec68e5bf4 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards cd70b56d0c 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards 0f467d2eac 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 9cf398a612 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards b96417f884 152: force: #1605: 7: Success after gcc: 9 commits discards 07e7582890 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 45745f3332 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards b34497026a 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 4b7f2798e3 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 4afca552ed 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 802d77262d 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 235bf898a2 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards c206a37e7c 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards ea38c0029f 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards c154a4f422 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 3b892a5e37 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 7dd0b12020 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards d772d39889 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 0cbe1a26f2 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards cb90e385fb 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 22d40b9e7a 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards dd31bcf752 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards d0ad94469a 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 28714960cb 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards d44e376f0e 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 1f362b4906 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 541558ddde 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 24cc3e8eb4 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 3be7ec6e7d 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 9caeb080b3 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards c3a102d532 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards d40c9be29d 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 1875495ae3 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 31108e5da5 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 9e27257dd1 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 54bcb79e38 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards aeac4a3ed7 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 1b03871248 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 93c4f2ae94 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards b2275e9fed 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards d734833654 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards f98525d12d 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards d367a2aafc 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards cf55bbe302 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 4ec5a84307 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards c197c5b15d 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 03e690785f 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 65352e352f 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards ef513e3eac 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards e0c4c47f55 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 7e15ab1407 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 631f3ca597 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards cb245a4088 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards abfef80665 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 0d17e6ad13 102: force: #1551: 1: Failure after gcc: 306 commits discards 1cba7c1d0c 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards ea08f4e31d 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 90229fc493 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 039032bcce 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 400652cda3 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards faa3fd82b4 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards d55e86e42f 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards bbf4732637 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 3fe108bb8d 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards bbb821dfaa 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards e4225e4b72 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 3b5f364c05 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards f169fe305a 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 6a39ef7f33 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 0ee8116b35 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 7a30f6f391 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 78b10a7d9c 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 88b2d015a7 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 40a7586b1a 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3d4b00dcc6 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards b36699094a 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d801300802 80: onsuccess: 7: Successful build after linux: 44 commits discards 002c7ec127 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards ee333e60a6 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 8f4c03dd1e 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9bef6434c0 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards b0af0062b5 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards ab967ab2d9 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ddc3928f3c 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 27f7eaf739 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8002a8654c 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fb4f55d7cc 70: onsuccess: 7: Successful build after gcc: 4 commits discards 2c5529f10c 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 76e3c631a1 68: onsuccess: 7: Successful build after linux: 6 commits discards 6438ead306 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards a736141f24 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 68f1b10702 65: onsuccess: 7: Successful build after binutils: 3 commits discards 21e1995d0d 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards ce746a5f4e 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards bb613e303b 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards c2f8b91b1e 61: onsuccess: 4: Successful build after gcc: 5 commits discards d5c745bd3c 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 4895dc8ee5 59: force: 7: Successful build after gcc: 3 commits new 2564644cd9 59: force: 7: Successful build after gcc: 3 commits new 505e8599ea 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 6ea8be9d00 61: onsuccess: 4: Successful build after gcc: 5 commits new dfd449b122 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 5b303716fd 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new a97784af3f 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 75d3a49ffd 65: onsuccess: 7: Successful build after binutils: 3 commits new 7d09528155 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 57dd16a5e1 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 404d98d3c0 68: onsuccess: 7: Successful build after linux: 6 commits new 2451b278bd 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new db70d8d3ec 70: onsuccess: 7: Successful build after gcc: 4 commits new 2535496150 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 0a7796ff02 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 57e4d14a95 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 63cd6fc938 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 9d2ce55a92 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 54126b0185 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 8886c63dd5 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 865a8e732f 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new e9fb76319b 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 59751b8ab5 80: onsuccess: 7: Successful build after linux: 44 commits new 11cae9a73d 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 81be855131 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new badb8324a7 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 87c5e13057 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d145c791e1 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new f5189409cd 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new c8b343ef22 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new a884438879 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 26810453e6 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 15656c0dd8 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 485cc8774f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 167e0d8143 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 57d727fbe2 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 3671a2585f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 82025c3625 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 35168ded40 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 63cc8fb41c 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 6bfb5884d0 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 98a72f7802 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 60e53503a6 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new d689df0f15 101: onsuccess: #1547: 7: Success after binutils: 82 commits new d8ffa80d18 102: force: #1551: 1: Failure after gcc: 306 commits new 6556960d9e 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 4175db2d68 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new a61605a57b 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 7b0e02052e 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new b83feafa44 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new e1d71fea1a 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new a02b997849 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 93db4b3261 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 47e1bd93fb 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 1854a3da2e 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 80b7b37e49 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 9355b47cdc 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new aaabae0ecd 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 175075e9ee 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 33da039b01 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new a03b32fd55 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new a94f245040 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 30f95bece1 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 3f6ace9e2b 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 3e7e880862 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new ad181b9bb1 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 964eff35f7 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 405d6558a7 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new e3f6238094 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new f30d711027 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new df7f1f2930 128: onsuccess: #1579: 7: Success after linux: 12 commits new 500a155938 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 45bb6c37bc 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 6b9d93763c 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new d08ff1249c 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 1eb4b3f856 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 63057a60af 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 34fa3261af 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new cf21e57ead 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 6811c0a452 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 50f31fb807 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 648d53710f 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new b53983a1a3 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new e72b1d12dd 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new ce7902845a 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 8117e0197b 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 1a1775cbda 144: onsuccess: #1595: 7: Success after glibc: 2 commits new a16a829ec8 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 95f5f75c1c 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new ab1a125a0f 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 918aa81247 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 394f37e1d2 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 337b91a8ec 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 82b62275d5 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new f75c2bff4c 152: force: #1605: 7: Success after gcc: 9 commits new a1dc00f4bd 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new bf0c5c0774 154: onsuccess: #1607: 1: Success after gcc: 2 commits new f49724ebbd 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new 446da8ee91 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 3905286c0f 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 71cd79e7f3 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new d933d77351 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 91bebf899e 160: onsuccess: #1613: 7: 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 (60a3cd7a06) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1920 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 30244 -> 30352 bytes 05-build_abe-stage1/console.log.xz | Bin 72520 -> 72292 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8928 -> 8544 bytes 08-build_abe-glibc/console.log.xz | Bin 239812 -> 240268 bytes 09-build_abe-stage2/console.log.xz | Bin 203488 -> 203104 bytes 10-build_abe-gdb/console.log.xz | Bin 37372 -> 37612 bytes 11-build_abe-qemu/console.log.xz | Bin 31932 -> 31764 bytes 12-check_regression/console.log.xz | Bin 3332 -> 4248 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++---------- 21 files changed, 57 insertions(+), 57 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-aarch64 updated (c9cbf18666 -> a51c72f0d7)

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-aarch64 in repository toolchain/ci/base-artifacts. discards c9cbf18666 154: onsuccess: #2089: 1: Success after gcc: 4 commits discards 1dfefea628 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] discards 2468f7bbad 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] discards 883a41e65a 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards 03ff894c3c 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards e8c8efb7e6 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards 395d6ca0db 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] discards 62fffada52 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards c5c89b72a8 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards f77e07073f 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 6224afda52 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards f26bf6a971 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards 3dd63f74a0 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards c528b8c435 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards ad1506c871 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 4420338100 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 77d9108fce 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards b526021275 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 6268cc4be7 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards adfa335ff6 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards 2adf3a01db 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 5ff901348d 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 6cdbac918c 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 0a240623ed 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards fd3ce7e0de 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 35aca19414 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards 4b6be5552e 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards f5ac95f85b 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 96d061d760 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 1630d56b19 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards a3c75d8e72 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards f25503fca4 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 2c26af006a 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 9c7f8fd1ce 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 7e475a00de 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards ca719c1064 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 1f0a7ba875 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 2ac191abad 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 759eae518d 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 7948dad018 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards bc72612c67 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 885d043f68 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards cd0b7d64bc 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 1c20a91b50 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 7c6e38328d 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards cd20320efc 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 67204e3022 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 75a6817d63 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 95858b6ad2 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards f5b13b12d3 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 52f2704f1d 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards d763134cbe 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards e6034ffb55 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards edca4cfc17 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 45cdd9b89d 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards d90a9e2b21 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 8183c793f1 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 400667b915 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 0cc30a4807 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards aff0e1a33b 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 5f69382c3d 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 6fdf73064b 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards a6b9bbafa9 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards fe2ecbd00a 91: onsuccess: 1: Success after gcc: Daily bump. discards 0fc19a26c3 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards f29590316f 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards d58be10787 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards e364cedcbf 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 14e486c5f3 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 344cee9d4a 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 5a53635d78 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 008ed59bc5 83: onsuccess: 1: Success after gcc: 8 commits discards 84c096e2a2 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 0fe6c7edfb 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 262cd5c60c 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards e2c0e4e77c 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 3cb1180f7e 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 686cd33034 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 23d38ca617 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards e8ab019cb3 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 95f11eef6a 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 8dd360b863 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards cc97739687 72: onsuccess: 1: Successful build after gcc: 2 commits discards e4963164bc 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards ff44481147 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards be9cbaf782 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards f999ef9e7d 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 066b27a8cd 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards e50e22a26d 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 401d220fce 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards bc9cf32470 64: onsuccess: 1: Successful build after gcc: 5 commits discards d10648aca2 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 067d5b85f3 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards c660902ff6 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards bbd7bedbf8 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards a4fdcc88e0 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards b685b3b560 58: onsuccess: 1: Successful build after binutils: 2 commits discards a1e8128709 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards db852d4aad 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 50ddeb4e21 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 59853a802f 54: onsuccess: 1: Successful build after gcc: 7 commits new 46d4265081 54: onsuccess: 1: Successful build after gcc: 7 commits new f622e28443 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 5266afb9aa 56: onsuccess: 1: Successful build after gcc: Daily bump. new fa0af7b900 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 469a6add7e 58: onsuccess: 1: Successful build after binutils: 2 commits new 74a430a62a 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 9c18bcae21 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 6441419f39 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new dcca2713e8 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new ed1dcf4c69 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 7d1ed76631 64: onsuccess: 1: Successful build after gcc: 5 commits new 2aa898beae 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new c05b0d1bbf 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new a5e2126684 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 801d657134 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 0ff50b11a8 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 53cbc958b8 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 4bb787c8eb 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new dff9175ce9 72: onsuccess: 1: Successful build after gcc: 2 commits new 476e4b0581 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new b46cdda1d7 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 21e987825f 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new b50440ab83 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 7e63c83469 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new f27bac7e98 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 4303355d05 79: onsuccess: 1: Successful build after gcc: Daily bump. new 456e380736 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 324a4772eb 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 34347293c3 82: onsuccess: 1: Success after binutils/gcc: 10 commits new f61612e2c8 83: onsuccess: 1: Success after gcc: 8 commits new 9d2b989cf6 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 9f0d37db89 85: onsuccess: 1: Success after binutils/gcc: 9 commits new d44bf86de4 86: onsuccess: 1: Success after binutils/gcc: 13 commits new e11a2f74c9 87: onsuccess: 1: Success after binutils/gcc: 4 commits new a0527befac 88: onsuccess: 1: Success after binutils/gcc: 16 commits new b875fb6705 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 7f1f81b8e9 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 8be2631511 91: onsuccess: 1: Success after gcc: Daily bump. new c02e15e11b 92: onsuccess: #1965: 1: Success after gcc: 2 commits new e258000311 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new 7b0028bccc 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 3cd9d71bed 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new c2a592b44e 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new d0b6f4a2f0 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new c33a6d6708 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new e50b902d26 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 3ab03f1702 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 08c3b7eb9a 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new c0d1d2f310 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 32f9ca3db2 103: onsuccess: #2020: 1: Success after gcc: 2 commits new ee79ca0691 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 1b29cdf54e 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 87afffa9e3 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 4837819805 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 46de82f308 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 56be9c3655 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new a6d6649098 110: onsuccess: #2027: 1: Success after gcc: 5 commits new c0009690fb 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new d6daaf5fee 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new c9b1517b0a 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 7c9bf46ac9 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 1987c4a172 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 2acc8fc708 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new c8af5ce1a6 117: onsuccess: #2034: 1: Success after binutils: 2 commits new a9593bdf8f 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new bfa4c3a49a 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 6b1d4230d3 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 63077e14dc 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new bedbb65afa 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new bec0cc029c 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 2beebc7bc1 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new eb3794ec6f 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new f3f97f30e9 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 7a0165628c 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new 5454fc4acf 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new a5f1fa1b6a 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 5e4e753c74 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 26b42e1ed2 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new 08d762fe92 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 47e69c3927 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 6851887452 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new 062c6a8a7f 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new bd45cba44c 136: onsuccess: #2056: 1: Success after binutils: 4 commits new f2498b42ad 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 977ecd5442 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 517b27fcbc 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 132eb758f3 140: onsuccess: #2070: 1: Success after binutils: 4 commits new 2ffdde00d8 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 4e95e4ecb8 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new 45f1959ce4 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 4a0a61c9dc 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new 4b8083688d 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new d7c642a45c 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new f8482b05d1 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new 7db603e1c4 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] new d45a8b403d 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 0f8ac50e16 150: onsuccess: #2085: 1: Success after gcc: 2 commits new 43c776724c 151: onsuccess: #2086: 1: Success after gcc: 2 commits new da3ad1cc7b 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] new ba3426aed9 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] new b31d667a32 154: onsuccess: #2089: 1: Success after gcc: 4 commits new a51c72f0d7 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 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 (c9cbf18666) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 37564 -> 39444 bytes 04-build_abe-gcc/console.log.xz | Bin 213372 -> 213648 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3876 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2828 -> 2508 bytes 07-check_regression/console.log.xz | Bin 5200 -> 5324 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 12 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 25 +- 07-check_regression/results.compare2 | 58 +- 07-check_regression/results.regressions | 32 - 08-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 32 - sumfiles/g++.log.xz | Bin 3585388 -> 3573804 bytes sumfiles/g++.sum | 130 +- sumfiles/gcc.log.xz | Bin 3091848 -> 3132992 bytes sumfiles/gcc.sum | 5068 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041764 -> 1041148 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207636 -> 207700 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450640 -> 439628 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2745 insertions(+), 2815 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (dd4dd8e5b9 -> 16ab3383f6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from dd4dd8e5b9 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 16ab3383f6 57: onsuccess: #536: 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 1712 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 51960 -> 53788 bytes 04-build_abe-gcc/console.log.xz | Bin 233716 -> 236372 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8896 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 234588 -> 232292 bytes 08-build_abe-gdb/console.log.xz | Bin 49900 -> 51564 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2128 -> 4012 bytes 11-check_regression/console.log.xz | Bin 18956 -> 21636 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 121 +- 11-check_regression/mail-body.txt | 236 +- 11-check_regression/results.compare | 182 +- 11-check_regression/results.compare2 | 5621 ++++++++------ 11-check_regression/results.regressions | 164 +- 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 | 238 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 164 +- sumfiles/gdb.log.xz | Bin 1646508 -> 1713768 bytes sumfiles/gdb.sum | 11783 ++++++++++++++---------------- 31 files changed, 9611 insertions(+), 8961 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