Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-defconfig updated (0764418340 -> 8ea2c60772)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-defconfig in repository toolchain/ci/base-artifacts. from 0764418340 22: onsuccess: #66: boot: Success after binutils/llvm/qemu: [...] new 8ea2c60772 23: onsuccess: #67: 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 1704 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31020 -> 30620 bytes 04-build_kernel_llvm/console.log.xz | Bin 66248 -> 66180 bytes 05-build_abe-qemu/console.log.xz | Bin 31552 -> 32144 bytes 06-build_linux/console.log.xz | Bin 3528 -> 3588 bytes 07-boot_linux/console.log.xz | Bin 6136 -> 6132 bytes 08-check_regression/console.log.xz | Bin 3940 -> 3868 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, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allnoconfig updated (37849a8df2 -> 78060de68f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allnoconfig in repository toolchain/ci/base-artifacts. from 37849a8df2 21: onsuccess: #411: boot: Success after binutils/gcc/linux/ [...] new 78060de68f 22: onsuccess: #412: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1900 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30268 -> 30480 bytes 04-build_abe-stage1/console.log.xz | Bin 68356 -> 68336 bytes 05-build_abe-qemu/console.log.xz | Bin 31240 -> 31868 bytes 06-build_linux/console.log.xz | Bin 3040 -> 3740 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4104 -> 3964 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 33 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-allnoconfig updated (f1ce5c745a -> 90d7768f01)

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-allnoconfig in repository toolchain/ci/base-artifacts. from f1ce5c745a 22: onsuccess: #381: all: Success after binutils/gcc/linux/q [...] new 90d7768f01 23: onsuccess: #382: all: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29732 -> 30240 bytes 04-build_abe-stage1/console.log.xz | Bin 87100 -> 87568 bytes 05-build_abe-qemu/console.log.xz | Bin 31348 -> 31296 bytes 06-build_linux/console.log.xz | Bin 3172 -> 3384 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4104 -> 3912 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

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

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 59b2fca441 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 0c450100d5 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] discards 02c0bbdbd6 194: force: #1853: 7: Success after gcc: 26 commits discards 4a6cddaf44 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards 4ed0672e07 192: onsuccess: #1848: 7: Success after linux: 213 commits discards f9394804ae 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 82c2845682 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards fb32d787a4 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards ae543da45f 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards 37dc3c2154 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards 04bbbd9b6d 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards f2b4007736 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] discards eb01ea05a4 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] discards f6a4d72bc4 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] discards c0dfee6e12 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits discards cac3aa725f 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] discards e2d73b5260 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] discards 65388c2450 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] discards ef7e527b1a 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] discards 6bfbf0e78a 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] discards ae00a1aaac 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] discards ea2529677c 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] discards de5ce5c021 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] discards 34b57a5a6b 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] discards 62d893866c 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards d342c9f0d1 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] discards bdd8c80399 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] discards 2a922bc5a5 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] discards d6e3306971 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards 0038f75b8d 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 10088170ad 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards 4d10c19a4a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards 0c4681c204 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards 3b08c13118 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards 7ec9a4a14c 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards c3a0802928 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards 5079fb0f93 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards 9f0db99aa1 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards 3a21763ca7 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards ad3f10ce96 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 6196c5337d 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 65e426c7c6 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards 08dd62c66b 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 0c5ff29de7 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards aa2f5309c5 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards 143369cc25 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 5d6f5b58bd 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 096780acc5 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 52e2bb46cb 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards d3f79da9c1 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 3accb3a201 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 342f2ccd84 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 2de125b66c 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards e74262a521 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 06a87af61b 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 07a5daa1fb 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards b19c2e6049 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 5fae420d7d 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 83cbcb29fa 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 080414fbcf 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 287f521f66 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards c56cf2746f 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 3dfe433e2e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 44f03966f3 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 9e0923fb20 132: onsuccess: #1645: 7: Success after linux: 23 commits discards af4c785411 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 8d214b9c74 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 38ce97e05b 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 9161ad8040 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards dfb6208db5 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards b7f64b908c 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 082b5f446f 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards eb39a24fd0 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 41e556a4e1 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards a246a434be 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 9e32067533 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 4b4f5e977b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards b289421e86 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards fb5ec03cd3 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 5f01c56cb8 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 88d052fb67 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 35af827aea 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 14667e3a37 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 5867a7e229 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards b3236611ca 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 9cfc7b1fd0 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards bb665730e6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards e6722e5b60 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards d90550b12b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 1e3ef25e7d 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards b1735755ee 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 374554ac16 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 6c41028305 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 4805b8a912 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 8c82dd99ca 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 8a6559c50c 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 3a97ef4c36 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 5eebb005c8 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 8a54a5cde5 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 5f7d709358 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards a24e4da003 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 3a840a696a 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 3106e56ce4 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 8acccadcb2 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 13b765a3ad 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new b6933c1782 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new c0a45da563 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 2b5b9da485 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new d9e40b5baa 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 447debf889 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new c73d260d2e 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new a496eff643 106: onsuccess: #1617: 7: Success after gcc: 2 commits new bd1ac62678 107: onsuccess: #1618: 7: Success after gcc: 2 commits new cec8fa4e51 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new f0e6647737 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 3ede723d31 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new a71f367356 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new d333678ea2 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 314cc0229f 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 3db832a292 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new a12b75a62f 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new a9d3046bbb 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 75e1d0004f 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new f0c9ee5560 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 4c55d745bc 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new b8b2ee3786 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 6cc3088167 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 2108829382 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 914d3e41c5 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 178e208a81 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new c42e42255d 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 80c3a0213f 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 41ae594758 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 9a6a9cc810 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new feb1073627 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 04f629b860 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 0545ecf8a4 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 76e9852da7 132: onsuccess: #1645: 7: Success after linux: 23 commits new 32842e4ad4 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 2956d10e82 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new bda9fe21c9 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 81e2d62a37 136: onsuccess: #1650: 7: Success after binutils: 2 commits new f2097962c0 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new b7295e9329 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 686a7d2d48 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 2689af2ed1 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 3d3679126f 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 31a550bc19 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 462a324b69 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new a194364fd1 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 4c5b33f079 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new c14919c3ff 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new d6a81de2c5 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 105b5b26c4 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 2c2880bef5 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 014cf914cd 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 83abd3201a 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 8150bbc68f 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new c3551d2ab2 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 5299591030 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 372c15f3f4 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 251506e4e1 156: onsuccess: #1671: 7: Success after gcc: 3 commits new dab9a3c9e6 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 8c45a821d9 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new c1c54fd263 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new c30fdb2ed2 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new c80a2f5805 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new cc4d2dacf6 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new 946224f2bc 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new 6974a3be6a 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new 5476dc2d9a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new 56a05e1325 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new c3625145d2 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 005dc069db 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new d3c8d78d1d 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] new 77fa9e55fc 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] new 8a83ac0f61 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] new fedfceb0c9 172: onsuccess: #1687: 7: Success after gcc: 11 commits new df3421eab5 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] new 3432ff2e19 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] new fbc65997bc 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] new e62f5b1f68 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] new 52c71b7cb4 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] new 662755a962 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] new 5f112ca778 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] new a0947a26f9 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] new 67eb56ed20 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new 227c8842bc 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits new 1cdf13c92e 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new 006cc1f769 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] new 030f9044e2 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new 0f9f6ac72f 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new 8bf8e9de39 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new 87fb6da03d 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new 384a3455d6 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new 7f97376a9a 190: onsuccess: #1834: 7: Success after binutils: 25 commits new af274f21d7 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 9826523b9a 192: onsuccess: #1848: 7: Success after linux: 213 commits new db75d51844 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new 655dd98356 194: force: #1853: 7: Success after gcc: 26 commits new 301ae6843f 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] new 309ec12528 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 1ba0dae38e 197: onsuccess: #1856: 4: 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 (59b2fca441) \ 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 1668 -> 1896 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30364 -> 30268 bytes 05-build_abe-stage1/console.log.xz | Bin 90132 -> 91080 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8736 -> 8332 bytes 08-build_abe-glibc/console.log.xz | Bin 236564 -> 236244 bytes 09-build_abe-stage2/console.log.xz | Bin 202160 -> 220564 bytes 12-check_regression/console.log.xz | Bin 2940 -> 4136 bytes 12-check_regression/mail-body.txt | 9 ----- 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 11 +----- mail/mail-subject.txt | 2 +- manifest.sh | 35 ++++++++++-------- 20 files changed, 63 insertions(+), 76 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-master-arm-spec2k6-O3 updated (d96eea92c6 -> 3bc818f86a)

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_gnu_tk1/gnu-master-arm-spec2k6-O3 in repository toolchain/ci/base-artifacts. from d96eea92c6 24: force: #503: 1: [TCWG CI] No change after gcc: 71 commits new 3bc818f86a 25: force: #504: 1: [TCWG CI] No change after basepoints/gcc [...] 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 1812 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31640 -> 31160 bytes 04-build_abe-stage1/console.log.xz | Bin 93836 -> 92480 bytes 06-build_abe-linux/console.log.xz | Bin 8780 -> 8768 bytes 07-build_abe-glibc/console.log.xz | Bin 238096 -> 237908 bytes 08-build_abe-stage2/console.log.xz | Bin 217104 -> 212804 bytes 09-benchmark/benchmark-build.log | 112 +- 09-benchmark/benchmark.log | 110 +- 09-benchmark/console.log.xz | Bin 3820 -> 3828 bytes 10-check_regression/console.log.xz | Bin 15756 -> 15676 bytes .../csv-results-vs-first-1/md5sum.csv | 2713 +- .../csv-results-vs-first-1/perf.csv | 3340 +- .../csv-results-vs-first-1/results.csv | 15081 +- .../csv-results-vs-first-1/size.csv | 470692 ++++++++-------- .../csv-results-vs-first-1/vect.csv | 370 +- .../csv-results-vs-prev-0/md5sum.csv | 2936 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3315 +- .../csv-results-vs-prev-0/results.csv | 18296 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 526542 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 1197 +- .../csv-results-vs-prev-1/md5sum.csv | 2713 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3340 +- .../csv-results-vs-prev-1/results.csv | 15081 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 470692 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 370 +- 10-check_regression/results-vs-first-brief.csv | 64 +- 10-check_regression/results-vs-first-full.csv | 3114 +- 10-check_regression/results-vs-first-internal.csv | 241 +- 10-check_regression/results-vs-first.csv | 241 +- 10-check_regression/results-vs-first.log | 1364 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 5 +- 10-check_regression/results-vs-prev-full.csv | 3432 +- 10-check_regression/results-vs-prev-internal.csv | 247 +- 10-check_regression/results-vs-prev.csv | 247 +- 10-check_regression/results-vs-prev.log | 1598 +- 10-check_regression/skipped-symbols.txt | 33 + 11-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../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 +- .../454.calculix/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 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/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 | 122 +- git/gcc_rev | 2 +- mail/jira-body.txt | 11 +- mail/mail-body.txt | 11 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results_id | 2 +- 83 files changed, 789432 insertions(+), 758610 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (d446919534 -> f4c63db5e3)

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_binutils/master-arm in repository toolchain/ci/base-artifacts. discards d446919534 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 74ef522aba 100: onsuccess: #521: 1: Success after binutils: 10 commits discards b55b1649f8 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards e639de8ac3 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 073e726bda 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 3a769a937d 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 2ffb45c4bc 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 7471bd6341 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 9f321864ca 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 6933d23556 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 04c1520ef6 91: onsuccess: #511: 1: Success after linux: 27 commits discards 41805c7bd5 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 2551fe2b6c 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 75076ec5a9 88: onsuccess: #506: 1: Success after linux: 34 commits discards 7f6683cc29 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 5196c98c0f 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 9666a7de38 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards c49022079d 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards fbaa47da67 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards cc2af9b82b 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 6c7adaa175 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 43ca493fda 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 9560df2b4f 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 722b301c1f 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 6f4b19b52a 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards b3f287ce8e 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 5a66bf2d64 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 2a51eb64d1 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards b71e4a385b 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards ebd82d0c4c 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards ee6eefdd08 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 50d95b50e1 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 2fd096b250 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 85bf592cd4 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards cf1129fdae 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards a77ba24642 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 661e9a5615 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 833859f37b 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 564e22662a 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards b910d15112 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 47073298ae 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 37b3fb1ef3 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards abcc947377 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 813720dea7 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 07320feb02 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 7c8660a707 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 4e52748336 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 1bfea7b0d4 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 07abc7a35e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards d3e4d44bd4 52: onsuccess: #467: 1: Success after binutils: 9 commits discards f7a91cc7e7 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 9012ab2342 50: onsuccess: #461: 1: Success after binutils: 12 commits discards d472fd487a 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 5c4f807c34 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 3b5e0de740 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 1984ccf523 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards c21d35277d 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards a8b84d60fc 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards f9dd7ecc93 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 9e6fd0e336 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 0ea9b13baf 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 0b3171d122 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 6f506d655c 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 13627e17d3 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 81122cf4fa 37: onsuccess: #443: 1: Success after binutils: 2 commits discards e630f5b80e 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards f0ea52416d 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards fb7b37f545 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards dee4d14dfc 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 53e33751e9 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 37ce1f5e5d 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards bad675f21a 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards b3d5ab25f0 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 45f5c176d6 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards d9f5dfdd07 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards c19ddc44bb 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 9b0eeb66eb 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards f0fcdb3b5e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards b183ceb05c 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 87533de764 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 29b0856c9b 21: onsuccess: 1: Successful build after linux: 79 commits discards 05f39940fa 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 40d0650d75 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f12583a674 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 867cace1f4 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7432dea941 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7f69835f61 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e7d1aecd5b 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 129404d9c6 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a8c6f8fc38 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cbcc538fa8 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d8506a106f 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce907df869 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ac1541867c 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5341e1fd28 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b6e00aff51 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 8af29f3db4 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 2e6cf7324d 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 1f5824e3f3 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards fd12045593 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3b4dbd5279 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a3d0da73c8 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8a32a5e073 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6653052042 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new caa062a71f 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 253267125b 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8142dd1c64 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 44a611f4ac 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5a84c4bf58 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a3bba6cb86 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new caae9173d6 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8e7c076251 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e7c148b8b0 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 281a451058 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce12390a33 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dc17a8fcf3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1bd3feb0e4 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2228e3d7e 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fe87497ff6 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 934c410ddd 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 78ee892fec 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a6f76425e8 21: onsuccess: 1: Successful build after linux: 79 commits new 5ceae8cac0 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4601a79c10 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5e32853e71 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 12812f7d73 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 9d78cfeed2 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 7e503bdb02 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 3592780831 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 7112616d1d 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 599a22e69a 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new dfbc7b50d3 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 8322194978 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 6393f4cdee 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new b5f2698c21 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 072c740d53 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 994a07d4fa 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new cba4e21449 37: onsuccess: #443: 1: Success after binutils: 2 commits new 9b3ef471eb 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 7474c543d0 39: onsuccess: #447: 1: Success after binutils: 5 commits new f7147372d5 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 78509d1cfe 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 091561f41f 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 3f7775d4b0 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new a64294ba36 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 1047ad4756 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new ac0305f710 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 9b10387565 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new c290746073 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 16e1d06a2f 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 6a078d7aa1 50: onsuccess: #461: 1: Success after binutils: 12 commits new c9f5e7941b 51: onsuccess: #464: 1: Success after binutils: 6 commits new 058088da88 52: onsuccess: #467: 1: Success after binutils: 9 commits new c8491190b5 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 8c5e88ae0c 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 2244f8f8cb 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 145d32ef0d 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 9e774d7647 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 13aa38525e 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new f5b3464335 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new c48595b2bd 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new f76e29e8bd 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 693f66f9a9 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new bf411b97d4 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 913735cb14 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new c9d976099b 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new c85b334353 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 37a11cf4c1 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 6ebff0dec5 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 2f536f2812 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 9e72b75cd3 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 94e24ee30f 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 95a01b11a3 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 8066feea11 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 129d0996be 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 3b164ffbef 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 9f3bd6841c 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 3ee1ba3ea8 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 35008fab77 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new a47801432f 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new d9523af140 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 2d9ee5b2d3 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new ce4ec1cfb7 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new c246bc8907 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new b44e86a2af 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 7042d3355a 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 152a7562d0 86: onsuccess: #503: 1: Success after binutils: 12 commits new ab6eaca20f 87: onsuccess: #505: 1: Success after glibc: 7 commits new f23cc67c8f 88: onsuccess: #506: 1: Success after linux: 34 commits new d9c54f0258 89: onsuccess: #508: 1: Success after binutils: 12 commits new 8212827aad 90: onsuccess: #510: 1: Success after glibc: 5 commits new db872b583c 91: onsuccess: #511: 1: Success after linux: 27 commits new c8d287b24d 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 016b80c424 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new edde6dddd8 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new ddd9bae991 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new af520a1496 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 2392881092 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 15d9859c6e 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new aaeba419ef 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 57c2437e3b 100: onsuccess: #521: 1: Success after binutils: 10 commits new 8c7520995b 101: onsuccess: #524: 1: Success after binutils: 2 commits new f4c63db5e3 102: onsuccess: #527: 1: Success after binutils: 5 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 (d446919534) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1616 -> 1620 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 50920 -> 51160 bytes 04-build_abe-gcc/console.log.xz | Bin 233012 -> 233916 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9808 -> 9692 bytes 07-build_abe-glibc/console.log.xz | Bin 236112 -> 235008 bytes 08-build_abe-gdb/console.log.xz | Bin 50960 -> 51028 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3860 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2112 -> 2272 bytes 11-check_regression/console.log.xz | Bin 4456 -> 4700 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/binutils.log.xz | Bin 62696 -> 62476 bytes sumfiles/binutils.sum | 65 +++--- sumfiles/gas.log.xz | Bin 97916 -> 98040 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 131436 -> 131440 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 26 files changed, 404 insertions(+), 395 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-master-arm-spec2k6-Oz updated (36020a40cf -> e83c398cdd)

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_apm/llvm-master-arm-spec2k6-Oz in repository toolchain/ci/base-artifacts. from 36020a40cf 40: onsuccess: #261: 1: [TCWG CI] No change after binutils: [...] new e83c398cdd 41: onsuccess: #263: 1: [TCWG CI] No change after v6.0.8-416 [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30404 -> 30784 bytes 04-build_abe-stage1/console.log.xz | Bin 90412 -> 89972 bytes 06-build_abe-linux/console.log.xz | Bin 8028 -> 7904 bytes 07-build_abe-glibc/console.log.xz | Bin 237124 -> 237300 bytes 08-build_abe-stage2/console.log.xz | Bin 208544 -> 208332 bytes 09-build_llvm-true-false-/console.log.xz | Bin 62396 -> 61444 bytes 10-benchmark/benchmark-build.log | 84 +- 10-benchmark/benchmark.log | 82 +- 10-benchmark/console.log.xz | Bin 3824 -> 3824 bytes 11-check_regression/console.log.xz | Bin 10660 -> 10120 bytes .../csv-results-vs-first-1/md5sum.csv | 1414 ++- .../csv-results-vs-first-1/perf.csv | 2535 +++--- .../csv-results-vs-first-1/results.csv | 7329 ++++++---------- .../csv-results-vs-first-1/size.csv | 4644 +++------- .../csv-results-vs-prev-0/md5sum.csv | 1410 ++- 11-check_regression/csv-results-vs-prev-0/perf.csv | 2548 +++--- .../csv-results-vs-prev-0/results.csv | 9255 ++++++++++++-------- 11-check_regression/csv-results-vs-prev-0/size.csv | 4644 +++++++--- 11-check_regression/csv-results-vs-prev-0/vect.csv | 6016 ++++++------- .../csv-results-vs-prev-1/md5sum.csv | 1414 ++- 11-check_regression/csv-results-vs-prev-1/perf.csv | 2535 +++--- .../csv-results-vs-prev-1/results.csv | 7329 ++++++---------- 11-check_regression/csv-results-vs-prev-1/size.csv | 4644 +++------- 11-check_regression/results-vs-first-brief.csv | 40 +- 11-check_regression/results-vs-first-full.csv | 2532 +++--- 11-check_regression/results-vs-first-internal.csv | 161 +- 11-check_regression/results-vs-first.csv | 161 +- 11-check_regression/results-vs-first.log | 638 +- 11-check_regression/results-vs-prev-brief.csv | 40 +- 11-check_regression/results-vs-prev-compare.csv | 6 +- 11-check_regression/results-vs-prev-full.csv | 2686 +++--- 11-check_regression/results-vs-prev-internal.csv | 161 +- 11-check_regression/results-vs-prev.csv | 161 +- 11-check_regression/results-vs-prev.log | 710 +- 12-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/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 +- .../453.povray/results-metadata.json | 10 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/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 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/linux_rev | 2 +- mail/jira-body.txt | 12 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 67 files changed, 29400 insertions(+), 34119 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[gcc] branch master updated (ce51e8439a4 -> 3c6721796d8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from ce51e8439a4 doc: port new documentation from Sphinx new 3c6721796d8 libstdc++: Fix install-debug makefile target 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: libstdc++-v3/src/Makefile.am | 4 ++-- libstdc++-v3/src/Makefile.in | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (d41f3fd066 -> 59b2fca441)

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 d41f3fd066 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] discards c37bf07822 194: force: #1853: 7: Success after gcc: 26 commits discards 723be450f9 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards 3f55a6371c 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 8a2b6cb5d9 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 96421f36e8 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 96882c9c4e 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards cee9cae54a 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards cb8d33f884 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards 8f46b28f34 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards 02340dfe33 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] discards 9bd5e54873 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] discards ced17500a7 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] discards f09433a3f5 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits discards 4ded9f10a6 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] discards 959cfe0986 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] discards d3847b9def 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] discards 1328bdfba2 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] discards d060dc5e01 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] discards 3118aff35c 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] discards 7c4a1de14b 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] discards 8db8c03c00 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] discards f114867110 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] discards bb24daaaba 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 40e47481e8 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] discards f0272d78b2 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] discards d979dafb0d 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] discards 443707ccee 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards 706dd1841b 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 5b70d8982e 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards b84d47cf03 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards c5114bc423 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards f7e5c8f600 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards 84bb228b4a 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards ecc89ea82a 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards d95dd2557f 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards d0c649a0a3 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards 751c3599d7 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 5bb020a66c 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 9b92bb1848 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 8391576780 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards dbd6e0e59e 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 3a55f73a21 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 15fb2401a2 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards df1b45579e 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 18e1db2e6f 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 6b8f281c08 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 496dd146c4 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 03c6ad700f 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards c2ffd65205 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards d9a787cc7b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 5cd7135089 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 04e5a0c9f9 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 4dd8182dda 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards d08d3d31ac 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 8aefe22ffb 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards ede5a4239c 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards fdc6f871bf 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 618d768cd5 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 0a9b6b2c7b 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 33dfef1c3f 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards a8083e80c0 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 9b40e94213 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 7e3659c2db 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 5adc9e6b1a 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards c6f349a1b7 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards e5f9c0006e 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 55c803329e 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 7d24372614 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 255d5f9fb5 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 2036686e25 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 4a1d306a65 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 494e2b3b37 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards fc63dcfa89 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 2260c32749 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 9e62c4ea1b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 2a77a4868f 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 665a30f379 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards e62ca6ded2 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards bc90f3f6a7 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 9192c75ba4 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 23c5b574f9 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 7944e5d4fa 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 41a43dbf47 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards c5b887a093 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 39ced6b935 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards a33208ad59 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards b2ca67beb9 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 13e69dd028 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 7524524b6b 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards d672446229 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 5b2b406eef 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards d9570d5406 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 1df75c3685 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 0e3ce92da7 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards ac002067c7 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 44978d2987 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 563a2e6ab3 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards c0e96aef36 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards aaf683a1ee 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards fb58d7638b 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 061d70a38c 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new a24e4da003 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 5f7d709358 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 8a54a5cde5 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 5eebb005c8 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 3a97ef4c36 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 8a6559c50c 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 8c82dd99ca 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 4805b8a912 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 6c41028305 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 374554ac16 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new b1735755ee 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 1e3ef25e7d 107: onsuccess: #1618: 7: Success after gcc: 2 commits new d90550b12b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new e6722e5b60 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new bb665730e6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 9cfc7b1fd0 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new b3236611ca 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 5867a7e229 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 14667e3a37 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 35af827aea 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 88d052fb67 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 5f01c56cb8 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new fb5ec03cd3 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new b289421e86 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 4b4f5e977b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 9e32067533 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new a246a434be 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 41e556a4e1 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new eb39a24fd0 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 082b5f446f 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new b7f64b908c 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new dfb6208db5 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 9161ad8040 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 38ce97e05b 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 8d214b9c74 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new af4c785411 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 9e0923fb20 132: onsuccess: #1645: 7: Success after linux: 23 commits new 44f03966f3 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 3dfe433e2e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new c56cf2746f 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 287f521f66 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 080414fbcf 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 83cbcb29fa 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 5fae420d7d 139: onsuccess: #1654: 1: Success after gcc: 11 commits new b19c2e6049 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 07a5daa1fb 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 06a87af61b 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new e74262a521 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 2de125b66c 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 342f2ccd84 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 3accb3a201 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new d3f79da9c1 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 52e2bb46cb 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 096780acc5 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 5d6f5b58bd 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 143369cc25 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new aa2f5309c5 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 0c5ff29de7 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 08dd62c66b 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 65e426c7c6 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 6196c5337d 156: onsuccess: #1671: 7: Success after gcc: 3 commits new ad3f10ce96 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 3a21763ca7 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 9f0db99aa1 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new 5079fb0f93 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new c3a0802928 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new 7ec9a4a14c 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new 3b08c13118 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new 0c4681c204 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new 4d10c19a4a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new 10088170ad 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new 0038f75b8d 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new d6e3306971 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new 2a922bc5a5 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] new bdd8c80399 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] new d342c9f0d1 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] new 62d893866c 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 34b57a5a6b 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] new de5ce5c021 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] new ea2529677c 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] new ae00a1aaac 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] new 6bfbf0e78a 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] new ef7e527b1a 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] new 65388c2450 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] new e2d73b5260 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] new cac3aa725f 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new c0dfee6e12 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits new f6a4d72bc4 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new eb01ea05a4 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] new f2b4007736 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new 04bbbd9b6d 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new 37dc3c2154 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new ae543da45f 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new fb32d787a4 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new 82c2845682 190: onsuccess: #1834: 7: Success after binutils: 25 commits new f9394804ae 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 4ed0672e07 192: onsuccess: #1848: 7: Success after linux: 213 commits new 4a6cddaf44 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new 02c0bbdbd6 194: force: #1853: 7: Success after gcc: 26 commits new 0c450100d5 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] new 59b2fca441 196: onsuccess: #1855: 4: Success after gcc: 30 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 (d41f3fd066) \ 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 1612 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30500 -> 30364 bytes 05-build_abe-stage1/console.log.xz | Bin 90376 -> 90132 bytes 07-build_abe-linux/console.log.xz | Bin 8760 -> 8736 bytes 08-build_abe-glibc/console.log.xz | Bin 236108 -> 236564 bytes 09-build_abe-stage2/console.log.xz | Bin 220384 -> 202160 bytes 12-check_regression/console.log.xz | Bin 3788 -> 2940 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 26 ++- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 9 - 12-check_regression/trigger-bisect | 2 - 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 72 ++++---- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 312 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 26 ++- mail/mail-subject.txt | 2 +- manifest.sh | 22 +-- results | 9 - 27 files changed, 75 insertions(+), 424 deletions(-) delete mode 100644 12-check_regression/results.regressions delete mode 100644 12-check_regression/trigger-bisect delete mode 100644 12-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap updated (8d50ae05aa -> 53ee24ec80)

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/master-aarch64-check_bootstrap in repository toolchain/ci/base-artifacts. from 8d50ae05aa 93: onsuccess: #631: 1: Success after binutils: 2 commits new 53ee24ec80 94: onsuccess: #634: 1: Success after binutils: 5 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 1728 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 38008 -> 37956 bytes 04-build_abe-bootstrap/console.log.xz | Bin 271112 -> 269816 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3840 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2676 -> 2664 bytes 07-check_regression/console.log.xz | Bin 4224 -> 4328 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 3681208 -> 3676712 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 3242404 -> 3237276 bytes sumfiles/gcc.sum | 4906 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1094184 -> 1092972 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2348 -> 2352 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 224716 -> 224944 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 472668 -> 469308 bytes sumfiles/libstdc++.sum | 10 +- 29 files changed, 2574 insertions(+), 2574 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022