Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-defconfig updated (671c1e2d58 -> 6864156ca7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-defconfig in repository toolchain/ci/base-artifacts. from 671c1e2d58 12: onsuccess: #264: boot: Success after binutils/llvm/linux [...] new 6864156ca7 13: onsuccess: #265: 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 1884 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30160 -> 30008 bytes 04-build_kernel_llvm/console.log.xz | Bin 64616 -> 62864 bytes 05-build_abe-qemu/console.log.xz | Bin 31668 -> 32112 bytes 06-build_linux/console.log.xz | Bin 4012 -> 3472 bytes 07-boot_linux/console.log.xz | Bin 5876 -> 5844 bytes 08-check_regression/console.log.xz | Bin 4060 -> 4328 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-norov-defconfig updated (68bea7498a -> 7d3f86b39e)

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-norov-defconfig in repository toolchain/ci/base-artifacts. from 68bea7498a 17: onsuccess: #52: boot: Success after binutils/gcc/linux/q [...] new 7d3f86b39e 18: onsuccess: #53: boot: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1712 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30872 -> 30128 bytes 04-build_abe-stage1/console.log.xz | Bin 73496 -> 72940 bytes 05-build_abe-qemu/console.log.xz | Bin 31496 -> 31932 bytes 06-build_linux/console.log.xz | Bin 5652 -> 5604 bytes 07-boot_linux/console.log.xz | Bin 6308 -> 6252 bytes 08-check_regression/console.log.xz | Bin 4412 -> 4320 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_gcc_check/master-arm updated (e5c6754a7b -> 480886c62a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards e5c6754a7b 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 8837579de2 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards 127924752e 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 176f2791f8 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 6b38c51538 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 0fa27ab758 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards a4c41de3ce 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards e8c5f35fe8 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards f860d0ddc0 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 9a689853a0 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards 7503adc963 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards a58a67c060 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 5a65763110 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 369dac8041 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 76bc1cd205 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 815e6a7dc1 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 2c9d1508c8 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 085968e88d 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 8bd94938b5 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 2ca88bdcc2 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 4a807f5df7 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 59a3f74cb4 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 150087d2f9 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 35c2cd36d1 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards e6f8e4d6f3 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 6e6b6f56b2 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 6e27cecddd 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 1f10c86213 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 8eb88c776c 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards fa45ced500 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 648fbcc82b 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards f04d8849de 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 26932b0bba 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 1513d6b92f 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 6d096ccab6 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 401d16d9a7 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 100307cf8a 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 36bcc707f6 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 533e275469 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 8e6f306ec0 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 6ac422fd7b 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards b2e8aa308f 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards f706177ec9 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards ce572ac9a1 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards c39e264088 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards e4e68b82d4 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards e75cb92635 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 5868c39bed 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards d76ec70d8b 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 79e105fabe 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards eee429079a 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 413ae2edd3 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards b60c37aac3 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards a4471cb6de 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 0126fc5588 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards c770f2940f 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 0b9245e4ad 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 0e097b28d4 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards aa3b57eecf 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 14cb4893a1 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 6de8e2fb33 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards a733ed1028 87: onsuccess: 1: Success after gcc: 6 commits discards bde659be3f 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 58d8942363 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards a7d33c4ea8 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards c11885fe52 83: onsuccess: 1: Success after gcc: 14 commits discards f7ffa2b756 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 3469b81359 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 7cff3d68c8 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards bbedf8c1ef 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 8b6e71d9ce 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 389d72b963 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 053e2cdcb8 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards c666e07500 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 16178d0fae 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 70049ebf21 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 115433d9f7 72: onsuccess: 1: Successful build after baseline build: no [...] discards c8e82f89a9 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards d7b348c97f 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 135c67610b 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards cf393d4c12 68: onsuccess: 1: Successful build after gcc: 2 commits discards 607250421e 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 7247655447 66: onsuccess: 1: Successful build after gcc: 4 commits discards 271438d724 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards ba9b69268a 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 099e8af444 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards d2445f9df4 62: onsuccess: 1: Successful build after gcc: 4 commits discards 33935508ea 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 6b8611d1d6 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 59468319e8 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 7b7c1bf05e 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards 4713c92525 57: onsuccess: 1: Successful build after binutils: 2 commits discards b46991ab0d 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 1495a0e119 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 42f12e2e7d 54: onsuccess: 1: Successful build after gcc: 5 commits discards e20b11efb1 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 81d9c14dd5 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 7faed9bb2d 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 7c21c0ab29 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 0c86c58bc1 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 50c3145b53 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 317118e5df 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 35d0113b79 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new b95c1a971c 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 8d8aee0533 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 03e2d5ed36 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new f6c765ce44 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 57da6ccdf6 54: onsuccess: 1: Successful build after gcc: 5 commits new 27419e0b2c 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 04213c90b6 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 591b3f53de 57: onsuccess: 1: Successful build after binutils: 2 commits new de7a103dbb 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new e54cbae059 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new c7102c8ba0 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new d1658ca8cc 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 903952e31a 62: onsuccess: 1: Successful build after gcc: 4 commits new dd382afef8 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 74e77ebde2 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 1330fc6a74 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 99fc76596d 66: onsuccess: 1: Successful build after gcc: 4 commits new e5fbc0ba49 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 5cc97fe869 68: onsuccess: 1: Successful build after gcc: 2 commits new 456971a36b 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new ef45c0081e 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 3cd38e71cc 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new df53c9c885 72: onsuccess: 1: Successful build after baseline build: no [...] new ddcbc3e68d 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new b1a49bcf8d 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 95060b0a02 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new c28eb7680d 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 223c674207 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 28481b7e65 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 03eaa6c8a2 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 52c97b508f 80: onsuccess: 1: Success after binutils/gcc: 8 commits new cc4e8f28ca 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 793e44cf4d 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 51ba76533c 83: onsuccess: 1: Success after gcc: 14 commits new 51b5dea19c 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 420d1c73ba 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 820848def1 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 51759969a7 87: onsuccess: 1: Success after gcc: 6 commits new cf7e2784a6 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 7986d18bf1 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 0462a4a18b 90: onsuccess: #1645: 1: Success after gcc: 2 commits new a771ab0a0e 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 5423cc0210 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 4cd1bb4b60 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 1071273851 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new c149721273 95: onsuccess: #1653: 1: Success after gcc: 13 commits new d3773b62a3 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 0efc2c3481 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 78ff72cb59 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 3c78e0035f 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 47cfad71e8 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 0a9e78770b 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new e7be46809a 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 5a7b436655 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 34ebeafecb 104: onsuccess: #1700: 1: Success after gcc: 2 commits new c129d76ce2 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 8ed28723d6 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 752eb09ca9 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new afe78ff989 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 9c70b6b4b3 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 0625e7c231 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new f633070d23 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 8afd4c566e 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new f6db764afe 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new e2e7055e22 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 155f4fa155 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 5a985a6970 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 98fa9d3762 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 1d71eb09c4 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 8a0651a2d3 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 2393a57e48 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 0c5f74379a 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 0be8a0cc5b 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 875a31236b 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 4796b61aaa 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new b3e030f4c6 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new f34c073621 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new 6f6648ee9b 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new dec7d57c32 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 5543694ab2 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 5df42490d9 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 2f6abfc435 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 41bcd54ea5 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 1969e74f31 133: onsuccess: #1733: 1: Success after binutils: 3 commits new f930083bf9 134: onsuccess: #1736: 1: Success after binutils: 3 commits new c9e14df03f 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 969181cf97 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new fd32604a23 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 5cc3693c46 138: onsuccess: #1749: 1: Success after binutils: 5 commits new ed57c9d81d 139: onsuccess: #1753: 1: Success after binutils: 5 commits new dfa2ba3835 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 6c5ff0e01f 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new faa54fd011 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 180b7bff79 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 77643e47f9 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new ee506ab77c 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new 2f2ceb67ef 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new d4ea277c1f 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new d20dcf0443 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 480886c62a 149: onsuccess: #1769: 1: Success after gcc: 3 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 (e5c6754a7b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (48 [...] 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 1656 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 50588 -> 50516 bytes 04-build_abe-gcc/console.log.xz | Bin 234452 -> 232040 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3812 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2672 -> 2736 bytes 07-check_regression/console.log.xz | Bin 5980 -> 4864 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 6 - 07-check_regression/mail-body.txt | 48 +- 07-check_regression/results.compare | 43 +- 07-check_regression/results.compare2 | 225 +- 07-check_regression/results.regressions | 40 - 08-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 50 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 40 - sumfiles/g++.log.xz | Bin 2784064 -> 2780096 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 2379844 -> 2368616 bytes sumfiles/gcc.sum | 4834 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 908216 -> 906480 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2176 -> 2160 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204640 -> 204720 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2528 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465660 -> 463488 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2627 insertions(+), 2942 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_cross_check_gcc/master-aarch64 updated (fb658c74c7 -> eb7339a4a8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards fb658c74c7 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 390c059681 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 9aa4792449 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 1c2a30e258 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards b43fe059a4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 94a9d6a9b1 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 86f89b4ec1 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 5d2328e294 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards b1a9105ac5 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 49e9d65eab 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 99758448bc 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 751f3a74e6 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards c77928f0df 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 524294315c 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 9b2a17e50b 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 0605fdfd5e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 1668cdf17a 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 1e4867d1ac 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 65e4c44109 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 44f7516f80 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 7221331945 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 6c464ec6a2 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 94fb3166c9 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 2819cae131 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 2460b23319 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 30e7569d3b 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 1e7005c8b2 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards bb9c4a82ef 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards ace728951b 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d7a13cce22 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 7296c59047 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 944cdeb5f1 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards c3eefb6e1d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards abf19fe719 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 37e09446ca 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards f131bfe70b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 4120842d02 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 79e66bf016 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 45f514c7f0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 0ae1aad08a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 121f21be3e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards bd511456de 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 8842e5eb0c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 82d2ffd300 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards a9dee08102 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 8f2bc2d27a 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 7185f03e83 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 72d7e0a86e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards e8ed7d53f6 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 819069775c 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 1fd337ac29 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 92926633a6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4953c55cbd 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 8d4d7117d4 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 9dec19115d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 8ba757f68d 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 7f219aa211 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 40e11a73b9 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 45964ae13e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards a013803e09 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards d05520b230 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 852f1e375d 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards e7fc646075 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 82d4a13218 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards d5eb8ee89b 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 4be6b45285 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards f0072d988e 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 4252114308 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d16182f3a8 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 3630bccb34 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 088082f6cf 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0b7ee2e242 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 596f51bf5f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 8f93137f46 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9868bae5de 75: onsuccess: 1: Successful build after linux: 44 commits discards 153975890e 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards de79be4b4e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fc2e250e01 72: onsuccess: 1: Successful build after linux: 12 commits discards 688d19f492 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards d7ebc80d6b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 08cef7c0ef 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 11855e3215 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bc4af4adb1 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 7db092a812 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 5f29b3ba2e 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8efc7d8983 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3b2d3d67d0 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards cb00a936e3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 42ad138b43 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 9d7d425595 60: onsuccess: 1: Successful build after glibc: 2 commits discards 52ce0615d4 59: onsuccess: 1: Successful build after binutils: 2 commits discards aa89bcc27e 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 6cb86e6167 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6c7975bdd1 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5cba90cf6 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards fe552c13fa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards f1d776dae8 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7a9af80545 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 38b471d422 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fcec6f040d 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5ba68a9a2c 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 340c427316 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 48f2206bbe 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e502a4213b 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5673f96610 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 884ef541cd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new fea7f4cc50 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2ec0641d1a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new cd764bfc0b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ea4ba54f2f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 08ed925a2b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new cf66ffc8b0 59: onsuccess: 1: Successful build after binutils: 2 commits new e349a63a86 60: onsuccess: 1: Successful build after glibc: 2 commits new 79815bb43f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new d763481550 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 164d95d30b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new b408306f95 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 87ab95e678 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8a51a66269 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 8cf5b5f510 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new d012719d99 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7d3089ac2e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 944a208bcf 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new cbb626bd1d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 9ed50c670e 72: onsuccess: 1: Successful build after linux: 12 commits new 833b96fa17 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c43b276759 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b9b524b84c 75: onsuccess: 1: Successful build after linux: 44 commits new d6aca2f47d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d0f83ac534 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 0dfdb94337 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 504de0a5ef 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 284c5e82ce 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1a4abe82a5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 7753741514 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new dbd5806d13 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 3bae85608b 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a7f4188a9f 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new ae6a318a53 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 176499303d 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 1874b03c00 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 6f284d9e77 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 8071ac88cf 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 7568a0ef46 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new e1dd9bcd5c 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a6a106682d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 5315b08ee1 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 430fe56d7b 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 007eb97a94 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new a5fb4df8ea 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new b53a59fc91 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 2d0c22adca 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new e4ac5a1057 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new eb695b2f24 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 3ca01c611f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 96b6900835 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new bac7e0a175 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 3ad84f798a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 49ead43d56 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new dd71f1dd68 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 6c768c41a6 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 89a2c0cfa3 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new d288051c76 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 429c75f84a 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new d8b11c088a 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 7eeeb50521 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new e79d998d25 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 4826b13519 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 360e13b317 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 8fa47ff213 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new a6190937e9 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6aa4b0c4a7 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new e16a53816e 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new acda6ae050 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new d1b9630fd5 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 630493ff38 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new bef18d16d2 124: onsuccess: #2159: 1: Success after linux: 23 commits new f6df9c3ca4 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 66062a554e 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 75185f98fe 127: onsuccess: #2162: 1: Success after gcc: 9 commits new bdcb0c95fb 128: onsuccess: #2163: 1: Success after linux: 23 commits new 48179d035d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 2ede3446c9 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 6c2d745882 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new e0da216d0a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 1ffa4d04b3 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new b80a5d451f 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new daf83f037a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 004503ef06 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new cd0672b5e3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5c67743b47 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new a53fcf24bd 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new d7f59292e3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ff73a233e8 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 82ca4ef3f1 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 5c729a4148 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new bc88c36c91 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 92922a2be4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 6ed5438594 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new ce48f072de 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 6e487becd9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 697ed8a9f4 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new eb7339a4a8 150: onsuccess: #2185: 1: Success after gcc: 3 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 (fb658c74c7) \ 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 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30188 -> 30124 bytes 04-build_abe-stage1/console.log.xz | Bin 72476 -> 72704 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 241060 -> 240396 bytes 08-build_abe-stage2/console.log.xz | Bin 203040 -> 203216 bytes 09-build_abe-gdb/console.log.xz | Bin 37380 -> 37508 bytes 10-build_abe-qemu/console.log.xz | Bin 31740 -> 32036 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2524 -> 2856 bytes 13-check_regression/console.log.xz | Bin 5988 -> 9344 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 130 + 13-check_regression/mail-body.txt | 101 + 13-check_regression/results.compare | 149 +- 13-check_regression/results.compare2 | 763 ++++- 13-check_regression/results.regressions | 101 + 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 101 + sumfiles/g++.log.xz | Bin 3438500 -> 3426616 bytes sumfiles/g++.sum | 90 +- sumfiles/gcc.log.xz | Bin 3011448 -> 3032264 bytes sumfiles/gcc.sum | 5536 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1033388 -> 1038696 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2300 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202616 -> 202728 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428988 -> 427560 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 4409 insertions(+), 2776 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create 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_kernel/llvm-release-aarch64-next-allyesconfig updated (97f059f1bf -> 664a95e4b3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from 97f059f1bf 19: onsuccess: #416: all: Success after binutils/llvm/linux/ [...] new 664a95e4b3 20: onsuccess: #417: 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 1720 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30672 -> 30076 bytes 04-build_kernel_llvm/console.log.xz | Bin 65084 -> 64988 bytes 05-build_abe-qemu/console.log.xz | Bin 32172 -> 31776 bytes 06-build_linux/console.log.xz | Bin 3160 -> 3100 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4440 -> 4400 bytes 08-check_regression/mail-body.txt | 6 ++++-- 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 | 8 +++++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 33 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-norov-allmodconfig updated (92237214a6 -> 6b7004261a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-norov-allmodconfig in repository toolchain/ci/base-artifacts. from 92237214a6 13: onsuccess: #50: boot: Success after linux: 4 commits new 6b7004261a 14: onsuccess: #51: boot: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1712 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30740 -> 30048 bytes 04-build_abe-stage1/console.log.xz | Bin 68852 -> 68632 bytes 05-build_abe-qemu/console.log.xz | Bin 31264 -> 31312 bytes 06-build_linux/console.log.xz | Bin 3312 -> 3412 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 2824 -> 4176 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 | 31 +++++++++++++++++-------------- 17 files changed, 25 insertions(+), 22 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_bootstrap/master-arm-bootstrap_profiled_lto updated (3c912694c6 -> 931fac20a0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. from 3c912694c6 49: onsuccess: #445: 2: Success after binutils/gcc: 119 commits new 931fac20a0 50: onsuccess: #446: 2: Success after binutils/gcc: 49 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1672 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50372 -> 50680 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 947792 -> 953600 bytes 06-check_regression/console.log.xz | Bin 3024 -> 3100 bytes 06-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 13 files changed, 18 insertions(+), 18 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-allmodconfig updated (064812760e -> db93c5bdc6)

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-allmodconfig in repository toolchain/ci/base-artifacts. from 064812760e 21: onsuccess: #486: 36: Success after llvm: 12 commits new db93c5bdc6 22: onsuccess: #487: 23149: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1692 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30340 -> 29924 bytes 04-build_kernel_llvm/console.log.xz | Bin 62280 -> 64684 bytes 05-build_abe-qemu/console.log.xz | Bin 30288 -> 31348 bytes 06-build_linux/console.log.xz | Bin 4552 -> 5668 bytes 08-check_regression/console.log.xz | Bin 2996 -> 4544 bytes 08-check_regression/mail-body.txt | 9 +-------- 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 | 11 ++--------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 2 +- 18 files changed, 28 insertions(+), 39 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_bootstrap/release-arm-bootstrap_lto updated (2939dd3eb4 -> 536518efaa)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_lto in repository toolchain/ci/base-artifacts. from 2939dd3eb4 17: onsuccess: #135: 2: Success after binutils/gcc: 8 commits new 536518efaa 18: onsuccess: #136: 2: Success after binutils/gcc: 14 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1860 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2700 bytes 04-build_abe-binutils/console.log.xz | Bin 50932 -> 52120 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 467268 -> 469280 bytes 06-check_regression/console.log.xz | Bin 2796 -> 2888 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (153ca019b77 -> ca01d252691)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 153ca019b77 OpenACC: Fix struct-component-kind-1.c test new ca01d252691 or1k: Only define TARGET_HAVE_TLS when HAVE_AS_TLS 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: gcc/config/or1k/or1k.cc | 2 ++ 1 file changed, 2 insertions(+) -- 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