Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-defconfig updated (0c7504884a -> 7c82ce5831)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from 0c7504884a 23: onsuccess: #413: boot: Success after binutils/linux/qemu [...] new 7c82ce5831 24: onsuccess: #414: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29936 -> 30020 bytes 04-build_kernel_llvm/console.log.xz | Bin 63620 -> 64828 bytes 05-build_abe-qemu/console.log.xz | Bin 31756 -> 30744 bytes 06-build_linux/console.log.xz | Bin 3204 -> 3216 bytes 07-boot_linux/console.log.xz | Bin 5660 -> 5664 bytes 08-check_regression/console.log.xz | Bin 3704 -> 4276 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (1ba0dae38e -> 4fb401d126)

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 1ba0dae38e 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] discards 309ec12528 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 301ae6843f 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] discards 655dd98356 194: force: #1853: 7: Success after gcc: 26 commits discards db75d51844 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards 9826523b9a 192: onsuccess: #1848: 7: Success after linux: 213 commits discards af274f21d7 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 7f97376a9a 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 384a3455d6 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards 87fb6da03d 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards 8bf8e9de39 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards 0f9f6ac72f 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards 030f9044e2 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] discards 006cc1f769 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] discards 1cdf13c92e 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] discards 227c8842bc 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits discards 67eb56ed20 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] discards a0947a26f9 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] discards 5f112ca778 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] discards 662755a962 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] discards 52c71b7cb4 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] discards e62f5b1f68 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] discards fbc65997bc 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] discards 3432ff2e19 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] discards df3421eab5 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] discards fedfceb0c9 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 8a83ac0f61 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] discards 77fa9e55fc 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] discards d3c8d78d1d 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] discards 005dc069db 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards c3625145d2 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 56a05e1325 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards 5476dc2d9a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards 6974a3be6a 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards 946224f2bc 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards cc4d2dacf6 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards c80a2f5805 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards c30fdb2ed2 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards c1c54fd263 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards 8c45a821d9 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards dab9a3c9e6 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 251506e4e1 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 372c15f3f4 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards 5299591030 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards c3551d2ab2 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 8150bbc68f 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards 83abd3201a 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 014cf914cd 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 2c2880bef5 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 105b5b26c4 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards d6a81de2c5 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards c14919c3ff 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 4c5b33f079 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards a194364fd1 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 462a324b69 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 31a550bc19 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 3d3679126f 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 2689af2ed1 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 686a7d2d48 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards b7295e9329 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards f2097962c0 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 81e2d62a37 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards bda9fe21c9 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 2956d10e82 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 32842e4ad4 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 76e9852da7 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 0545ecf8a4 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 04f629b860 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards feb1073627 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 9a6a9cc810 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 41ae594758 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 80c3a0213f 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards c42e42255d 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 178e208a81 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 914d3e41c5 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 2108829382 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 6cc3088167 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards b8b2ee3786 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 4c55d745bc 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards f0c9ee5560 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 75e1d0004f 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards a9d3046bbb 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards a12b75a62f 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 3db832a292 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 314cc0229f 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards d333678ea2 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards a71f367356 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 3ede723d31 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards f0e6647737 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards cec8fa4e51 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards bd1ac62678 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards a496eff643 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards c73d260d2e 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 447debf889 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards d9e40b5baa 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 2b5b9da485 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards c0a45da563 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards b6933c1782 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 13b765a3ad 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 8acccadcb2 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 3106e56ce4 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new aee8793d68 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 2b52a5218c 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new b5012f8b42 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new c8317ca1d0 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new a17c47e441 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 22ee5d0285 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 0c508494c9 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new c2aa4823ff 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 818ee94558 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 1041746ed4 106: onsuccess: #1617: 7: Success after gcc: 2 commits new eff93a0654 107: onsuccess: #1618: 7: Success after gcc: 2 commits new a9a35af8ff 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new ea5e3c821a 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 07647874c5 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 08c6ebebb6 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 77ac6eccf0 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 71c012cad7 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 5f2d92a7eb 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 5c43487cd1 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 7da08099c5 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 72fb6b9b33 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new dad1c2cc8e 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 68e12230e6 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 48b455cbd7 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new dbe4a8278e 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 0233dfe0bf 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 219f4381df 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 627695140d 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 8c64ec1def 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 38fc4e4b11 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new fc79920685 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new d72d748e87 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 2c2cdaa846 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new a4c3dbe382 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 38ed194312 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 7e7b90a829 132: onsuccess: #1645: 7: Success after linux: 23 commits new d4614a24a7 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 542e1a9d91 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new cfc3e2b63a 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new d95df6961c 136: onsuccess: #1650: 7: Success after binutils: 2 commits new d9e538ddb8 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new f23a419b10 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 1e97357d66 139: onsuccess: #1654: 1: Success after gcc: 11 commits new e8137e8d75 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new e9f58a6b1f 141: onsuccess: #1656: 7: Success after gcc: 7 commits new cdeeca8376 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 6155e0e1d6 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new fabcba5734 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new befbb3d716 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 157ee386e1 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 13bbfffd85 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 8354d0301b 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 67fb80de00 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new b073a62546 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new f07512a42b 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new e180480c47 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new cca5eef5b4 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new e916e594c2 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new ac91d3f792 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 60d519dec0 156: onsuccess: #1671: 7: Success after gcc: 3 commits new eb3be86971 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 9c694cccac 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 58c9a09400 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new af1ecf65f1 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new f54dc4d0f9 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new c717ffa515 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new c3d01f7cf7 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new c79c83b24a 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new d5d819f346 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new 5ac2cf0c06 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new e554ebda54 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 4d3be19553 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new 89a6573322 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] new 3b47e0b45f 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] new 259a444f1e 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] new ec58f76988 172: onsuccess: #1687: 7: Success after gcc: 11 commits new c01ed10d96 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] new be2b7f0f95 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] new 563395a256 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] new e54b403733 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] new 68b17ea4f9 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] new 72084a71da 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] new cfc58e4b87 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] new 1297bb2015 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] new c86ee6feb6 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new eafd601cfd 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits new 834c3cf5c0 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new bf8f111c7c 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] new 096c65d40a 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new a0ebecd737 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new d1f574fa84 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new f2ce7925a6 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new 39993bd508 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new 8f6d6ad28e 190: onsuccess: #1834: 7: Success after binutils: 25 commits new c62cff7c2c 191: onsuccess: #1846: 7: Success after binutils: 4 commits new f22c98ca05 192: onsuccess: #1848: 7: Success after linux: 213 commits new 1ddc28c41f 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new 39ad97a50e 194: force: #1853: 7: Success after gcc: 26 commits new b2dbaeb410 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] new 976462482b 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 7cc620242a 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] new 4fb401d126 198: onsuccess: #1878: 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 (1ba0dae38e) \ 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 1896 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 30268 -> 31464 bytes 05-build_abe-stage1/console.log.xz | Bin 91080 -> 91980 bytes 07-build_abe-linux/console.log.xz | Bin 8332 -> 8528 bytes 08-build_abe-glibc/console.log.xz | Bin 236244 -> 235400 bytes 09-build_abe-stage2/console.log.xz | Bin 220564 -> 223588 bytes 10-build_abe-gdb/console.log.xz | Bin 0 -> 38784 bytes 11-build_abe-qemu/console.log.xz | Bin 0 -> 30980 bytes 12-check_regression/console.log.xz | Bin 4136 -> 5148 bytes 12-check_regression/mail-body.txt | 6 +- 13-update_baseline/console.log | 66 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 + git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 8 ++- mail/mail-subject.txt | 2 +- manifest.sh | 46 +++++++------- results | 6 +- 25 files changed, 85 insertions(+), 66 deletions(-) create mode 100644 10-build_abe-gdb/console.log.xz create mode 100644 11-build_abe-qemu/console.log.xz create mode 100644 dashboard/squad-vs-first/score/results-functional.json -- 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-release-arm-next-defconfig updated (6fb9673fcc -> 66bf7e69a2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-next-defconfig in repository toolchain/ci/base-artifacts. from 6fb9673fcc 22: onsuccess: #330: boot: Success after binutils/linux/qemu [...] new 66bf7e69a2 23: onsuccess: #331: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29820 -> 30096 bytes 04-build_kernel_llvm/console.log.xz | Bin 63516 -> 64128 bytes 05-build_abe-qemu/console.log.xz | Bin 31908 -> 31396 bytes 06-build_linux/console.log.xz | Bin 3112 -> 3108 bytes 07-boot_linux/console.log.xz | Bin 5624 -> 5656 bytes 08-check_regression/console.log.xz | Bin 3692 -> 4204 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_tx1/llvm-master-aarch64-spec2k6-O3 updated (0304b77f72 -> 4493f49a8c)

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_bmk_llvm_tx1/llvm-master-aarch64-spec2k6-O3 in repository toolchain/ci/base-artifacts. from 0304b77f72 17: force: #505: 1: [TCWG CI] No change after llvm: 468 commits new 4493f49a8c 18: force: #506: 1: [TCWG CI] No change after working-3956-g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1644 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 31740 -> 31828 bytes 04-build_abe-stage1/console.log.xz | Bin 72984 -> 72996 bytes 06-build_abe-linux/console.log.xz | Bin 8744 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 244100 -> 243508 bytes 08-build_abe-stage2/console.log.xz | Bin 177436 -> 177216 bytes 09-build_llvm-true-false-/console.log.xz | Bin 64348 -> 63968 bytes 10-benchmark/benchmark-build.log | 104 +- 10-benchmark/benchmark.log | 102 +- 10-benchmark/console.log.xz | Bin 4000 -> 4024 bytes 11-check_regression/console.log.xz | Bin 11348 -> 11676 bytes .../csv-results-vs-first-1/md5sum.csv | 1553 +- .../csv-results-vs-first-1/perf.csv | 1925 +- .../csv-results-vs-first-1/results.csv | 8757 +- .../csv-results-vs-first-1/size.csv | 138960 +++++++------ .../csv-results-vs-first-1/vect.csv | 6816 +- .../csv-results-vs-prev-0/md5sum.csv | 1592 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 1933 +- .../csv-results-vs-prev-0/results.csv | 4245 +- 11-check_regression/csv-results-vs-prev-0/size.csv | 194358 +++++++++--------- 11-check_regression/csv-results-vs-prev-0/vect.csv | 18326 +- .../csv-results-vs-prev-1/md5sum.csv | 1553 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 1925 +- .../csv-results-vs-prev-1/results.csv | 8757 +- 11-check_regression/csv-results-vs-prev-1/size.csv | 138960 +++++++------ 11-check_regression/csv-results-vs-prev-1/vect.csv | 6816 +- 11-check_regression/results-vs-first-brief.csv | 44 +- 11-check_regression/results-vs-first-full.csv | 1907 +- 11-check_regression/results-vs-first-internal.csv | 150 +- 11-check_regression/results-vs-first.csv | 150 +- 11-check_regression/results-vs-first.log | 576 +- 11-check_regression/results-vs-prev-brief.csv | 44 +- 11-check_regression/results-vs-prev-compare.csv | 4 +- 11-check_regression/results-vs-prev-full.csv | 2035 +- 11-check_regression/results-vs-prev-internal.csv | 150 +- 11-check_regression/results-vs-prev.csv | 150 +- 11-check_regression/results-vs-prev.log | 800 +- 11-check_regression/skipped-symbols.txt | 27 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 74 +- git/llvm_rev | 2 +- mail/jira-body.txt | 11 +- mail/mail-body.txt | 11 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results_id | 2 +- 71 files changed, 282463 insertions(+), 260564 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_check/master-aarch64 updated (56b37ffcf8 -> ce5323cdd5)

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 56b37ffcf8 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards 97a81ac6fa 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint-2 [...] discards 32bd464da0 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards 9a5776f0a6 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards f8f78652aa 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards 10200e5112 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards 656bd6a130 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards ab5b609de1 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards 00fa1a5401 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards e757710d01 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 759c7f00c6 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards 812656b13a 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards 99f83de1a1 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards 16bd629530 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards 167acdf71b 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards bcf73aa95a 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards df8fe00695 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards 761dcf7748 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 19476da783 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint-2 [...] discards f4faebc2ab 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards 96a375a3df 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint-2 [...] discards 3a407dbcca 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint-2 [...] discards d9c5033eee 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint-2 [...] discards 48da3629ac 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint-2 [...] discards 015cdee5ce 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards 6eed893e62 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards 4dc3584cae 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards b312d49b52 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards d6398310f2 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards 13e9de4767 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards 0922858646 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards b13e804118 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards 23a4c91841 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards c5dd8763dc 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits discards c43d6b85b4 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits discards aeee39c4a6 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits discards c49bc84fcc 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits discards 8492ff7eed 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits discards 1568695a72 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits discards 26c9063aaa 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits discards 83d4575667 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits discards 25ace31d89 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits discards 8d69aebe9e 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits discards 28d7a56bff 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits discards aeaf699eb9 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits discards db20cb9d8a 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits discards da5897a4ca 283: onsuccess: #2222: 1: Success after gcc: 4 commits discards 9ac58f5220 282: onsuccess: #2221: 1: Success after gcc: 2 commits discards 443c359802 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits discards c630b30c30 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits discards b01ba2478f 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-36 [...] discards 364a580d1b 278: onsuccess: #2217: 1: Success after binutils: 7 commits discards dbe1937933 277: onsuccess: #2216: 1: Success after binutils: 2 commits discards 8a8f26d72f 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits discards 906a733444 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits discards d65be2d447 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits discards 42b2d184bc 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits discards 539c7d4526 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits discards 0a67ef1581 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits discards b7ac258a71 270: onsuccess: #2209: 1: Success after gcc: 2 commits discards 04437a1dcb 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits discards 64e080b2a1 268: onsuccess: #2207: 1: Success after binutils/gcc: 12 commits discards 27c55435a2 267: onsuccess: #2206: 1: Success after binutils/gcc: 5 commits discards 2d8d977fe2 266: onsuccess: #2205: 1: Success after binutils/gcc: 8 commits discards c4076b5d36 265: onsuccess: #2204: 1: Success after binutils/gcc: 5 commits discards a2b95a36a2 264: onsuccess: #2203: 1: Success after gcc: 9 commits discards cbfadfe837 263: onsuccess: #2202: 1: Success after binutils/gcc: 5 commits discards 28e82231d8 262: onsuccess: #2201: 1: Success after gcc: 6 commits discards 715348cc31 261: onsuccess: #2200: 1: Success after binutils/gcc: 8 commits discards e874b4f051 260: onsuccess: #2199: 1: Success after binutils/gcc: 18 commits discards 4391b4f9ba 259: onsuccess: #2198: 1: Success after binutils/gcc: 8 commits discards 7a3114f0b3 258: onsuccess: #2197: 1: Success after binutils/gcc: 5 commits discards 3a96556228 257: onsuccess: #2196: 1: Success after binutils/gcc: 2 commits discards 4db4c41556 256: onsuccess: #2195: 1: Success after gdb-12-branchpoint-2 [...] discards b37afaf69c 255: onsuccess: #2194: 1: Success after basepoints/gcc-13-35 [...] discards df5528579e 254: onsuccess: #2193: 1: Success after gdb-12-branchpoint-2 [...] discards 18eeb0d0f2 253: onsuccess: #2192: 1: Success after gdb-12-branchpoint-2 [...] discards c9cc08b995 252: onsuccess: #2191: 1: Success after binutils/gcc: 29 commits discards 3085d45253 251: onsuccess: #2188: 1: Success after binutils/gcc: 11 commits discards d9d95da59f 250: onsuccess: #2187: 1: Success after binutils/gcc: 10 commits discards ab63bcc193 249: onsuccess: #2186: 1: Success after binutils/gcc: 7 commits discards 98168ddcf7 248: onsuccess: #2185: 1: Success after binutils/gcc: 7 commits discards 13ecfea550 247: onsuccess: #2184: 1: Success after binutils/gcc: 7 commits discards 3a724fd783 246: onsuccess: #2183: 1: Success after binutils/gcc: 8 commits discards bbb65d5e27 245: onsuccess: #2182: 1: Success after binutils/gcc: 6 commits discards aa6f5729a3 244: onsuccess: #2181: 1: Success after binutils/gcc: 7 commits discards 39a5382ec0 243: onsuccess: #2180: 1: Success after binutils/gcc: 4 commits discards 39aa39458e 242: onsuccess: #2179: 1: Success after binutils/gcc: 16 commits discards 6fa2701240 241: onsuccess: #2178: 1: Success after binutils/gcc: 7 commits discards e5f648c333 240: onsuccess: #2177: 1: Success after binutils/gcc: 6 commits discards 1b23e0ee9e 239: onsuccess: #2176: 1: Success after binutils/gcc: 8 commits discards ffabc2bd2c 238: onsuccess: #2175: 1: Success after binutils/gcc: 14 commits discards abdc113eff 237: onsuccess: #2174: 1: Success after binutils/gcc: 8 commits discards 854bfcf368 236: onsuccess: #2173: 1: Success after binutils/gcc: 9 commits discards 3315db42e5 235: onsuccess: #2172: 1: Success after binutils/gcc: 16 commits discards 903dcafed5 234: onsuccess: #2171: 1: Success after binutils/gcc: 11 commits discards 171588a8e0 233: onsuccess: #2170: 1: Success after gcc: 5 commits discards 4c28d98816 232: onsuccess: #2169: 1: Success after binutils: 4 commits discards 07c8e3b22a 231: onsuccess: #2168: 1: Success after gcc: 2 commits discards 118ed8c3e1 230: onsuccess: #2167: 1: Success after binutils/gcc: 2 commits discards ff89097be7 229: onsuccess: #2166: 1: Success after basepoints/gcc-13-34 [...] new 736f23cf64 229: onsuccess: #2166: 1: Success after basepoints/gcc-13-34 [...] new 17497c4b87 230: onsuccess: #2167: 1: Success after binutils/gcc: 2 commits new 850e06fab9 231: onsuccess: #2168: 1: Success after gcc: 2 commits new c8e41d8b27 232: onsuccess: #2169: 1: Success after binutils: 4 commits new 90237241f6 233: onsuccess: #2170: 1: Success after gcc: 5 commits new f2d0e4c695 234: onsuccess: #2171: 1: Success after binutils/gcc: 11 commits new 4862e146df 235: onsuccess: #2172: 1: Success after binutils/gcc: 16 commits new 420fca1fec 236: onsuccess: #2173: 1: Success after binutils/gcc: 9 commits new 5e53db1233 237: onsuccess: #2174: 1: Success after binutils/gcc: 8 commits new cbd47d58a1 238: onsuccess: #2175: 1: Success after binutils/gcc: 14 commits new b378cae317 239: onsuccess: #2176: 1: Success after binutils/gcc: 8 commits new 58556f6e24 240: onsuccess: #2177: 1: Success after binutils/gcc: 6 commits new 892d727c72 241: onsuccess: #2178: 1: Success after binutils/gcc: 7 commits new f398f68fdd 242: onsuccess: #2179: 1: Success after binutils/gcc: 16 commits new 28f1e453b7 243: onsuccess: #2180: 1: Success after binutils/gcc: 4 commits new 5e4f5731a7 244: onsuccess: #2181: 1: Success after binutils/gcc: 7 commits new 18e77899b1 245: onsuccess: #2182: 1: Success after binutils/gcc: 6 commits new 342f549156 246: onsuccess: #2183: 1: Success after binutils/gcc: 8 commits new 9ba6cd5fb5 247: onsuccess: #2184: 1: Success after binutils/gcc: 7 commits new 89b791307c 248: onsuccess: #2185: 1: Success after binutils/gcc: 7 commits new f1b1bfd8f7 249: onsuccess: #2186: 1: Success after binutils/gcc: 7 commits new 39e86b90e9 250: onsuccess: #2187: 1: Success after binutils/gcc: 10 commits new 79b35ad251 251: onsuccess: #2188: 1: Success after binutils/gcc: 11 commits new 4f319c27fe 252: onsuccess: #2191: 1: Success after binutils/gcc: 29 commits new c4d3bacac4 253: onsuccess: #2192: 1: Success after gdb-12-branchpoint-2 [...] new 04f826bba6 254: onsuccess: #2193: 1: Success after gdb-12-branchpoint-2 [...] new c93b8ecfa3 255: onsuccess: #2194: 1: Success after basepoints/gcc-13-35 [...] new dedb5ae109 256: onsuccess: #2195: 1: Success after gdb-12-branchpoint-2 [...] new 463fc52567 257: onsuccess: #2196: 1: Success after binutils/gcc: 2 commits new 4610710475 258: onsuccess: #2197: 1: Success after binutils/gcc: 5 commits new 94229bfd4e 259: onsuccess: #2198: 1: Success after binutils/gcc: 8 commits new cfb55b907b 260: onsuccess: #2199: 1: Success after binutils/gcc: 18 commits new d1f5cd6059 261: onsuccess: #2200: 1: Success after binutils/gcc: 8 commits new 3feed46ae4 262: onsuccess: #2201: 1: Success after gcc: 6 commits new 281b148b4f 263: onsuccess: #2202: 1: Success after binutils/gcc: 5 commits new fa7e735d09 264: onsuccess: #2203: 1: Success after gcc: 9 commits new a67f8e31ba 265: onsuccess: #2204: 1: Success after binutils/gcc: 5 commits new 385bca2bfc 266: onsuccess: #2205: 1: Success after binutils/gcc: 8 commits new 6a2cf832e1 267: onsuccess: #2206: 1: Success after binutils/gcc: 5 commits new 21863558bd 268: onsuccess: #2207: 1: Success after binutils/gcc: 12 commits new 930f359d4a 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits new 43a6de8b40 270: onsuccess: #2209: 1: Success after gcc: 2 commits new 71e101b9df 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits new 240e6fcfda 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits new 0f70b9d049 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits new bc8a1c09b0 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits new 753e3ca5a9 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits new 1a7f5c35c8 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits new ae2467d4c5 277: onsuccess: #2216: 1: Success after binutils: 2 commits new e1ea602fad 278: onsuccess: #2217: 1: Success after binutils: 7 commits new b4247fd6b4 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-36 [...] new a149111129 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits new 2456633f9d 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits new 3262e699f0 282: onsuccess: #2221: 1: Success after gcc: 2 commits new c9614de6b7 283: onsuccess: #2222: 1: Success after gcc: 4 commits new dc21dc4b7a 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits new 73d9556179 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits new 8659b7ed2b 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits new 6d37bd02a6 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits new 29471847db 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new 7419111566 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits new 1378a6a51b 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits new fc28b0bf42 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits new a1ffe4c305 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits new 3b35ae73cd 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits new f7eddd0156 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits new a5c134c16a 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits new 1721b18093 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new 8f964c7f28 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new f18a7b9ce3 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new 7d5d623937 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new 0fd0c42bf1 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new 0634fdf0ed 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new 1d76b6e281 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new 779bc1c29d 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new 97557c7832 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new 35b10dde96 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new e86d1205fd 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint-2 [...] new db0425a4d0 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint-2 [...] new 9a36bea52d 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint-2 [...] new 9748ed0103 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint-2 [...] new 668cbfb0d0 310: onsuccess: #2259: 1: Success after binutils: 2 commits new d6d54d2d23 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint-2 [...] new ee6e9d3627 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 297aa89bd1 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new 3856920f2e 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new 809ad91cf6 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new 0179b20173 316: onsuccess: #2270: 1: Success after gcc: 2 commits new ca62316080 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new f97abda315 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 62b6702171 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new f80d1ea8fd 320: onsuccess: #2274: 1: Success after gcc: 5 commits new be77b01e0e 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new a2ce0fc95a 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new e70efc30d1 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 53de1d89a2 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new eeb541c702 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 252e13e2bf 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new 3275dcf22f 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 8f236db5f9 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint-2 [...] new 486c0941dd 329: onsuccess: #2285: 1: Success after gcc: 8 commits new ce5323cdd5 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 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 (56b37ffcf8) \ 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 1728 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 40340 -> 40328 bytes 04-build_abe-gcc/console.log.xz | Bin 214516 -> 216968 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3892 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2616 -> 2652 bytes 07-check_regression/console.log.xz | Bin 7876 -> 6128 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 13 +- 07-check_regression/mail-body.txt | 64 +- 07-check_regression/results.compare | 36 +- 07-check_regression/results.compare2 | 551 +--- 07-check_regression/results.regressions | 36 +- 08-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 66 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 36 +- sumfiles/g++.log.xz | Bin 3644500 -> 3599864 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 3155696 -> 3146792 bytes sumfiles/gcc.sum | 4812 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1046124 -> 1044556 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219200 -> 219024 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451452 -> 452596 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 2751 insertions(+), 3145 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_check_bootstrap/release-arm-check_bootstrap updated (a7267a4be8 -> f2d4906f9d)

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_bootstrap/release-arm-check_bootstrap in repository toolchain/ci/base-artifacts. from a7267a4be8 32: onsuccess: #155: 1: Success after binutils/gcc: 10 commits new f2d4906f9d 33: onsuccess: #156: 1: Success after binutils/gcc: 10 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 1716 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 52544 -> 51068 bytes 04-build_abe-bootstrap/console.log.xz | Bin 465492 -> 466856 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3828 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2972 -> 3108 bytes 07-check_regression/console.log.xz | Bin 4892 -> 4924 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 35 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 2854372 -> 2807904 bytes sumfiles/g++.sum | 142 +- sumfiles/gcc.log.xz | Bin 2466952 -> 2468864 bytes sumfiles/gcc.sum | 4868 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 935260 -> 942648 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2304 -> 2304 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207256 -> 207212 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2728 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 473640 -> 461892 bytes sumfiles/libstdc++.sum | 10 +- 27 files changed, 2609 insertions(+), 2606 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/release-arm-bootstrap_debug updated (07a4e21070 -> 66e69e81da)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug in repository toolchain/ci/base-artifacts. from 07a4e21070 32: onsuccess: #155: 2: Success after binutils/gcc: 10 commits new 66e69e81da 33: onsuccess: #156: 2: Success after binutils/gcc: 10 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 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 52036 -> 52940 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 462308 -> 463336 bytes 06-check_regression/console.log.xz | Bin 2808 -> 2908 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- manifest.sh | 20 ++++++++++---------- 9 files changed, 13 insertions(+), 13 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-aarch64-lts-allnoconfig updated (4d8e92278d -> c34111f3ad)

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-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 4d8e92278d 21: onsuccess: #474: boot: Success after binutils/llvm/qemu: [...] new c34111f3ad 22: onsuccess: #475: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30860 -> 31736 bytes 04-build_kernel_llvm/console.log.xz | Bin 66440 -> 65368 bytes 05-build_abe-qemu/console.log.xz | Bin 32412 -> 31180 bytes 06-build_linux/console.log.xz | Bin 3352 -> 3364 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3900 -> 4440 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allnoconfig updated (933b7cb0f7 -> 88a2d70e49)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 933b7cb0f7 22: onsuccess: #244: all: Success after binutils/qemu: 37 commits new 88a2d70e49 23: onsuccess: #245: all: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1692 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30068 -> 30084 bytes 04-build_kernel_llvm/console.log.xz | Bin 64448 -> 65148 bytes 05-build_abe-qemu/console.log.xz | Bin 32132 -> 30944 bytes 06-build_linux/console.log.xz | Bin 3428 -> 3428 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3300 -> 4248 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (36bdd7eb49 -> 668ba4031a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 36bdd7eb49 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 4b79ce8a09 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards a3529a00b1 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 954658d918 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 25ca9dc340 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 7429bbe90e 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 495deb9955 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 7e8350ed19 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards ce6afb7a90 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards f59d32eeea 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 8f5bcb2cdb 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 780d841699 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 51a1c3bce5 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards d97330c9d6 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards c142a08264 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 8df4275e9e 92: onsuccess: #575: 1: Success after linux: 34 commits discards 56404bda13 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 46edf05259 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 3e1d86bf28 89: onsuccess: #570: 1: Success after linux: 11 commits discards d9a8d91029 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 74e94904c2 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 99dcf97145 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 5f87a3c9bc 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards ea0fcb6f63 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 31a72aca3a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards b327b4b92e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 06bd4c0250 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards e1c2f4ea3f 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 04e5573a3a 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 3875d8918b 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards d0156a255c 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 4af6444f9e 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 733726095b 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 1190b00d1c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 600950e063 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 97dd94fd41 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 6adc9073f9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 22ef809bfb 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards bcd630e1b2 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 513758380b 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 4404a9a057 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards c63e232f4c 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 3f3b2a9da6 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 4d2419c12b 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards d6c98c7274 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards f3c0c223cb 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards bf669c3527 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards de857ee181 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 9a87ddc45b 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 97473bb138 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 3da1fb3cbc 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards be2d1d8787 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards ea40d9ed7b 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 3299e19375 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 169d0130e4 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 2819bb557d 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 84238ea724 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 2f581cbfce 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 1ad35f0736 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 00a05ed7bc 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards d93182586f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 7f22e8f203 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 247cfe95f2 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 8b1b807366 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 8dae927960 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 6dc24c3733 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards e846ccb5e3 41: onsuccess: #514: 1: Success after linux: 64 commits discards f306ee8053 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 760ad34f29 39: onsuccess: #511: 1: Success after binutils: 8 commits discards cf52af0506 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 1563b9c851 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards db418681ed 36: onsuccess: #505: 1: Success after glibc: 3 commits discards cb9a98c86a 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 308ddd570a 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards f101e78d5d 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 234d81bf5b 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 51f63a324a 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 1e33c13ee9 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards fa00a7e1df 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 09aaabba77 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 96035bc2e4 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 9e712a6c6d 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards a44a178fd9 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards f66e4f08a0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards ec53d3d88d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards e2188a4b54 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards a259b3e853 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 41a230dc9d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0a6f04bee1 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1cec99ab96 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 61e0ce5440 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ebe95edac8 16: onsuccess: 1: Successful build after binutils: 4 commits discards c2da457e6c 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 28b1e7cfec 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ec804e0b0d 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5134493b6 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5edfc42f2b 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 40b5deb2df 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e863e8c536 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fa4a640749 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9c68dfa7de 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cc4f39a23c 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 36b95f2a69 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 69ed808efa 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9dd5d35ea3 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 713c59108f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e3940b400 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fbeb692901 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9296b48aa9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5439856d79 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5fa12a764 16: onsuccess: 1: Successful build after binutils: 4 commits new c166289066 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7bf6175d66 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5a58cd66cc 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 45058311d9 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f81e4f9caa 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50eb77d410 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new b5ed8468c6 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5b490c5a82 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 8be5b1effa 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 52de82f9db 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 0a30f713d8 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 33c9a812fa 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new df8a006f6c 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new a0a79c33c5 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 1f7a28ac47 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 751d16c613 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 9e23ef111b 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new ae53fc446d 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new cc65699a93 35: onsuccess: #503: 1: Success after binutils: 11 commits new e5fd55e5eb 36: onsuccess: #505: 1: Success after glibc: 3 commits new 48bce7cd1d 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new fa4de52c0a 38: onsuccess: #508: 1: Success after binutils: 3 commits new 71ba9f66bc 39: onsuccess: #511: 1: Success after binutils: 8 commits new 8e0b9ba28d 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 2066cba80d 41: onsuccess: #514: 1: Success after linux: 64 commits new 0d0f247b1c 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 76dc2b55db 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new be011e853a 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 5da6d10f34 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 79d8eac418 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new b121a93594 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 2f294dbc58 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new b5e8a7f26f 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 13cc3ea22e 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 480b2a41f2 51: onsuccess: #525: 1: Success after binutils: 8 commits new ceaec79148 52: onsuccess: #528: 1: Success after binutils: 8 commits new ac7367f427 53: onsuccess: #531: 1: Success after binutils: 12 commits new 422e84d29a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new b96dee6e3a 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new b350f5abe6 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 9e94cad1cf 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new eb962c875f 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 1459ee8e2f 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 9bd0b32d6d 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new f2da2285a4 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 6fe6103c1a 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new c592ae3551 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 5d93d24849 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 57762032cd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new f37f0006c0 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e5b09a01b1 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 4aa6da2055 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new b9f5146236 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 6811b2353b 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 7959fab7d9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new d2bc750403 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 4476589738 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 4f9075ccbf 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 6a9277b000 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 7c0db87b2a 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 0ee12b00b8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new d5b1c68dc0 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 23a2e44bf0 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 489f47bc01 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new f7263bc448 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new da52189e18 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 56c2be42c9 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new eba248d942 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 71b477fb8b 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new b09efb9075 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 2c56672076 87: onsuccess: #567: 1: Success after binutils: 8 commits new 4c0d27f88e 88: onsuccess: #569: 1: Success after glibc: 10 commits new d0374efbc6 89: onsuccess: #570: 1: Success after linux: 11 commits new 9b6cbe95f6 90: onsuccess: #572: 1: Success after binutils: 15 commits new 55b05114cd 91: onsuccess: #574: 1: Success after glibc: 3 commits new e912af799b 92: onsuccess: #575: 1: Success after linux: 34 commits new b498f589c8 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 9e37d22a2a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 929f839c27 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 8b9bb52389 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 09d7fc3674 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 89f1d325f9 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new cb26254986 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 1d95a0b1f7 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 70e0aaa658 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new fb001163cc 102: onsuccess: #586: 1: Success after binutils: 5 commits new a813ee454d 103: onsuccess: #589: 1: Success after binutils: 3 commits new 8e5cabc6d0 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 1a8da83d40 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new dc8c26ee60 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 48972e4794 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 668ba4031a 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] 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 (36bdd7eb49) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 53296 -> 53412 bytes 04-build_abe-gcc/console.log.xz | Bin 236832 -> 236148 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9200 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 236028 -> 235844 bytes 08-build_abe-gdb/console.log.xz | Bin 50916 -> 51736 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2624 -> 2276 bytes 11-check_regression/console.log.xz | Bin 11888 -> 15036 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 132 +- 11-check_regression/mail-body.txt | 213 +- 11-check_regression/results.compare | 162 +- 11-check_regression/results.compare2 | 5066 ++++++++++--------- 11-check_regression/results.regressions | 168 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 215 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 168 +- sumfiles/gdb.log.xz | Bin 1728584 -> 1790664 bytes sumfiles/gdb.sum | 8212 ++++++++++++++----------------- 30 files changed, 7197 insertions(+), 7251 deletions(-) -- 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 November 2022