Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[linux] branch master updated (f3e8416619ce -> ce19275f0103)

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 linux. from f3e8416619ce Merge tag 'soc-fixes-6.1-5' of git://git.kernel.org/pub/sc [...] new a6f4f1662711 HID: uclogic: Fix frame templates for big endian architectures new 9ad6645a9dce HID: ite: Enable QUIRK_TOUCHPAD_ON_OFF_REPORT on Acer Aspi [...] new d180b6496143 HID: hid-lg4ff: Add check for empty lbuf new 2afac81dd165 HID: fix I2C_HID not selected when I2C_HID_OF_ELAN is new 3405a4beaaa8 HID: uclogic: Add HID_QUIRK_HIDINPUT_FORCE quirk new ec61b4191858 HID: core: fix shift-out-of-bounds in hid_report_raw_event new f6d910a89a23 HID: usbhid: Add ALWAYS_POLL quirk for some mice new 40f2432b53a0 Revert "HID: logitech-hidpp: Remove special-casing of Blue [...] new a9d9e46c755a Revert "HID: logitech-hidpp: Enable HID++ for all the Logi [...] new ce19275f0103 Merge tag 'for-linus-2022120801' of git://git.kernel.org/p [...] The 10 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: drivers/hid/hid-core.c | 3 +++ drivers/hid/hid-ids.h | 4 ++++ drivers/hid/hid-ite.c | 5 +++++ drivers/hid/hid-lg4ff.c | 6 ++++++ drivers/hid/hid-logitech-hidpp.c | 28 +++++++++------------------- drivers/hid/hid-quirks.c | 3 +++ drivers/hid/hid-uclogic-core.c | 1 + drivers/hid/hid-uclogic-rdesc.c | 2 +- drivers/hid/i2c-hid/Kconfig | 4 ++-- 9 files changed, 34 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (52068c6ed21 -> a16136761ee)

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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from 52068c6ed21 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new a16136761ee 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1720 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52372 -> 52348 bytes 04-build_abe-gcc/console.log.xz | Bin 235188 -> 233252 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 234744 -> 235180 bytes 08-build_abe-gdb/console.log.xz | Bin 51780 -> 51684 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3872 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2652 -> 2752 bytes 11-check_regression/console.log.xz | Bin 5700 -> 5956 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14492 -> 14464 bytes sumfiles/gdb.sum | 34 +++++++++++++++--------------- 25 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (034bbd52ad0 -> c590ebe1699)

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 034bbd52ad0 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/ [...] discards 25cc89a55ed 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/ [...] discards 959f00c1548 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards 2ea10eb154f 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards c6fc6c9bd4e 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/ [...] discards 2e60c65ac9a 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/ [...] discards e687789c776 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qe [...] discards ebedc7b4e5f 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] discards ae003e31f3b 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-4 [...] discards cf5f7d7fe56 221: force: #1949: 3: Failure after basepoints/gcc-13-4492- [...] discards d5a98c2bb50 220: force: #1948: 5: Success after gcc: 4 commits discards b8b6645e098 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards 9aed96da850 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards 7852477d3a2 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] discards 55d563d80f6 216: onsuccess: #1940: 7: Success after linux: 12 commits discards ef5df772854 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards 7f0f1149099 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards 28abe38c84f 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards 0e205f7dec7 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards 3e635d7a80d 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] discards ca270bcc98a 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] discards 0ec297bcb35 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] discards 52040f890f7 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards c46c776896c 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] discards c2597223a3a 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] discards e33be8becf2 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] discards 9f73ae98843 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] discards 4867d82b801 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] discards ace2b5f561a 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] discards 10ba561bd71 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] discards 02f084edf8d 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] discards 88ff85e008d 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] discards f577b39255b 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] discards 3afc0f339e6 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] discards 88ff537ba44 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards a51184e4ab7 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] discards 0df11ca8d1e 194: force: #1853: 7: Success after gcc: 26 commits discards bd235b54f37 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] discards 8a924efb518 192: onsuccess: #1848: 7: Success after linux: 213 commits discards a61d10ef207 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards a3999ac79f8 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 67c7e3cfcf0 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] discards 30efdfba9d0 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] discards 5ad8bc1b959 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] discards 4e8890737a9 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] discards 5672c0ae4a2 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] discards a8ebd27768f 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] discards 8a27d591f72 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] discards 997de1c1525 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] discards 95d5be0746c 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] discards 6ee5f1dde5e 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] discards 9479439fb60 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] discards cbefcf39436 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] discards 91ba3bfa829 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] discards 8e99876515d 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] discards b62010de828 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] discards 47290f6a2e2 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] discards 7bdd2c51e74 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] discards 6f186b1879a 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards b97e8e3b858 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] discards 72a4edcb17e 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] discards ec305af6e71 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] discards 5423cb4509a 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] discards 377f43c7157 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 87c4be1237e 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] discards 2068e01ed5a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] discards b943ca01eef 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] discards 373ecb8dad7 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] discards 29d51f50aaf 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] discards 605d5091819 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] discards 4dfabf597fd 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] discards 3fc37ce3f37 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] discards f6cb216e265 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 2af57183d94 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 8073e28b196 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards a693cb5905a 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] discards c00a739ddb5 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] discards f83748ea014 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] discards f87e2150698 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] discards d0bc10062df 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] discards ade3a8613ed 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] discards 483d53f4b04 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] discards 946380606f9 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 8e4eb01b9c8 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] discards 624ef04130a 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] discards 76050e65ca8 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] discards d1592eef2f9 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] discards ce5f7d3ffa2 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] discards 8b58fd8bc36 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] discards 9c719d23f08 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 232689697ee 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] discards 62f7d6e4aca 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 30847e27a22 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] discards 5c8c785a891 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] discards 653360bec9c 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 656f94d3b6b 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] discards 16e9c1a872f 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] discards 5a6ac44583b 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] discards ebb17887ce4 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 5e5f1bb1949 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 0b85182a815 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] new eddd3cdba4d 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] new 3f9634af4f8 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 526c378c0d1 132: onsuccess: #1645: 7: Success after linux: 23 commits new 06035f4f66c 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] new 8fd255a11ff 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] new bd40166d9de 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] new a4d9494f832 136: onsuccess: #1650: 7: Success after binutils: 2 commits new b030c3d889d 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] new a0e6901fff4 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] new 017d71bddb5 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 9c1aef05d74 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] new 280390aaa7a 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 503e45d2121 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] new 9a24fd2b05e 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] new 990342a77bf 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] new ed36a81c9c5 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] new ecde728ffe8 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] new c3b4bbe3553 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] new b5f6efe13a7 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 1394f570df0 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] new 82d429ac15a 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] new 0b7146bcc6e 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] new 82665d13341 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] new ac20fcd4763 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] new ddf3c9a2aba 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] new a39a8593e83 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] new 5b694c1ea56 156: onsuccess: #1671: 7: Success after gcc: 3 commits new ff67035ead3 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 42901607f36 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 6964e3940d3 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] new febdf4acdaf 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] new 02dc54b8ebe 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] new de77c5edd1e 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] new 2cb272f6f5e 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] new 68d3f3fae39 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] new 613e47f3942 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] new f679ff8b9d9 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] new 60ca0b71b83 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 8a907552a94 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] new e5d084d33d1 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] new 989430fb71f 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] new a9aa8248c7c 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] new c4177739558 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 9c66a89451c 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] new b710c300914 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] new 9397204736d 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] new 6503086905f 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] new e404acf4a90 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] new 9d73b6264b9 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] new 0cf0341d820 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] new 2adc78d35d0 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] new c285cd08437 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] new 4c98a96553f 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] new d5d03e5c176 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] new ad79f7acc0a 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] new 2300c9eb56d 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] new 7e305475da0 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] new 6861347b524 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] new a95453f3df6 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] new b7957d917d2 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] new 8b3c522ee74 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 42d942ab02f 191: onsuccess: #1846: 7: Success after binutils: 4 commits new d9ac1cd3f93 192: onsuccess: #1848: 7: Success after linux: 213 commits new 8983093fa6c 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] new 0edb04b13fa 194: force: #1853: 7: Success after gcc: 26 commits new ddd49e293cf 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] new 2fa6c347456 196: onsuccess: #1855: 4: Success after gcc: 30 commits new ca2bbaf1a2b 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] new 57868ec269b 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] new 4fb33795967 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] new 9a47cf75c44 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] new aaa07aeafb2 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] new 3192707ffa2 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] new 92ab4b46fea 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] new a7923a79656 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] new 0623bb15e37 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] new 7532993b068 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] new 7635c0d9060 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] new 46f96c9fa9b 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new 07d36b1e2d4 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] new d39cf19400c 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] new 0903f2f5c5e 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] new c831b2613c4 212: onsuccess: #1934: 7: Success after gcc: 3 commits new fc4afd07f14 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 577a4c92821 214: onsuccess: #1937: 7: Success after binutils: 4 commits new f2d3b77effc 215: onsuccess: #1938: 7: Success after gcc: 4 commits new 7a3050bbf5a 216: onsuccess: #1940: 7: Success after linux: 12 commits new 3bdc34d1b59 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] new 1d49b647770 218: onsuccess: #1943: 5: Success after gdb: 3 commits new b0bae7336fc 219: onsuccess: #1945: 5: Success after binutils: 8 commits new c645b649108 220: force: #1948: 5: Success after gcc: 4 commits new 38840ba3183 221: force: #1949: 3: Failure after basepoints/gcc-13-4492- [...] new bae42e4ab05 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-4 [...] new 239b0ae5d77 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] new 56e7478db1d 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qe [...] new 571aadafde7 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/ [...] new 55c2f339b47 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/ [...] new 4c600732699 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new 008af681b9b 228: onsuccess: #1956: 7: Success after gcc: 5 commits new 9d62b8281fd 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/ [...] new c51f19fb424 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/ [...] new c590ebe1699 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/ [...] 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 (034bbd52ad0) \ 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 1728 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 31480 -> 31608 bytes 05-build_abe-stage1/console.log.xz | Bin 91936 -> 91316 bytes 07-build_abe-linux/console.log.xz | Bin 8548 -> 8564 bytes 08-build_abe-glibc/console.log.xz | Bin 235768 -> 235540 bytes 09-build_abe-stage2/console.log.xz | Bin 225488 -> 225024 bytes 10-build_abe-gdb/console.log.xz | Bin 38612 -> 38776 bytes 11-build_abe-qemu/console.log.xz | Bin 30248 -> 30420 bytes 12-check_regression/console.log.xz | Bin 4000 -> 3984 bytes 13-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +++++++++++++++++------------------ 20 files changed, 48 insertions(+), 48 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-allnoconfig updated (18fea297a62 -> 8064e940e32)

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-allnoconfig in repository toolchain/ci/base-artifacts. from 18fea297a62 27: onsuccess: #378: all: Success after binutils/llvm/linux [...] new 8064e940e32 28: onsuccess: #379: all: Success after binutils/linux/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 1752 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 30752 -> 30412 bytes 04-build_kernel_llvm/console.log.xz | Bin 65912 -> 65296 bytes 05-build_abe-qemu/console.log.xz | Bin 30232 -> 30852 bytes 06-build_linux/console.log.xz | Bin 3172 -> 3260 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4088 -> 3912 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 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, 5 months

