Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (cd1d3dc030 -> 62500c5e7d)

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 cd1d3dc030 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards b38f38feb1 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards 8eeae39a6e 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 5b75b5e95a 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 9addbca9f4 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards e32fbe7d30 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 74931e38b8 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards c518e17024 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 86d244cab1 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 79a2917a44 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 7641615ead 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards d0be6cbb7c 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 876e6dd44f 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 30469fc0af 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 20bb569de6 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 9b810befcd 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 3b27786536 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 27de09ba6a 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 71ccc26b21 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 9df2ff7ec0 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 0d6b225315 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 7dd6764f31 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 6f0f717e8f 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards e1875267f0 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 73323a6bec 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 7d0e08a1e8 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 070971a1e6 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards ac7747a0e4 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 35131f089b 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards a455c61aae 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 7542b75b8b 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 41a5da5b8f 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 2d23b9b6ec 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 92871d6935 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 85f675bab3 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 41177f5584 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards e0ef7e239c 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 069c8ee768 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards e1bbe81240 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards c225f56304 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 81da751eec 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards dc3d305181 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 0020811527 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 969cb91618 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 23268d734f 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards d1416562e4 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 8d5f8a1a7c 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards e5418781c2 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 407944ff3b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards bb96e74bb6 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards f2676eb0e5 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards b7178a85f7 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 830edb590b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 408c617c0b 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards e03eda8831 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 0bde21774c 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 93bc58de6e 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards b5c38e9fe6 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards f9b99acf71 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 468dc8ba47 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards da6efb947f 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards c4e5accfdd 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 58bae676cb 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 69620bd936 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 5090dfc09a 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards b880738527 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards ce14c6d37d 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards e7ddb66b4b 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards b506e55a84 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 272d2abea3 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 631c0f8033 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 21a3236393 85: onsuccess: 7: Success after gcc: 9 commits discards 8e02269604 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards de7491ac6f 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 5d13c8b1f7 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards f889fcc440 81: onsuccess: 7: Successful build after gcc: 2 commits discards 42e5a73443 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards f9a9713737 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fb3ae27480 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2f0cdb48e0 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards efbda1da5a 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6a7abccaa0 75: onsuccess: 7: Successful build after linux: 44 commits discards ba31b3fbd8 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 8ba2f9a9e7 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a50613bde8 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 14dfdb8349 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 6619fa908a 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 992541897e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards be37b6d6c6 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e4240a704d 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 264e818ea8 66: onsuccess: 7: Successful build after gcc: 3 commits discards 77b338c766 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 94f29c0952 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cd2183cb63 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 801c8879cf 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards d8159120b0 61: onsuccess: 4: Successful build after gcc: 15 commits discards 2cdd019629 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 8f8ac02ec8 59: force: 7: Successful build after gcc: 2 commits discards b4b12de00d 58: onsuccess: 7: Successful build after glibc: 2 commits discards 1af97da021 57: onsuccess: 7: Successful build after gcc: 7 commits discards 67f35bb11d 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 576c1c9c17 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new eab2724fa4 57: onsuccess: 7: Successful build after gcc: 7 commits new 1fa6c48b15 58: onsuccess: 7: Successful build after glibc: 2 commits new 890601dff0 59: force: 7: Successful build after gcc: 2 commits new 7e3efeac3e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new c55016b2b2 61: onsuccess: 4: Successful build after gcc: 15 commits new f7d70f123f 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new c8135444c7 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new c0f9c717ae 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0d3a956bcc 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5fc9dea3a2 66: onsuccess: 7: Successful build after gcc: 3 commits new 56ea0c9256 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d35ad127b5 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7dea929520 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 4365fb6025 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 20b0bb2ba0 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 79785617eb 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new dbbc997636 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b0c7dda274 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new b22d5075c1 75: onsuccess: 7: Successful build after linux: 44 commits new ad49c5513e 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6a78b37dd4 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 2dc766b3f9 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f72411053f 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d791f41a97 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new ece4440a63 81: onsuccess: 7: Successful build after gcc: 2 commits new d1c9d16cdf 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 4bbd04dba1 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 7eadf130f5 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5f088b2f76 85: onsuccess: 7: Success after gcc: 9 commits new b30366d39e 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 725171dc7c 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new bc0fc2c05a 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 248fa2fd38 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new c489ccf389 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a442f3c307 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 3e3485946a 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 350d95e53d 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 924d7814a0 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new ffc8312ff7 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 1b2504a505 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new b10d4a46a7 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 038d56c861 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 8a1337576e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 2f8579b021 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 899321ab73 101: onsuccess: #1609: 7: Success after binutils: 78 commits new b29528a9a0 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new bd03144934 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 5b220d9acd 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 4a9eca8f03 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 15f19f7ca4 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 2611b14f07 107: onsuccess: #1618: 7: Success after gcc: 2 commits new aa8ae8713b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 7147ac9387 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new fd8749cfc6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 9787fcd32b 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 1752be0872 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new d433dc328d 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 7ebad9e5a0 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 53cc9736f9 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 72756deafd 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 4f7f5c7519 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new ca70ea8152 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 7d6730bc71 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new a183dcbf2f 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 5328c24681 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 615f1c2b7d 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 25804e2fae 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 6a00317488 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 18dfdd1849 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new d6ddb65d76 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 17242707d2 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 96c6f8a9ae 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new d4019cb437 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new f7fb9fb100 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 78e9a9c5b4 131: onsuccess: #1644: 7: Success after gcc: 10 commits new e0e6131ecd 132: onsuccess: #1645: 7: Success after linux: 23 commits new 5c43ced46d 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new b38124b3a9 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new c5f474187a 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 06a35458d0 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 5df0c93afb 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new bd1bee6f64 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 9778cc8250 139: onsuccess: #1654: 1: Success after gcc: 11 commits new afc4a0a5ed 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new d88fb74fca 141: onsuccess: #1656: 7: Success after gcc: 7 commits new a3172f8d91 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 4a3f193734 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 5dbfd5d4b9 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 8acb112f1a 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new f7529f78c9 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new eb6a7187d3 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new d65b93d040 148: onsuccess: #1663: 7: Success after glibc: 2 commits new be0f9ac6b2 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 788e73fe1a 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new ac651e341f 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 705656d83e 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 73136f8f8b 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new d5928e3d01 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new bae22b3612 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new c1b4f5b55d 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 62500c5e7d 157: onsuccess: #1672: 7: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (cd1d3dc030) \ 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 1684 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 29880 -> 29912 bytes 05-build_abe-stage1/console.log.xz | Bin 91272 -> 90732 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8552 -> 8616 bytes 08-build_abe-glibc/console.log.xz | Bin 233688 -> 234396 bytes 09-build_abe-stage2/console.log.xz | Bin 224980 -> 223320 bytes 10-build_abe-gdb/console.log.xz | Bin 37200 -> 37152 bytes 11-build_abe-qemu/console.log.xz | Bin 31480 -> 31992 bytes 12-check_regression/console.log.xz | Bin 3236 -> 3344 bytes 13-update_baseline/console.log | 42 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++----------- 18 files changed, 39 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_kernel/gnu-master-arm-stable-allmodconfig updated (e5ca1f735 -> 56e3f379c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from e5ca1f735 15: onsuccess: #479: 33: Success after binutils/gcc/linux/qem [...] new 56e3f379c 16: onsuccess: #480: 33: Success after binutils/gcc/linux/qem [...] 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 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30008 -> 29960 bytes 04-build_abe-stage1/console.log.xz | Bin 91940 -> 90684 bytes 05-build_abe-qemu/console.log.xz | Bin 31076 -> 31268 bytes 06-build_linux/console.log.xz | Bin 4860 -> 4048 bytes 08-check_regression/console.log.xz | Bin 4376 -> 4416 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 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (423936e93 -> e1678080b)

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 423936e93 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards af6c05a11 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 3812cd38f 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g1 [...] discards e40bdfe0f 152: force: #1605: 7: Success after gcc: 9 commits discards fc6628547 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-20 [...] discards e2d8a668b 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/gl [...] discards bac22a60a 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 commits discards 8c0b41f62 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/gd [...] discards e7909c272 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/gd [...] discards 3d201ad9d 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/gd [...] discards 82e8f8476 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 commits discards 89704cab9 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 8f28a7ca3 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/gl [...] discards 31e8a1ce4 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/gd [...] discards 9f8631e8a 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 98c239a86 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 96609aa3e 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/gl [...] discards 1f1b0bc81 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/gd [...] discards 2e4a6d213 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards c4f3b66a3 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 commits discards 5ecd77450 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/gd [...] discards 9ef655f5c 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/gd [...] discards 87f023a39 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 commits discards bbdc87fec 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 commits discards dc3d1a6be 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/gd [...] discards fd962234d 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 3a1994ae5 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-283 [...] discards f14aeeae8 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 2d7ea5129 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 6c125fd27 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 0b4b10c64 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards b77ec3649 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 06c577dbe 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/gd [...] discards 06ab98895 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/gl [...] discards 6e4225726 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/gl [...] discards fbff942e6 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/gd [...] discards d82968013 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/gd [...] discards c8a2f5365 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 48c8d3488 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qemu [...] discards 8d081a8a3 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/gl [...] discards b8e5479be 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 commits discards 66ad76d03 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: 1 [...] discards 905eab287 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/gd [...] discards e873a9f42 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] discards 5d142520f 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] discards f63a8679d 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards c2edbbd46 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 2e8856c59 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] discards 322bd49e7 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] discards f601cc4e3 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] discards a13c8f537 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 4b3c99290 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] discards b5ace78c4 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 389c86035 102: force: #1551: 1: Failure after gcc: 306 commits discards 3c74b1822 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 41c77e18b 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 08b70d3af 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards d6085ab9c 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards b1819ce15 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 9413415a8 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7749c9aed 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards f279e72ef 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards dda8c4301 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 8ad5c2f49 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 255b0ecbc 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 3e62c0be7 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 3069a60e9 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 095984ba7 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards a1b1014bb 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 1785134ed 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards aa89750b4 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards e5b73c19d 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 73f0638b1 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1a61f1b87 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards ba5ab8179 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9814309a8 80: onsuccess: 7: Successful build after linux: 44 commits discards abfa21695 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards a791f70b2 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 1fa90b445 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards becd206a2 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 645c9be9d 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 4ec0a85c2 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 09c8cc3f2 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8e8fe7a9e 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f9a5fc79a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7ba2b5333 70: onsuccess: 7: Successful build after gcc: 4 commits discards b4cac72e4 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d868add1a 68: onsuccess: 7: Successful build after linux: 6 commits discards ecb5e08d6 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards a9fb9ee17 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards a82f34d42 65: onsuccess: 7: Successful build after binutils: 3 commits discards 6f90d0b91 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards cd6b4a97d 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards e628353ae 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 93337c3b2 61: onsuccess: 4: Successful build after gcc: 5 commits discards f1dfcadfa 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards a1e74e687 59: force: 7: Successful build after gcc: 3 commits discards 442a1a258 58: onsuccess: 7: Successful build after glibc: 2 commits discards 0fd3b342f 57: onsuccess: 7: Successful build after gcc: 7 commits discards ba5a02ea2 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4814e8ebe 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 859f75fce 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 10f9ca0f8 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new eb4951080 57: onsuccess: 7: Successful build after gcc: 7 commits new 275cb5418 58: onsuccess: 7: Successful build after glibc: 2 commits new 1e3ad951a 59: force: 7: Successful build after gcc: 3 commits new 590076b56 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 30c4e2008 61: onsuccess: 4: Successful build after gcc: 5 commits new b7e879c33 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 95414b9af 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 8ba37c041 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new eec66eb31 65: onsuccess: 7: Successful build after binutils: 3 commits new 36925d16c 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new e570d0481 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new b155c5251 68: onsuccess: 7: Successful build after linux: 6 commits new 2a0a3ca61 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 87384df03 70: onsuccess: 7: Successful build after gcc: 4 commits new c52da3258 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e1030ad63 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 919f3f9e0 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3b50dc9a0 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 6693e364d 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new d51336df3 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 627bd2cb1 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 81087a271 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new db5a676a4 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 5bba1c3ab 80: onsuccess: 7: Successful build after linux: 44 commits new 3b05cd058 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 23eea4fe6 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 6b2f3ce88 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new da36fd0f2 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 4b501278c 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 789fd3ab0 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 108e84529 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new df5c0eb51 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 7ff1e6fc1 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 56c5435bb 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 5862e0aa4 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 9f40ca6e7 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 4ce12102b 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 42eca8ab1 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 97dc99a6b 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new bb9bc8d74 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 2522be9a6 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new b17290c5d 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new 81568c2aa 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new becffb9fa 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new a1c093059 101: onsuccess: #1547: 7: Success after binutils: 82 commits new da7b5eeeb 102: force: #1551: 1: Failure after gcc: 306 commits new 9565d4eb5 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 1cf9fd184 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] new b6107cb3b 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] new 4669ce380 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] new 7fb65d427 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] new 68e063351 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] new 9a3bf4dda 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 802d79d64 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 8a0135f2e 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] new 44dd796de 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...] new 526c37411 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/gd [...] new 72e11ff6c 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: 1 [...] new abbb27863 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 commits new 06e108742 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/gl [...] new 0fe2c8784 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qemu [...] new 358a01236 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 421383632 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/gd [...] new ebfd7d562 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/gd [...] new c2495dcf9 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/gl [...] new eede4f450 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/gl [...] new 1095633eb 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/gd [...] new 17bdc2df6 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 48fd17a88 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new df9eb5603 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new a8a8ed07d 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 4e5882a29 128: onsuccess: #1579: 7: Success after linux: 12 commits new 77d075adb 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-283 [...] new 827f0eae7 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 5bbd278bf 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/gd [...] new f43923533 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 commits new 0bfd97c8b 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 commits new 1759e5278 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/gd [...] new fc940b865 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/gd [...] new 275c432c8 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 commits new 0473e0210 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 55b09f58d 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/gd [...] new 45984f2da 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/gl [...] new 61fba2c21 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new cb8f97a84 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new eb3a67e6a 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/gd [...] new c9a4b182d 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/gl [...] new 1b6776775 144: onsuccess: #1595: 7: Success after glibc: 2 commits new d52113ed8 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 commits new d9fa1cf58 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/gd [...] new 5465ab80c 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/gd [...] new 4aec85c89 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/gd [...] new 943777e2d 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 commits new db5cc9367 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/gl [...] new e3b0ef873 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-20 [...] new 74921c1f9 152: force: #1605: 7: Success after gcc: 9 commits new c6f3985b7 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g1 [...] new 828c57eb4 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 6bfcf4b87 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new e1678080b 156: onsuccess: #1609: 7: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (423936e93) \ 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 1692 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30208 -> 30152 bytes 05-build_abe-stage1/console.log.xz | Bin 72628 -> 72380 bytes 07-build_abe-linux/console.log.xz | Bin 8548 -> 8596 bytes 08-build_abe-glibc/console.log.xz | Bin 239352 -> 240064 bytes 09-build_abe-stage2/console.log.xz | Bin 202836 -> 203400 bytes 10-build_abe-gdb/console.log.xz | Bin 37392 -> 37280 bytes 11-build_abe-qemu/console.log.xz | Bin 31872 -> 32240 bytes 12-check_regression/console.log.xz | Bin 4180 -> 3376 bytes 12-check_regression/mail-body.txt | 12 ++++++- 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 14 ++++++-- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++------- 18 files changed, 73 insertions(+), 53 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-aarch64-bootstrap_ubsan updated (10b86458e -> 83f4a0c3d)

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_ubsan in repository toolchain/ci/base-artifacts. from 10b86458e 49: onsuccess: #475: 2: Success after binutils/gcc: 121 commits new 83f4a0c3d 50: onsuccess: #476: 2: Success after binutils/gcc: 37 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 1684 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2700 bytes 04-build_abe-binutils/console.log.xz | Bin 37652 -> 38164 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 325504 -> 328440 bytes 06-check_regression/console.log.xz | Bin 3164 -> 3056 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_gcc_bootstrap/master-arm-bootstrap_lto updated (265368c35 -> c7b9e5fca)

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_lto in repository toolchain/ci/base-artifacts. from 265368c35 51: onsuccess: #460: 2: Success after binutils/gcc: 126 commits new c7b9e5fca 52: onsuccess: #461: 2: Success after binutils/gcc: 32 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2700 bytes 04-build_abe-binutils/console.log.xz | Bin 51772 -> 50568 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 472776 -> 473280 bytes 06-check_regression/console.log.xz | Bin 3180 -> 3044 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_gcc_check/master-aarch64 updated (6caed188f -> 23d0794c0)

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 6caed188f 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards 0dae79590 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-20 [...] discards 822c4c6ca 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards 074d685fc 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards e53809ef2 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 781e8ebce 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards 64fd7314b 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards 538eebe76 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 78af0c171 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards e0ba90ac7 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 216a0e86a 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards ba6992f4a 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 503f45b7a 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards ea84e61d0 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards c12104171 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards bfa63b594 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 6098c5b2b 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards efbbadb89 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 303f121f5 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-20 [...] discards 82254f8f1 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 7e89f65b5 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-283 [...] discards 79842cb0d 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-283 [...] discards ce19c7ab4 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-20 [...] discards 3b43a874a 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-283 [...] discards 988ecd6e4 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 5246064da 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards a9b4ddd41 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards f0105d202 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 7950f191a 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards b2d503b2e 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 9e06d6620 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards ef98d3ec8 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards ce47f8544 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards c056e228f 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards ac487f960 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 3257135e8 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards e4df43a81 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards d0ad41dc8 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 979d88fb2 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 5929b8e85 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 5240a32e1 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards eb432b7b1 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 0825d5d13 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards d744c69b6 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 67e8fbc62 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 2eb552825 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 1708f28f2 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 095b33ff5 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-270 [...] discards 964696e49 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 4b861ab01 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards c95f13ae5 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 88da88779 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 1adee3c20 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards c58a6d256 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-2393 [...] discards bffcffa28 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-2392 [...] discards b278f546a 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards a414d5265 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-2390 [...] discards 201c177a5 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards d6034b53c 91: onsuccess: 1: Success after gcc: Daily bump. discards 6bb2cff44 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 31f3ed4f7 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 4f9f4dcd9 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards a14c1bb85 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards f9a5c6104 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 389752f0c 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 2ab8809d1 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 8b2168e11 83: onsuccess: 1: Success after gcc: 8 commits discards 769b232e2 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 2cd170aa1 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards c99a3c547 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 0711d02b2 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 30359863b 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 0aa9cf1d4 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards c141be188 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 0a8eaa4d6 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 15014f4ce 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 6b6c96970 73: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] discards 90eb8b79c 72: onsuccess: 1: Successful build after gcc: 2 commits discards e47adb911 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards ebc2cd46b 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards d48f49476 69: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards b890183fe 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards eff5b649f 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 09bd34141 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards ad9463582 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards c3eb43121 64: onsuccess: 1: Successful build after gcc: 5 commits discards ca61e65cd 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 7cd405d27 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards def61cd74 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 831e61521 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 3af83067d 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards b9af89f19 58: onsuccess: 1: Successful build after binutils: 2 commits discards 6c94a3424 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 1ebb543b1 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 16f6f9ca0 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 924d7077a 54: onsuccess: 1: Successful build after gcc: 7 commits discards 326732908 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 4110966e2 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 4108636b9 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards c63461851 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards e9e23214e 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 6e9d8c7a5 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new f51be06c0 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new a074a7153 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 3ac79c475 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 269c2f4ed 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 49597b429 54: onsuccess: 1: Successful build after gcc: 7 commits new 0d76fc310 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 6381a0621 56: onsuccess: 1: Successful build after gcc: Daily bump. new ea47f5850 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 5b3aded9f 58: onsuccess: 1: Successful build after binutils: 2 commits new 848b776dd 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 5a48b9b7e 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new b65dca503 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 4ae1432a3 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new a6da97dba 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 261d211d1 64: onsuccess: 1: Successful build after gcc: 5 commits new 1b999fe8a 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 4fa94bc4b 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new eb5565ce5 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new c8caff147 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new b2db7d8fa 69: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 618dc836d 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 0e57a9f86 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new cbfb54e10 72: onsuccess: 1: Successful build after gcc: 2 commits new a89c4d3e9 73: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] new b3a0190cf 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 503df3266 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 69b4f1797 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 70ce0f878 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 2dac472d3 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 12819684e 79: onsuccess: 1: Successful build after gcc: Daily bump. new 16db7a01c 80: onsuccess: 1: Success after binutils/gcc: 14 commits new adcb76d06 81: onsuccess: 1: Success after binutils/gcc: 27 commits new f0fe2e33d 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 264d67e3c 83: onsuccess: 1: Success after gcc: 8 commits new edbe7e1ad 84: onsuccess: 1: Success after binutils/gcc: 9 commits new a33e5ba52 85: onsuccess: 1: Success after binutils/gcc: 9 commits new f687fab29 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 6efdd2ef6 87: onsuccess: 1: Success after binutils/gcc: 4 commits new d99044db5 88: onsuccess: 1: Success after binutils/gcc: 16 commits new d9fd8e59c 89: onsuccess: 1: Success after binutils/gcc: 9 commits new e567ae1e4 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 041e94007 91: onsuccess: 1: Success after gcc: Daily bump. new 751aa035e 92: onsuccess: #1965: 1: Success after gcc: 2 commits new eae3a339b 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-2390 [...] new 4f175d793 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 5f107a24f 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-2392 [...] new 2d2055edb 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-2393 [...] new 370912ab6 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new dc6c14bc6 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 802a3fe7f 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 9de4a7dbe 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new c3963eb0f 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new e486e210f 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-270 [...] new d5fdbc10d 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 74f7dea19 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 92a08dd24 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 4a04e19c9 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 2ac9cf313 107: onsuccess: #2024: 1: Success after gcc: 3 commits new e310b4bc7 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new d5bc63710 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 61caa4302 110: onsuccess: #2027: 1: Success after gcc: 5 commits new bbd82c684 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new aec557560 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 668b77a91 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new dd124b118 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 8f67ef8e2 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 5ac23065f 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new af5807a56 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 874a404d8 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new d3e98c336 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 344313282 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new b2cb8c78f 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 805a7fd6a 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new e88a2a76d 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 17b1b7ea5 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 889f5cc46 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new bb6da816e 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-283 [...] new c0ace2065 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-20 [...] new 01f22092f 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-283 [...] new 5eb53d4d5 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-283 [...] new b75090b9d 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 2c033b18c 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-20 [...] new e91cf52c8 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 383e5df8a 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 4d7a7643d 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new b00e3abdb 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new c09b6740f 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 89a1631b0 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 865e3b195 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 1651adac3 139: onsuccess: #2067: 1: Success after binutils: 2 commits new bef5fea6c 140: onsuccess: #2070: 1: Success after binutils: 4 commits new f9f30663d 141: onsuccess: #2073: 1: Success after binutils: 3 commits new a7a9f9208 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new f3c03063d 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 3890a3df5 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new 0a739b7ee 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new fe5c2f920 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new d7d8b9784 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new f864cb557 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-20 [...] new 05db7bd2e 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 23d0794c0 150: onsuccess: #2085: 1: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (6caed188f) \ 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 1736 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 38092 -> 37688 bytes 04-build_abe-gcc/console.log.xz | Bin 214084 -> 212112 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2792 -> 2800 bytes 07-check_regression/console.log.xz | Bin 4948 -> 5096 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 48 + 07-check_regression/results.compare | 41 +- 07-check_regression/results.compare2 | 61 +- 07-check_regression/results.regressions | 48 + 08-update_baseline/console.log | 40 +- 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 | 48 + sumfiles/g++.log.xz | Bin 3580332 -> 3564160 bytes sumfiles/g++.sum | 152 +- sumfiles/gcc.log.xz | Bin 3113216 -> 3090760 bytes sumfiles/gcc.sum | 4578 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041932 -> 1038120 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207708 -> 207444 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2540 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 449568 -> 452656 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2700 insertions(+), 2472 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allnoconfig updated (059792bee -> de5d6d3e7)

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-norov-allnoconfig in repository toolchain/ci/base-artifacts. from 059792bee 12: onsuccess: #49: boot: Success after binutils/llvm/linux/q [...] new de5d6d3e7 13: onsuccess: #50: boot: Success after binutils/llvm/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 1696 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 29992 -> 30084 bytes 04-build_kernel_llvm/console.log.xz | Bin 64772 -> 64232 bytes 05-build_abe-qemu/console.log.xz | Bin 31356 -> 31928 bytes 06-build_linux/console.log.xz | Bin 911896 -> 3444 bytes 08-check_regression/console.log.xz | Bin 4236 -> 4436 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (64bd0df6d -> 0e1991b6e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts. from 64bd0df6d 54: onsuccess: #468: 6: Success after binutils/gcc/linux/glib [...] new 0e1991b6e 55: onsuccess: #469: 6: Success after binutils/gcc/linux/glib [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1676 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 37584 -> 37696 bytes 05-build_abe-gcc/console.log.xz | Bin 213212 -> 214880 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8548 -> 8704 bytes 08-build_abe-glibc/console.log.xz | Bin 241800 -> 242548 bytes 09-build_abe-gdb/console.log.xz | Bin 38232 -> 37636 bytes 10-check_regression/console.log.xz | Bin 4460 -> 4368 bytes 11-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++------------------ 20 files changed, 28 insertions(+), 37 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_O3 updated (860202c228 -> 6646847a34)

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_O3 in repository toolchain/ci/base-artifacts. from 860202c228 51: onsuccess: #469: 2: Success after binutils/gcc: 121 commits new 6646847a34 52: onsuccess: #470: 2: Success after binutils/gcc: 37 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50316 -> 50588 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 461740 -> 462364 bytes 06-check_regression/console.log.xz | Bin 3116 -> 3044 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_gnu_native_check_gcc/release-arm updated (16e689e606 -> a702cfc6f7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/release-arm in repository toolchain/ci/base-artifacts. from 16e689e606 17: onsuccess: #181: 1: Success after binutils/gcc/gdb: 11 commits new a702cfc6f7 18: onsuccess: #182: 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 1676 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 51500 -> 53008 bytes 04-build_abe-gcc/console.log.xz | Bin 228896 -> 227956 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 232512 -> 232544 bytes 08-build_abe-gdb/console.log.xz | Bin 46140 -> 46228 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3812 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2892 -> 2376 bytes 11-check_regression/console.log.xz | Bin 5320 -> 6496 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 61 +- 12-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2848464 -> 2840696 bytes sumfiles/g++.sum | 136 +- sumfiles/gcc.log.xz | Bin 2496748 -> 2457500 bytes sumfiles/gcc.sum | 5334 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 930500 -> 936648 bytes sumfiles/gfortran.sum | 104 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 210628 -> 211672 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455692 -> 463196 bytes sumfiles/libstdc++.sum | 22 +- 38 files changed, 2925 insertions(+), 2839 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