Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1 updated (05baed3aaf -> d243721920)

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_O1 in repository toolchain/ci/base-artifacts. from 05baed3aaf 81: onsuccess: #475: 2: Success after binutils/gcc: 29 commits new d243721920 82: onsuccess: #476: 2: Success after binutils/gcc: 33 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 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 38532 -> 38112 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 273668 -> 273828 bytes 06-check_regression/console.log.xz | Bin 3068 -> 2992 bytes 07-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 24 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (52438f783d -> c9b0b5714c)

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 52438f783d 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] discards 2a70cbe300 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits discards c98fba67a3 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] discards c4ecf0d2c2 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] discards f1865190ad 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] discards 89fe415ad0 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] discards 6f6b614343 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] discards 207d08a790 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] discards b46c540dd4 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] discards 2c0e24d7d0 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] discards 7174e5449e 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] discards 4c7444e4f6 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards fd8e6f11da 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] discards fc9a339d3c 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] discards 38cfcb098e 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] discards 60f9b8185f 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards 9445ed8d45 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards b064ab2b09 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards 7624f675f1 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards a8815df1d6 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards 681e0bc3f0 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards e66a072cbb 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards 0065bafcb9 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards de719764c8 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards 636ddd827a 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards 45bee013be 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards c917fc1211 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 87d7728fec 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards ac13d04cb1 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards 4f9a87d41a 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards b582ba6826 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards df6876594a 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards 4ad4bc4512 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 3633711f65 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards b498ad877f 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards fcd740a0fd 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards a085ba80bd 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 1309554476 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards a8582cadab 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 62659190b1 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards d58fed4bac 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 8b23c8c592 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 43ec12d982 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards a76da806e9 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 0fc4802fc9 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards d615bfb83b 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards d27c3d7241 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 5cbf070d42 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 2279361c24 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards ed384d20f2 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 22e1c4708b 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 3407e22d05 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 48017a0288 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards cd74ae3384 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards d21894977a 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards ea39110ca9 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards ff5e8fab01 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards b7cc886df8 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 70267d4ce4 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 938771c38a 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 1e6e45f41c 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 12f474b84a 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 928b668c7c 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 578d9d9f28 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 2e75b95236 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 110ec7b604 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 72ee1050d4 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 6d7d3b9e7c 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards f2a6700f1c 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 9e1c42c53d 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 0625caec38 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards f5bf6c1a68 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 145a009538 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards e89918e4cf 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards ec01697bb2 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards fead261f36 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 97842c9f7b 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 84a745ecb2 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards d5adc2a044 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 936d756ef1 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards c8128c53bb 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 513d6c97ff 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 84285ae55a 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 9c8e1a455b 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards d00bf23f18 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards aa46a21ea7 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 00d2e3bdae 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 73bb9f206f 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 2f1a8b8d25 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards bbdfa6aed3 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards ee55efb88e 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 85e9243c28 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 0d3a41d838 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 80ba701961 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards ec23661b06 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 820d8b0552 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 15b514a489 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 7cba2853ca 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards f0a016d83a 85: onsuccess: 7: Success after gcc: 9 commits discards cbb486c704 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 505e4e83b7 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 7ba5b15ac3 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 399606f7e8 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 37364c0e0b 85: onsuccess: 7: Success after gcc: 9 commits new c3285ac4a6 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 0a01d827e1 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new a1e3a25b7d 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 6024aef74e 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 6eaec2b558 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 9708441e84 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a85b89f22b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 32b2c9a4fe 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new becea03a4f 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 40e0441b30 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 74129078d7 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new aa9c4b65c9 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 16f3cc2f4a 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 2cc038ab10 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 5ef0af239c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new c2edaf60fa 101: onsuccess: #1609: 7: Success after binutils: 78 commits new ffbb606489 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 532623e09a 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 44cc3d1aae 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new e95a4fc184 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 6ef96a511f 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 4f3b982962 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 4e09a71a71 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new e03899d7c1 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 76d4cb78a9 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 4994c45ab1 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new ee9bc8f1ad 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 38ebab3014 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 5bf344969d 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new d253302601 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 0ef2efe75b 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new b87d6ab434 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 764478114e 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 4bd23cc7d4 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 83b1097fa2 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 2aca55018e 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new ed471baf3e 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 862d7009c7 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new aa2d0a07e9 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 62c7a4551c 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 07ad1c8cb4 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 3394da4e20 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 7452547433 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 64a16ec9d2 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new ecd63b555c 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new b022dddf93 131: onsuccess: #1644: 7: Success after gcc: 10 commits new ca6a507716 132: onsuccess: #1645: 7: Success after linux: 23 commits new ab113ecaa1 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 9c0fb22021 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new ab0dbc252d 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new a0d6daf1fa 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 6055c63247 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 151e89e804 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 21b0406118 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 1c2dafca3b 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 0e433920a7 141: onsuccess: #1656: 7: Success after gcc: 7 commits new b432a1bb68 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 316a88cdba 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new e6c1be2c07 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 4fbf7549cf 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 76e939f806 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 9b6be465bf 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new e73c8bebb9 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 8d1ad6f7d4 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 3a8e905220 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 072a5f2472 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new f0c768b11c 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 05bd26111d 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new a596a4a688 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 66d9a40fd4 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 907cc03886 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 0795ca8ff6 157: onsuccess: #1672: 7: Success after gcc: 2 commits new d8454e404e 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 8c7f785a5f 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new 534dbf64c9 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new 8e47fd71b6 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new ca759ab937 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new d4d0479810 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new 02d9034039 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new fff96b1148 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new a877438829 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new bc898daf07 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 5023f49a07 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new 28f2884371 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] new 03e8c5c6c9 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] new b14f2b5f55 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] new e5430feee0 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 8e4703b3c2 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] new 60a86e4ec4 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] new f1b143ae71 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] new da608f32ab 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] new 3e6fd85e32 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] new cb03a425ed 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] new 8556b93ef9 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] new 07e32d5e83 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] new dabfed0453 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new c493b2aab9 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits new 7156f043eb 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new c9b0b5714c 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (52438f783d) \ 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 -> 1880 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30624 -> 30040 bytes 05-build_abe-stage1/console.log.xz | Bin 91764 -> 91028 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8440 -> 8704 bytes 08-build_abe-glibc/console.log.xz | Bin 233652 -> 234160 bytes 09-build_abe-stage2/console.log.xz | Bin 224288 -> 224172 bytes 10-build_abe-gdb/console.log.xz | Bin 37508 -> 37276 bytes 11-build_abe-qemu/console.log.xz | Bin 31456 -> 31372 bytes 12-check_regression/console.log.xz | Bin 4452 -> 4184 bytes 13-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++---------------- 21 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (383699d8f7 -> 41ad731891)

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 383699d8f7 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 63b884b89f 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 1279b0b5dc 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 70630e8a04 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 78639c79c9 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards ce5d84c863 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards c136c7c65f 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 2312dc145f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 86e84608b3 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards cdfec58809 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards e63bce3a3f 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 81a084d602 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 40e4aeca60 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 0bccd32dd0 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 5da6ebd265 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 759a212437 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 5b4b4334be 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 16330ac1c6 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards e4427e6412 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 73558e8f82 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards c9ef789a00 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 84dc18f124 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards c2111d5a5f 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards c4dbe88bb8 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards dbcb3b8553 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards def5c1755b 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards b28d28d89f 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 2318252cca 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards ec62d48000 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 5f679242e9 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 0a5d52e988 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 7dbb069571 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards a0c17159dc 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 7d6f442ff1 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 0226adada9 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 1be63980a3 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 79c2a1ad26 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 80f03bbe86 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards ab3c760ade 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 3e1c53b7d2 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 0108fece0d 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards de53bcfba2 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards db7b9122cd 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards dd8b6c596b 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 761dab0b2b 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 72bd900481 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards adef381f16 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 2c4602ec63 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 4f7464d68a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards bcbd399319 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 374526d474 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards d6bd09caae 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 750f48f612 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1032ebe30f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards ef08b86179 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 2f8aee780d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 483ec00c82 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 6d89a54beb 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 096c371683 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards a98b9ba295 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 33dd3fe765 124: onsuccess: #2159: 1: Success after linux: 23 commits discards cb3a6b1c3b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards fb938c5205 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 7fd826deca 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards a4fb6984c1 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 61cbd20406 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards d9b741c2f5 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards bbcac8ed52 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 11de982c42 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 24abb9333a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards b15cad8ee3 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 05fb58be8b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards de5bf05de3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards df0ae7ec05 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 5275b74533 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 995ab3bce7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards e146ac504b 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards e3477defbd 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 4c114ed50e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 4b0c5b0bc9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 4a3dc40ab2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 84acc47491 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards f5ad770f52 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards cc7b7b54ca 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards d267089fad 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 74e114f701 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards d6de3649e9 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 398e47cde0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 93c6d976e2 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards af3f0b2d96 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 328dba1666 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards f725cbec53 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 7255253583 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2680beba8f 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 2e4862b20f 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 070f78d0b4 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 5e527ba421 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards df0fc6e910 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards ec7c073945 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards caa700def0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards dc1b50e498 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a90f965286 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 622281ae0d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 0d6dd897c2 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new de8122ed78 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new faf110862e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new f530bc1b27 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 396a549163 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 6c64fdf441 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new a008552b98 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 645610f784 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 9666822c05 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new fe1f413555 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new ebea578df9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new d9d0bc449d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 5f8941e1a4 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d97a00965a 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new aecf401a8b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 67f6b52666 101: onsuccess: #2130: 1: Success after binutils: 81 commits new ddc99a5cc1 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new acacb42c1d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 7decdf432a 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 583849fc46 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new d8cd2b3794 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new fe36add65e 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new c22b7c891e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new b598817a14 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 2cac1aee19 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 934d518d55 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 55c71eccf5 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 9060659fb5 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 46cd96ed63 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 74adc05d7d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 0059bc65e1 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 564f0b32ad 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 242f3704a0 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b1d2246d78 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new f33c16fef9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 0d97d58a7c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 6758d2afa9 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 49cb69220f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new b3c5a3bf9d 124: onsuccess: #2159: 1: Success after linux: 23 commits new e3a6bde2cc 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 800c21ad89 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 8a42ce3c83 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 48c65f4bfa 128: onsuccess: #2163: 1: Success after linux: 23 commits new 88fb483d70 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 054313bfe4 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 1ab265ea0f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new c118702180 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 68cd8f0ac6 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new e9074e1998 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 228037905f 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new e9c00f5850 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new f836ea54d1 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3d38fae4d8 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 750612b2c5 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 3f0be535ad 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 091b739f94 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 0a63688ffe 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 928dedfa6b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 4b30e5fa51 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 04838d9e7d 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new cbfd369cfe 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 4ade955916 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 085e3e34f9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 3c20950a80 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 27d625f037 150: onsuccess: #2185: 1: Success after gcc: 3 commits new fc4c2b126d 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 3364e353bf 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 9698f72926 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new fc32e4c69e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 774d667166 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 2410ba3e48 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new af0ecb06f2 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new fb9e1b846c 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 70a6d665aa 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new bd97bc639e 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new bfd6f35d5c 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 219009b990 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 88e9c4a542 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 7df2c82842 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 901d9a8fb3 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 5b523a5935 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 50705d9bf1 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new bdfa895998 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new b97e24a7e0 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new db40b73f65 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 20b6496a20 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 53e7731484 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new daa89bb38b 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 17fe549eec 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 77b8330d76 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 6a061ccf35 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 326a82e342 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 52dbc42669 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new c642e04dc5 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 882750ee62 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new ab6b668c3e 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new f51ff1431f 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 0856aad4ff 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 753aa65469 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 41ad731891 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (383699d8f7) \ 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 1828 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 31132 -> 30972 bytes 04-build_abe-stage1/console.log.xz | Bin 72860 -> 73320 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9540 -> 8512 bytes 07-build_abe-glibc/console.log.xz | Bin 240364 -> 241464 bytes 08-build_abe-stage2/console.log.xz | Bin 206612 -> 207012 bytes 09-build_abe-gdb/console.log.xz | Bin 38184 -> 38188 bytes 10-build_abe-qemu/console.log.xz | Bin 32160 -> 32472 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3956 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2708 -> 3252 bytes 13-check_regression/console.log.xz | Bin 19788 -> 8564 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 33 +- 13-check_regression/mail-body.txt | 198 +- 13-check_regression/results.compare | 517 +-- 13-check_regression/results.compare2 | 2828 ++--------------- 13-check_regression/results.regressions | 132 +- 14-update_baseline/console.log | 64 +- 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 | 200 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 130 +- sumfiles/g++.log.xz | Bin 3451364 -> 3431572 bytes sumfiles/g++.sum | 315 +- sumfiles/gcc.log.xz | Bin 3027976 -> 3042760 bytes sumfiles/gcc.sum | 5184 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1037932 -> 1030816 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 203944 -> 204136 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2696 -> 2700 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 430644 -> 423764 bytes sumfiles/libstdc++.sum | 37 +- 45 files changed, 3484 insertions(+), 6280 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[glibc] branch master updated (8c77e26ba8 -> 361d6454c0)

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 glibc. from 8c77e26ba8 Remove unused scratch_buffer_dupfree new 361d6454c0 Correctly determine libc.so 'OUTPUT_FORMAT' when cross-compiling. 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: aclocal.m4 | 2 -- configure | 96 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-- configure.ac | 1 + 3 files changed, 94 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-allmodconfig updated (6487052501 -> a19e8457d3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from 6487052501 26: onsuccess: #887: boot: Success after binutils/gcc/qemu: [...] new a19e8457d3 27: force: #889: boot: Success after linux: 404 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 1904 -> 1828 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 29896 -> 30888 bytes 04-build_abe-stage1/console.log.xz | Bin 87736 -> 87908 bytes 05-build_abe-qemu/console.log.xz | Bin 31832 -> 32092 bytes 06-build_linux/console.log.xz | Bin 3408 -> 3356 bytes 07-boot_linux/console.log.xz | Bin 480 -> 480 bytes 08-check_regression/console.log.xz | Bin 3612 -> 2912 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 22 ++++++++++------------ results | 2 +- 17 files changed, 19 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_debug updated (99644598fe -> 04339a9b13)

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_debug in repository toolchain/ci/base-artifacts. from 99644598fe 86: onsuccess: #505: 2: Success after binutils/gcc: 27 commits new 04339a9b13 87: onsuccess: #506: 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 1692 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 50552 -> 51364 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 467172 -> 466192 bytes 06-check_regression/console.log.xz | Bin 3164 -> 2992 bytes 07-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 15 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-norov-defconfig updated (b490994744 -> 4906906b2e)

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-norov-defconfig in repository toolchain/ci/base-artifacts. from b490994744 17: onsuccess: #56: boot: Success after binutils/llvm: 394 commits new 4906906b2e 18: onsuccess: #57: boot: Success after binutils/llvm/qemu: [...] 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 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30212 -> 30344 bytes 04-build_kernel_llvm/console.log.xz | Bin 63728 -> 65116 bytes 05-build_abe-qemu/console.log.xz | Bin 32136 -> 31628 bytes 06-build_linux/console.log.xz | Bin 3636 -> 3664 bytes 07-boot_linux/console.log.xz | Bin 5732 -> 5716 bytes 08-check_regression/console.log.xz | Bin 3632 -> 4044 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch releases/gcc-12 updated (9831a5f4843 -> ebe47cc6f15)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 9831a5f4843 Fortran: BOZ literal constants are not compatible to any ty [...] new ebe47cc6f15 Daily bump. 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/ChangeLog | 10 ++++++++++ gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 9 +++++++++ gcc/testsuite/ChangeLog | 8 ++++++++ libgomp/ChangeLog | 13 +++++++++++++ 5 files changed, 41 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch releases/gcc-11 updated (f2298bd5010 -> dd27a84503b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from f2298bd5010 Fortran: BOZ literal constants are not compatible to any ty [...] new dd27a84503b Daily bump. 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/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 9 +++++++++ gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 18 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (1f6fc6ba2e -> bddc2727ea)

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 1f6fc6ba2e 251: onsuccess: #1872: 1: Success after binutils/gcc: 10 commits discards 5eef1ad688 250: onsuccess: #1871: 1: Success after binutils/gcc: 11 commits discards 00950ff36d 249: onsuccess: #1870: 1: Success after binutils/gcc: 9 commits discards 825d86033a 248: onsuccess: #1869: 1: Success after gcc: 4 commits discards 3f6934db71 247: onsuccess: #1868: 1: Success after binutils/gcc: 7 commits discards 8560d7d92c 246: onsuccess: #1867: 1: Success after binutils/gcc: 8 commits discards a782726272 245: onsuccess: #1866: 1: Success after binutils/gcc: 8 commits discards 4d3dca0034 244: onsuccess: #1865: 1: Success after gcc: 6 commits discards f40b61aba1 243: onsuccess: #1864: 1: Success after binutils/gcc: 6 commits discards bcdecf01c5 242: onsuccess: #1863: 1: Success after binutils/gcc: 17 commits discards eb5cc87531 241: onsuccess: #1862: 1: Success after binutils/gcc: 5 commits discards 808f8a6e5a 240: onsuccess: #1861: 1: Success after gcc: 6 commits discards 5040a13d9e 239: onsuccess: #1860: 1: Success after binutils/gcc: 9 commits discards d03f661f83 238: onsuccess: #1859: 1: Success after binutils/gcc: 14 commits discards 4799e5d98f 237: onsuccess: #1858: 1: Success after binutils/gcc: 6 commits discards d64111d3e7 236: onsuccess: #1857: 1: Success after binutils/gcc: 10 commits discards ba9308f0d0 235: onsuccess: #1856: 1: Success after binutils/gcc: 18 commits discards 7914ddc55b 234: onsuccess: #1855: 1: Success after binutils/gcc: 7 commits discards 955896fac8 233: onsuccess: #1854: 1: Success after binutils/gcc: 6 commits discards a7defb2b24 232: onsuccess: #1853: 1: Success after binutils: 3 commits discards 58d24a5a0f 231: onsuccess: #1852: 1: Success after binutils/gcc: 4 commits discards 23b98ad352 230: onsuccess: #1851: 1: Success after basepoints/gcc-13-34 [...] discards ab14e9680c 229: onsuccess: #1850: 1: Success after basepoints/gcc-13-34 [...] discards ebb472b6e6 228: onsuccess: #1849: 1: Success after binutils/gcc: 3 commits discards 9b14e967e2 227: onsuccess: #1848: 1: Success after binutils/gcc: 4 commits discards d69b86ad1c 226: onsuccess: #1847: 1: Success after binutils/gcc: 8 commits discards 2fb217f6b7 225: onsuccess: #1846: 1: Success after binutils/gcc: 18 commits discards b03de6a58d 224: onsuccess: #1845: 1: Success after binutils/gcc: 9 commits discards 02a1aad2c7 223: onsuccess: #1844: 1: Success after gcc: 7 commits discards 787df38acb 222: onsuccess: #1843: 1: Success after binutils/gcc: 17 commits discards 767c2f167f 221: onsuccess: #1842: 1: Success after binutils/gcc: 15 commits discards 074137d597 220: onsuccess: #1841: 1: Success after binutils/gcc: 10 commits discards d239cd1efd 219: onsuccess: #1840: 1: Success after gcc: 7 commits discards a752980e17 218: onsuccess: #1839: 1: Success after binutils/gcc: 23 commits discards ede4dee91c 217: onsuccess: #1838: 1: Success after binutils/gcc: 12 commits discards 830a1fcd2d 216: onsuccess: #1837: 1: Success after binutils/gcc: 4 commits discards 5642d4c4fa 215: onsuccess: #1836: 1: Success after binutils/gcc: 2 commits discards f1194532e5 214: onsuccess: #1835: 1: Success after binutils/gcc: 30 commits discards 348a436ed4 213: onsuccess: #1834: 1: Success after binutils/gcc: 8 commits discards ff785c3977 212: onsuccess: #1833: 1: Success after binutils/gcc: 8 commits discards 3cc44ca479 211: onsuccess: #1832: 1: Success after binutils/gcc: 26 commits discards a08c4e197b 210: onsuccess: #1830: 1: Success after binutils/gcc: 10 commits discards ad3b83db49 209: onsuccess: #1829: 1: Success after binutils/gcc: 4 commits discards affaef2234 208: onsuccess: #1828: 1: Success after binutils: 2 commits discards fc20c6c0d9 207: onsuccess: #1827: 1: Success after gcc: 2 commits discards a7d2fa0c53 206: onsuccess: #1826: 1: Success after binutils/gcc: 5 commits discards a11da81ffe 205: onsuccess: #1825: 1: Success after gcc: 3 commits discards 39e13c71dd 204: onsuccess: #1824: 1: Success after gdb-12-branchpoint-2 [...] discards a920f24f2d 203: onsuccess: #1823: 1: Success after binutils/gcc: 3 commits discards 680bd131aa 202: onsuccess: #1822: 1: Success after binutils/gcc: 10 commits discards d7d1a19e80 201: onsuccess: #1821: 1: Success after binutils/gcc: 19 commits discards 42b4a3aff0 200: onsuccess: #1820: 1: Success after binutils/gcc: 19 commits discards abeed9f66e 199: onsuccess: #1819: 1: Success after binutils/gcc: 5 commits discards eafbd27f4b 198: onsuccess: #1818: 1: Success after binutils/gcc: 5 commits discards f7092df28e 197: onsuccess: #1817: 1: Success after gcc: 13 commits discards cf4b17d6dc 196: onsuccess: #1816: 1: Success after binutils/gcc: 5 commits discards 3b92fe2af3 195: onsuccess: #1815: 1: Success after binutils/gcc: 4 commits discards e96fa72517 194: onsuccess: #1814: 1: Success after binutils/gcc: 8 commits discards fb44e04426 193: onsuccess: #1813: 1: Success after binutils/gcc: 17 commits discards a83cc1cbe7 192: onsuccess: #1812: 1: Success after binutils/gcc: 11 commits discards 5f9830c43a 191: onsuccess: #1811: 1: Success after binutils/gcc: 6 commits discards d4bb65fc79 190: onsuccess: #1810: 1: Success after binutils/gcc: 6 commits discards f21f2edde1 189: onsuccess: #1809: 1: Success after binutils/gcc: 33 commits discards d9465ce776 188: onsuccess: #1808: 1: Success after binutils/gcc: 15 commits discards 5c8d586449 187: onsuccess: #1807: 1: Success after binutils/gcc: 7 commits discards 977bd5b7bc 186: onsuccess: #1806: 1: Success after binutils/gcc: 11 commits discards b925778a17 185: onsuccess: #1805: 1: Success after binutils/gcc: 18 commits discards 5bf4e0d39b 184: onsuccess: #1804: 1: Success after binutils/gcc: 16 commits discards bf650b957b 183: onsuccess: #1803: 1: Success after binutils/gcc: 4 commits discards 1fcbfcbbdf 182: onsuccess: #1802: 1: Success after gcc: 2 commits discards 748677a1d8 181: onsuccess: #1801: 1: Success after basepoints/gcc-13-31 [...] discards 98ed0f9e78 180: onsuccess: #1800: 1: Success after binutils/gcc: 2 commits discards c290ee8bd8 179: onsuccess: #1799: 1: Success after basepoints/gcc-13-31 [...] discards bdb3a275b0 178: onsuccess: #1798: 1: Success after gdb-12-branchpoint-2 [...] discards 7842c6504b 177: onsuccess: #1797: 1: Success after gdb-12-branchpoint-2 [...] discards 75261bc9c0 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits discards 46e1e371b6 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits discards a1c5c9ef6c 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits discards 76920f0f4e 173: onsuccess: #1793: 1: Success after gcc: 12 commits discards 86153fa6db 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits discards d2fdbc7939 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits discards 7e0d8201d2 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits discards 1bbe02ccdc 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits discards 2482253516 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits discards 1b76fdaa2f 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards 3dd10a96c5 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards 9b1e01e3e5 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards b5c72837de 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards bc8498bbcc 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards c5c3a2995e 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards e981f3f0f7 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards 21a8827014 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards 1ec943fa79 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards 2b0351e2b5 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards 3c35d3d4f7 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 7edd221985 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards d82dd7852e 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards dc13eb3c2a 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 3731af8ad6 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards 80ccb1e988 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards e478ac644f 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 247c52fcc1 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new c2fb0098ee 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 4573d9b1c1 153: onsuccess: #1773: 1: Success after gcc: 4 commits new 7f64af815f 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new f9bff3ca78 155: onsuccess: #1775: 1: Success after binutils: 2 commits new 89f93758eb 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new 37d80f095d 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new 1d703fb235 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new 0714a79e15 159: onsuccess: #1779: 1: Success after gcc: 2 commits new c0b0c29fa5 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new 76c01c2fec 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new 243199cab6 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new 4f221fd191 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new 60528e426a 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new c8b90eb5b0 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new 897f5aad04 166: onsuccess: #1786: 1: Success after gcc: 10 commits new 666b1b8b38 167: onsuccess: #1787: 1: Success after gcc: 8 commits new cba93eafdc 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits new c7ee743ad6 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits new 14c48a3cd5 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits new a726432d82 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits new 5097862ab5 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits new eba90dc16b 173: onsuccess: #1793: 1: Success after gcc: 12 commits new 842ee00c2b 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits new 09cb891fc8 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits new 7bf7f92534 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits new 1bd3aa35f4 177: onsuccess: #1797: 1: Success after gdb-12-branchpoint-2 [...] new dc5be5741d 178: onsuccess: #1798: 1: Success after gdb-12-branchpoint-2 [...] new ebdd9ae1d7 179: onsuccess: #1799: 1: Success after basepoints/gcc-13-31 [...] new c174126487 180: onsuccess: #1800: 1: Success after binutils/gcc: 2 commits new 45690ee625 181: onsuccess: #1801: 1: Success after basepoints/gcc-13-31 [...] new c6f1ca561e 182: onsuccess: #1802: 1: Success after gcc: 2 commits new 3946ae0164 183: onsuccess: #1803: 1: Success after binutils/gcc: 4 commits new 2747aecd8f 184: onsuccess: #1804: 1: Success after binutils/gcc: 16 commits new d8bba572c8 185: onsuccess: #1805: 1: Success after binutils/gcc: 18 commits new 82af3e1706 186: onsuccess: #1806: 1: Success after binutils/gcc: 11 commits new 82a51d057f 187: onsuccess: #1807: 1: Success after binutils/gcc: 7 commits new d870bb7547 188: onsuccess: #1808: 1: Success after binutils/gcc: 15 commits new c5ae7b28a3 189: onsuccess: #1809: 1: Success after binutils/gcc: 33 commits new ad3ff1c752 190: onsuccess: #1810: 1: Success after binutils/gcc: 6 commits new 5a5697b0fc 191: onsuccess: #1811: 1: Success after binutils/gcc: 6 commits new ede2a0e7e5 192: onsuccess: #1812: 1: Success after binutils/gcc: 11 commits new e38207f900 193: onsuccess: #1813: 1: Success after binutils/gcc: 17 commits new ae079c1004 194: onsuccess: #1814: 1: Success after binutils/gcc: 8 commits new a2a030aaef 195: onsuccess: #1815: 1: Success after binutils/gcc: 4 commits new 582cc8ba33 196: onsuccess: #1816: 1: Success after binutils/gcc: 5 commits new 8c10e4d14d 197: onsuccess: #1817: 1: Success after gcc: 13 commits new 7ee713ba3a 198: onsuccess: #1818: 1: Success after binutils/gcc: 5 commits new 6e17964f2e 199: onsuccess: #1819: 1: Success after binutils/gcc: 5 commits new 24a8647b11 200: onsuccess: #1820: 1: Success after binutils/gcc: 19 commits new 0ede18fe8f 201: onsuccess: #1821: 1: Success after binutils/gcc: 19 commits new 0cacffbfd2 202: onsuccess: #1822: 1: Success after binutils/gcc: 10 commits new cc81deadc1 203: onsuccess: #1823: 1: Success after binutils/gcc: 3 commits new f011cfbc7b 204: onsuccess: #1824: 1: Success after gdb-12-branchpoint-2 [...] new 97e6002c70 205: onsuccess: #1825: 1: Success after gcc: 3 commits new 50b890c790 206: onsuccess: #1826: 1: Success after binutils/gcc: 5 commits new 021af82e2a 207: onsuccess: #1827: 1: Success after gcc: 2 commits new de3a9b69f3 208: onsuccess: #1828: 1: Success after binutils: 2 commits new fea25064b4 209: onsuccess: #1829: 1: Success after binutils/gcc: 4 commits new 58d32c9581 210: onsuccess: #1830: 1: Success after binutils/gcc: 10 commits new 49d85d4813 211: onsuccess: #1832: 1: Success after binutils/gcc: 26 commits new 7f6fe6a099 212: onsuccess: #1833: 1: Success after binutils/gcc: 8 commits new 2ea752c155 213: onsuccess: #1834: 1: Success after binutils/gcc: 8 commits new 1988a789da 214: onsuccess: #1835: 1: Success after binutils/gcc: 30 commits new a77bbf3910 215: onsuccess: #1836: 1: Success after binutils/gcc: 2 commits new 51c17f06e2 216: onsuccess: #1837: 1: Success after binutils/gcc: 4 commits new d9713653de 217: onsuccess: #1838: 1: Success after binutils/gcc: 12 commits new 16dacccbd3 218: onsuccess: #1839: 1: Success after binutils/gcc: 23 commits new 86a132d156 219: onsuccess: #1840: 1: Success after gcc: 7 commits new ec8fe0771d 220: onsuccess: #1841: 1: Success after binutils/gcc: 10 commits new f1cf627cad 221: onsuccess: #1842: 1: Success after binutils/gcc: 15 commits new 11293008e3 222: onsuccess: #1843: 1: Success after binutils/gcc: 17 commits new 4dd5247040 223: onsuccess: #1844: 1: Success after gcc: 7 commits new f2e7d86af7 224: onsuccess: #1845: 1: Success after binutils/gcc: 9 commits new e2ab99d971 225: onsuccess: #1846: 1: Success after binutils/gcc: 18 commits new d68fd523d0 226: onsuccess: #1847: 1: Success after binutils/gcc: 8 commits new 570166fbf8 227: onsuccess: #1848: 1: Success after binutils/gcc: 4 commits new d82acad08d 228: onsuccess: #1849: 1: Success after binutils/gcc: 3 commits new 22d0d179d1 229: onsuccess: #1850: 1: Success after basepoints/gcc-13-34 [...] new a3b615b995 230: onsuccess: #1851: 1: Success after basepoints/gcc-13-34 [...] new e52508e717 231: onsuccess: #1852: 1: Success after binutils/gcc: 4 commits new bb4718ca1e 232: onsuccess: #1853: 1: Success after binutils: 3 commits new bb3e741bc0 233: onsuccess: #1854: 1: Success after binutils/gcc: 6 commits new d5f02c6451 234: onsuccess: #1855: 1: Success after binutils/gcc: 7 commits new b25937930f 235: onsuccess: #1856: 1: Success after binutils/gcc: 18 commits new 419a666214 236: onsuccess: #1857: 1: Success after binutils/gcc: 10 commits new c337d985e1 237: onsuccess: #1858: 1: Success after binutils/gcc: 6 commits new c38dad28ec 238: onsuccess: #1859: 1: Success after binutils/gcc: 14 commits new cc113668f0 239: onsuccess: #1860: 1: Success after binutils/gcc: 9 commits new 242e1a956f 240: onsuccess: #1861: 1: Success after gcc: 6 commits new ab697cd26f 241: onsuccess: #1862: 1: Success after binutils/gcc: 5 commits new dd84ffc278 242: onsuccess: #1863: 1: Success after binutils/gcc: 17 commits new 556939310d 243: onsuccess: #1864: 1: Success after binutils/gcc: 6 commits new ba35cca0cc 244: onsuccess: #1865: 1: Success after gcc: 6 commits new 61b9f16972 245: onsuccess: #1866: 1: Success after binutils/gcc: 8 commits new bd75ab884f 246: onsuccess: #1867: 1: Success after binutils/gcc: 8 commits new a7371c00c5 247: onsuccess: #1868: 1: Success after binutils/gcc: 7 commits new 96e3871f38 248: onsuccess: #1869: 1: Success after gcc: 4 commits new 00572e4f3a 249: onsuccess: #1870: 1: Success after binutils/gcc: 9 commits new ea666a3a11 250: onsuccess: #1871: 1: Success after binutils/gcc: 11 commits new ea262c0d97 251: onsuccess: #1872: 1: Success after binutils/gcc: 10 commits new bddc2727ea 252: onsuccess: #1873: 1: Success after binutils/gcc: 4 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (1f6fc6ba2e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (bd [...] 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 1664 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 50872 -> 50720 bytes 04-build_abe-gcc/console.log.xz | Bin 233452 -> 233900 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3848 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2588 -> 2984 bytes 07-check_regression/console.log.xz | Bin 5440 -> 5068 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 27 + 07-check_regression/results.compare | 26 +- 07-check_regression/results.compare2 | 155 +- 07-check_regression/results.regressions | 27 + 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 27 + sumfiles/g++.log.xz | Bin 2839564 -> 2788764 bytes sumfiles/g++.sum | 132 +- sumfiles/gcc.log.xz | Bin 2395188 -> 2395664 bytes sumfiles/gcc.sum | 4412 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 922448 -> 912944 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206740 -> 206524 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2536 -> 2536 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 469960 -> 467184 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2541 insertions(+), 2474 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022