[gcc] branch master updated (5ddfe794405 -> 7410032a772)

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 5ddfe794405 bpf: add define_insn for bswap new 7410032a772 Fix count comparison in ipa-cp The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ipa-cp.cc | 2 +- gcc/testsuite/gcc.dg/tree-prof/pr108000.c | 93 +++++++++++++++++++++++++++++++ 2 files changed, 94 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gcc.dg/tree-prof/pr108000.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allmodconfig updated (adda00497c0 -> 474f7c78138)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from adda00497c0 30: onsuccess: #576: 33: Success after binutils/gcc/linux/q [...] new 474f7c78138 31: onsuccess: #577: 33: 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 1944 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32104 -> 31692 bytes 04-build_abe-stage1/console.log.xz | Bin 92208 -> 91248 bytes 05-build_abe-qemu/console.log.xz | Bin 30560 -> 30228 bytes 06-build_linux/console.log.xz | Bin 4948 -> 5444 bytes 08-check_regression/console.log.xz | Bin 4420 -> 4388 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (5c8e02e5738 -> d0b444c2e56)

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 5c8e02e5738 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards c41e5de71b6 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards 51972d9c3b7 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards e49fd0a71dc 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards 05f836517c2 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards 78d1f6c8556 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards 6fd765f77dd 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards 2f0baaa8f4b 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards 0a2d968bdbd 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards 82563d824b1 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards 635ab110a12 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards 60de52d1f8e 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards 152405debd5 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards 3211c4d833e 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards 886ba5f175d 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards ca47c9ced8f 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards 4a9d6dd21f6 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards c34ce9c996b 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] discards 5f2d3e65dd9 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards 06b04f1f8f4 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards 1e98f195907 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards 2bce680dd76 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards b04bd9cb150 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 8491dd57615 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards 755f1db142f 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 1600efcc937 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards b41153829db 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards 63b253f6338 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards b4d211509b5 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 8832d3f28b1 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards 6e4f80a94d7 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards f3dc4ff1b8e 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards 3ede768b399 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 37ad50026e7 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards 1259457855d 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards acb774dee7b 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards 58d81493269 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards 969248ade1e 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards f390a6e101b 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards 3da529a324e 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards f89c326dc12 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards 587334d0fd0 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 734dbfd544b 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards a48fe2c04e1 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 9578424bf22 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 724e06f1a92 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards a4259c93449 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards cd70695b675 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 3927a8c1d62 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards 75f5df9a767 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards e37a33aa249 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards ba3e3c6ee80 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards a60303d96dc 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 6d6433c1407 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards 60f0bb1b676 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 325788f4afb 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 8de97d301cd 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards 754b380bacf 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 9a5e1dc2b07 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 421bf6001ab 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 79b0ce75ba2 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards 2e00646bda1 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 7769c84b1bb 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards 6794cf6e69f 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards 245ed1cef8b 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards b8a2795a3a4 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards 9bdef4b00de 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards e0498009ee2 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards 8bc1637315c 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards 83a2e0de907 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards af256be51a0 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards 32c25298e0e 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards 6cb7e606b6e 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards 47b255785ee 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards f387a6c4dce 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards 0d03b4e06cd 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards b4c11ec895a 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 1a06eefb0f9 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards 3fbdb1a9f1c 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards 6ab6b6c9fee 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards f1b02c31ca9 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards 53105d927ed 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards 36131059efb 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards 8d32aa38fa0 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards c15cffe9e35 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards a97f296c11c 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] discards f7a5a9cf544 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards dee173ac4ab 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] discards 7f53e2dc6ea 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] discards 7422f113854 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] discards fefaee73299 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] discards e89b4440757 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards a48b273b748 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards fe3c25cbd60 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards d1eb8907237 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards fa230dbf133 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards 50731e5ed6d 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards 0905ee5d37a 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards c41de5a71dd 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards 64561903277 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards cd8fae7635b 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new 0ecc34bf4af 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new 1e6d84d5164 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new ec115cf45c6 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new a2447d999c9 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new fe3af78c102 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new 4d19e345ca1 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new d1e0a78c76d 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new 37885e2af00 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new 42f4b647cc9 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new 3899f3742e4 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new 3cdd441ffbc 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] new 10c4ae578f3 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] new 8bc4b8f9c2c 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] new a316045345b 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] new 6cf76e4f351 310: onsuccess: #2259: 1: Success after binutils: 2 commits new 4ae37562135 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] new 9f120fd0684 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 6975b25e976 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new f597d50d735 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new 3c66fa3afc5 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new 6ac884cdc2d 316: onsuccess: #2270: 1: Success after gcc: 2 commits new 7596c9b2930 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new 8454724e031 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 5c46b95dae3 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 225882ce9bd 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 3e381a32958 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 319806f73c3 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new 9095f589c79 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 60111325b04 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 9424b682e8c 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 8f782474195 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new 430c40753e5 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 72a3ed8f8e5 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new c29a0987535 329: onsuccess: #2285: 1: Success after gcc: 8 commits new fdebe495deb 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 877479c09b5 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new 67e9f802528 332: onsuccess: #2288: 1: Success after gcc: 2 commits new 758d2168d36 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new 0127970c9be 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 848b5d591e5 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 34b39c5507f 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new d4731df29c5 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 7186b9187cb 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new ea496e3d986 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new cd31629504c 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 142a25b02f5 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new b3ce7c993f8 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new a4250171b4e 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new fb3fc182008 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new 0997007c64f 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new bceb5e3bf91 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 0067ecc6ee4 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new 8d5c50b123d 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new 14faa99faa8 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new 9f49a770c2f 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 2946cc24d40 351: onsuccess: #2307: 1: Success after binutils: 2 commits new 3867d2bee64 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 2243989170d 353: onsuccess: #2309: 1: Success after gcc: 7 commits new e2dbd3d9cbe 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new adfdf5cbfc0 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new f1eda89fbb5 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 012780ed59d 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new a473f720b78 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new 45312f9c9a9 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new f7731914220 360: onsuccess: #2317: 1: Success after binutils: 4 commits new cc08a66b07f 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 928712651e3 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 4d83bc1cb71 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new 546a92c6018 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new b5fb9212c1b 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new ebc877ff532 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 4bdf694d7bd 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new 814f3dfb90e 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new 26ba0b05b90 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new e89376060a0 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new 23a0156b985 371: onsuccess: #2333: 1: Success after binutils: 5 commits new 89dc706293f 372: onsuccess: #2334: 1: Success after gcc: 5 commits new d79510cc18f 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new a9c3ffc9ea8 374: onsuccess: #2336: 1: Success after gcc: 4 commits new edaa6fa7ac9 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 9684b7d7cf8 376: onsuccess: #2338: 1: Success after gcc: 2 commits new ae88f281e50 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new 62c8b65a967 378: onsuccess: #2340: 1: Success after binutils: 2 commits new 3bc0f8bb337 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] new 0898cc2096c 380: onsuccess: #2342: 1: Success after gcc: 3 commits new a3625f3e92b 381: onsuccess: #2343: 1: Success after gcc: 2 commits new cd7d40df2fd 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new b48568b8dac 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new 20b27b7477f 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new bbcb7cbdead 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new 541ccd8194e 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new f96c7c4756e 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new 69f126af4e4 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new 458709287cc 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new 2392575c314 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new 3314c43745c 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new 2299c5aba75 392: onsuccess: #2354: 1: Success after gcc: 5 commits new 388ccacfe0a 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new 598def852bb 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new 5d823b59cd2 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new 3308a6404a3 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new d0b444c2e56 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 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 (5c8e02e5738) \ 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 1720 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39776 -> 39748 bytes 04-build_abe-gcc/console.log.xz | Bin 215044 -> 215684 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3884 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2708 bytes 07-check_regression/console.log.xz | Bin 5284 -> 5176 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 129 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 3592732 -> 3640120 bytes sumfiles/g++.sum | 130 +- sumfiles/gcc.log.xz | Bin 3150824 -> 3141464 bytes sumfiles/gcc.sum | 5051 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1047012 -> 1034044 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 218660 -> 219228 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 454584 -> 452508 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2705 insertions(+), 2779 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[linux] branch master updated (479174d402bc -> f3e8416619ce)

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 linux. from 479174d402bc Merge tag 'platform-drivers-x86-v6.1-5' of git://git.kerne [...] new fbf8321238ba memcg: Fix possible use-after-free in memcg_write_event_control() new d95d140e8363 ata: libahci_platform: ahci_platform_find_clk: oops, NULL pointer new 57fb3f66a3aa Merge tag 'ata-6.1-rc8' of git://git.kernel.org/pub/scm/li [...] new ec851b23084b gpiolib: fix memory leak in gpiochip_setup_dev() new 45fecdb9f658 gpio: amd8111: Fix PCI device reference count leak new 63ff545af73f gpio/rockchip: fix refcount leak in rockchip_gpiolib_register() new 306ba2402de5 Merge tag 'gpio-fixes-for-v6.1' of git://git.kernel.org/pu [...] new 7dfa764e0223 xen/netback: fix build warning new a4c3a07e5b9f Merge tag 'for-linus-xsa-6.1-rc9b-tag' of git://git.kernel [...] new 143d64bdbdb8 LoongArch: Export symbol for function smp_send_reschedule() new b681604edab6 LoongArch: mm: Fix huge page entry update for virtual machine new 38eb496d85b8 docs/LoongArch: Add booting description new 1385313d8bc1 docs/zh_CN: Add LoongArch booting description's translation new 7f043b7662b6 Merge tag 'loongarch-fixes-6.1-3' of git://git.kernel.org/ [...] new 6a3fc8c330d1 ARM: at91: fix build for SAMA5D3 w/o L2 cache new da0cbf9307a2 Merge tag 'at91-fixes-6.1-3' of https://git.kernel.org/pub [...] new f3e8416619ce Merge tag 'soc-fixes-6.1-5' of git://git.kernel.org/pub/sc [...] The 17 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: Documentation/loongarch/booting.rst | 42 +++++++++++++++++++ Documentation/loongarch/index.rst | 1 + .../translations/zh_CN/loongarch/booting.rst | 48 ++++++++++++++++++++++ .../translations/zh_CN/loongarch/index.rst | 1 + arch/arm/mach-at91/sama5.c | 2 +- arch/loongarch/include/asm/smp.h | 10 ----- arch/loongarch/kernel/smp.c | 11 +++++ arch/loongarch/mm/tlbex.S | 30 +++++++------- drivers/ata/libahci_platform.c | 2 +- drivers/gpio/gpio-amd8111.c | 4 ++ drivers/gpio/gpio-rockchip.c | 1 + drivers/gpio/gpiolib.c | 42 +++++++++++-------- drivers/net/xen-netback/netback.c | 2 +- include/linux/cgroup.h | 1 + kernel/cgroup/cgroup-internal.h | 1 - mm/memcontrol.c | 15 ++++++- 16 files changed, 167 insertions(+), 46 deletions(-) create mode 100644 Documentation/loongarch/booting.rst create mode 100644 Documentation/translations/zh_CN/loongarch/booting.rst -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig updated (16e1dfe3d80 -> 8d8a4750519)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 16e1dfe3d80 26: onsuccess: #468: boot: Success after binutils/gcc/qemu: [...] new 8d8a4750519 27: onsuccess: #469: 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 1960 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31816 -> 32100 bytes 04-build_abe-stage1/console.log.xz | Bin 73496 -> 73336 bytes 05-build_abe-qemu/console.log.xz | Bin 31092 -> 31112 bytes 06-build_linux/console.log.xz | Bin 3332 -> 4072 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3940 -> 4292 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, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (1abaf1f4632 -> d04a13ae207)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 1abaf1f4632 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards e8d686c50f9 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 79e88deac68 118: onsuccess: #863: 1: Success after linux: 12 commits discards 1ad647f1b30 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 5e2ebb2956d 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards e0908f6dffc 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards abe04a87932 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 6ed424e493c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 23006f4737a 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 365be5a5132 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 944ca9cd947 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 07261adb25c 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 1b95615456f 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 1162873ea48 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 2d37c00d8e2 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 2285d27f42a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 89a0c228f2f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 0fb01b784ec 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards ccf14b94e40 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 1324b914218 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 1ebe264f89d 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards fab35a06a69 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 1b885cab7b2 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 38074d9c0a4 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards c01db81b2d6 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 985ad4af17a 95: onsuccess: #835: 1: Success after binutils: 3 commits discards b22f08b79f0 94: onsuccess: #832: 1: Success after binutils: 5 commits discards b1d4bd1bf3f 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards e8ead4039e9 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 6fba8420a73 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 59efb65f650 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 7c0131405d5 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 79a343a6d6c 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 699fb7d2045 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 9a47f79d457 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 8684de813b9 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 0371d8c6651 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards f6d65243974 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 56460e77686 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 085a0b46639 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards de340c48516 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards f7abd138dfb 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 294c6c26d5f 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards f9c2f5599bc 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 6d9f89dda3a 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 30afc751247 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards a5a476f9f5b 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 570a1e727a5 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards d5fb5162d92 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards adf534a1e49 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 58fd80e3607 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards c45805643a2 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards b43bcc36078 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards a682181f569 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 03ce2dc18b5 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 869f9e72a1f 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards e2c30ac73cd 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 6435228b6bd 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 0d4668028f2 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards c373f914153 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 06aac5daacb 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 4a7df064418 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 84b64b1df0d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards af8481ad9dd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 4fb9c625830 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 9521ca64ea6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 618efc85143 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards b062579a9c2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards e9b9cc520a4 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards a0e4cec84ee 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards ef9053f764e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 4df711824a0 49: onsuccess: #785: 1: Success after binutils: 12 commits discards b493f7dde94 48: onsuccess: #782: 1: Success after binutils: 8 commits discards cf8cf5c8166 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards f333971e78f 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 8f3168664ba 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards c4f8eee90f9 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 80e8cbf84d3 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 03d43ce35cd 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 9f30efddfa2 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards d91f98d578a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards aa925c6c795 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 17a196ded7f 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards b9eca511e02 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards a4e28e71c2b 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 121714b476c 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 68dd2b335f8 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards ae38e8f1814 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 6fa24e3dfd6 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 5e00c5b611e 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 7e232212853 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards fe92e3b2747 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards d1406ec4695 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 894695feb67 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 5f570a5fdde 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 0dada265ce2 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards e1bfb94a87c 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 9de5833f9ed 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 46dde8ebe90 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 52eac4f18ff 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c32533c80b5 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 776343b91e4 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 6e5c310f839 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f239de4a29a 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 18c1b76b0eb 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 1f437a786b0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 18ef88a2997 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 26f9a339173 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 359a4253e35 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new d0f3bd9e55d 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 8d90163205e 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 40b3948168b 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 0814acfbb26 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 6edeccbec08 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 30d28ea9998 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 45290253906 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new c068f9ffd1e 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 352da7305fb 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 14bdfe8c57e 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new fcd868f4a22 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new ad66afbb04e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new b1456d77fa1 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 0064ef484ba 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new afd9d778f2e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new a382d7ba1ac 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 851538ae099 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 9148f6776f3 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new c3e48d64dd9 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 623f6fffd32 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new c4deaa5671f 48: onsuccess: #782: 1: Success after binutils: 8 commits new 755f69ad2ba 49: onsuccess: #785: 1: Success after binutils: 12 commits new 1a329a896d3 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 3acd5369329 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new d0dc6a5f499 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new f5b68dfe22b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new a05f8e40ca0 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new b27108279d3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 0d04972b3de 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new bf302f382e9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 0e2f011b1df 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new db16fdc5df7 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 5da817e231d 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new b4cb9742696 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 101d34c5208 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 01caf8b0701 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 85b5e42b8f9 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 9724e52a190 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 146cb134aa5 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 6cb1780ebe9 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 0eaf5bad93f 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new cdc41291707 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 89a5c0738b3 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new ac6930b5466 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 94d75eb4d63 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new a53d1fe6c5a 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new c1ca7411af5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 75102afe700 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new d6a84952af9 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new bd106f71e95 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 9e9f635d719 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 334adb95c18 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 99e39120a9c 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 13856fffc15 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 38fcd727b0c 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 1dbcb05d1e0 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new feab18af51e 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 84cecdc46a0 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new a52c3c8e038 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 8876df3b2dd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 55a0f0ba1d4 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new fc836ea4ecb 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new be62ad06e56 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 3ff8b02aa49 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 3c708a5cb13 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 7aaade82c24 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new b4f5b9a7a35 94: onsuccess: #832: 1: Success after binutils: 5 commits new e7c009c91d5 95: onsuccess: #835: 1: Success after binutils: 3 commits new cc3d3f57c1a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 7cfbb364a21 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new bb70f71dc60 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 8fa6ad95962 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 9abac687911 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new ecc98a64c88 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 8577c385c2d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new cd82797f6a2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 395fb5addf4 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 059457bacdd 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 6d7e069791a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new aee5cffd05a 107: onsuccess: #849: 1: Success after binutils: 5 commits new d455e0fc6fa 108: onsuccess: #850: 1: Success after gcc: 2 commits new 84ee35915ee 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 16e733e634c 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 742a68a918e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 680343463d6 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 3a1cdf1a147 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new dbabd8cc56f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 08f94db2ecb 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 795e13375ab 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 75ae16f679b 117: onsuccess: #861: 1: Success after binutils: 18 commits new d1edaaeb629 118: onsuccess: #863: 1: Success after linux: 12 commits new 18a92f6494b 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new ac53ca3583f 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new d04a13ae207 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (1abaf1f4632) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/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 1756 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39752 -> 39676 bytes 04-build_abe-gcc/console.log.xz | Bin 216032 -> 212676 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8492 bytes 07-build_abe-glibc/console.log.xz | Bin 244392 -> 243216 bytes 08-build_abe-gdb/console.log.xz | Bin 39232 -> 39004 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2516 -> 2708 bytes 11-check_regression/console.log.xz | Bin 7328 -> 7728 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 278 +- 11-check_regression/results.regressions | 27 - 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 27 - sumfiles/g++.log.xz | Bin 3750376 -> 3728288 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3291704 -> 3303216 bytes sumfiles/gcc.sum | 5483 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1085088 -> 1075860 bytes sumfiles/gfortran.sum | 118 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231448 -> 231420 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453348 -> 450116 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 3155 insertions(+), 3125 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022