Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (8b9fc9551db -> 3730e9728ce)

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 8b9fc9551db 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 3730e9728ce 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] 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 1776 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 52228 -> 52208 bytes 04-build_abe-gcc/console.log.xz | Bin 235772 -> 233848 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8532 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 236176 -> 235596 bytes 08-build_abe-gdb/console.log.xz | Bin 50456 -> 50616 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2568 -> 2476 bytes 11-check_regression/console.log.xz | Bin 5960 -> 5536 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/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- sumfiles/gdb.log.xz | Bin 14512 -> 14440 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[gcc] branch master updated (98d6e4b6f10 -> 24b9337d1f1)

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 98d6e4b6f10 Fortran: fix typo in documentation of intrinsic FLOOR [PR107870] new 24b9337d1f1 Fortran: error recovery simplifying UNPACK for insufficient [...] 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/fortran/simplify.cc | 11 ++++++++++- gcc/testsuite/gfortran.dg/unpack_field_1.f90 | 15 +++++++++++++++ 2 files changed, 25 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gfortran.dg/unpack_field_1.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (c081e32c528 -> 46559daae47)

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 c081e32c528 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards f118ca4bda3 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] discards 5bd55c6e19b 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] discards caf66f8886e 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] discards 1e65348d3d7 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards b9220832a0f 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] discards 48574ba3a5d 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] discards 155a9f521b3 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] discards 5f983b17f48 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] discards 6912f2d90a4 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] discards dbdf936bac4 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] discards 4c26b238d80 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] discards 732ef00758a 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] discards aa3945111fd 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] discards c95b2a170da 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] discards a2d2febe7da 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] discards e406d19da46 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards d21cfe83cdd 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] discards 72983165094 194: force: #1853: 7: Success after gcc: 26 commits discards 2c4ade9fd7a 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] discards caf6bc3688e 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 9376ae3e638 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 42d07e65cc3 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 0ce5c1301fd 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] discards f72895593b3 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] discards 51cac54586f 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] discards 09f66be8e38 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] discards b8c9634272f 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] discards 07a06d923fe 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] discards 231af6c3bcb 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] discards dae3a75e697 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] discards 8d5db893abf 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] discards 869e28c4c6c 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] discards 61a44bffc44 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] discards de25b6e28a4 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] discards d758fa3d19c 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] discards 5a3a693f5a6 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] discards 9ab212e923f 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] discards 3ae63f109b4 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] discards a965ad5ca1d 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] discards 8e52765023c 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 5ddd867bcbc 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] discards 9ee8e94ddec 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] discards d81865fc36c 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] discards 56574fcf279 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] discards 33d02a26911 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 0f58f4fee95 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] discards 7a4e48e09ca 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] discards 10432ee9034 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] discards 6af9f370bc8 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] discards 393f4c8b203 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] discards c47c63aacb0 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] discards 5d3ddf22e72 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] discards c667d75c24c 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] discards 40f4e76e568 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 5f0e87ebd0a 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 4a5880bd64b 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards deb6d23cd52 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] discards 09647375085 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] discards 171cec56685 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] discards 1d720a665df 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] discards b1531a7a680 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] discards 22cb12bd9dc 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] discards 1fe815d29fc 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] discards a61ef0b0b60 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 60b913fc4e1 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] discards 36e3a182c62 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] discards 98240cb8e66 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] discards f461f92f162 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] discards 976c2e9a56d 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] discards 537a7ee8c62 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] discards 064511e8452 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 08168e7ce57 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] discards 7a1fdd8bae4 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 91a2ed88201 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] discards 024986040cd 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] discards 47725064f57 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 15ee53540dd 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] discards 302fbcf8538 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] discards 0faeb539612 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] discards c8b865c9783 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 9c41147be30 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards c57e4ed24fb 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] discards dbf9dd6ea74 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 70b8428a28a 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] discards 4f2d71e3e23 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 6d3dacf68bc 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/ [...] discards 91057bb994d 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/ [...] discards 6071a7c8adc 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/ [...] discards b8aae68dfe0 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards 12d1ebe8c48 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/ [...] discards c75168e4c98 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 1 [...] discards 883b0f695ab 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qe [...] discards 078cf41427c 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards fafdef78a3f 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 1 [...] discards b8df37718ff 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 22d8f9477b0 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/ [...] discards 1e66a389473 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards 05ea7fd6059 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/ [...] discards ed845ff3559 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards f051a98f820 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 [...] new 262a8160f2f 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 [...] new 2a0736f46ba 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 2d5e23102bf 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/ [...] new 7242270889c 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new 78e0fe85431 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/ [...] new a15ab19bc34 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 5be9d3612a0 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 1 [...] new 3e85d0ebbcd 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new a6410412679 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qe [...] new fd42571efb9 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 1 [...] new 43c6b43752b 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/ [...] new e11a5a9498a 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new 000cd3539ee 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/ [...] new 731b686261d 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/ [...] new b90ed7bb59e 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/ [...] new f1c03479155 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new ec7f540e96d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] new 5f45e57e473 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new e49bf3c7e94 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] new 93f65e15398 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 91e72759d5e 132: onsuccess: #1645: 7: Success after linux: 23 commits new c9253047a54 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] new ee74b88e3ad 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] new e24f3dc50ad 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] new e56c505d3d5 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 60d2a8800d7 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] new a6487970d12 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] new 61e1b002f1a 139: onsuccess: #1654: 1: Success after gcc: 11 commits new c8c93e67f92 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] new 884f6950dd9 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 69834242c60 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] new 9035260c158 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] new 6fe1a211750 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] new 7bd227ceb5b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] new c9fb059ba52 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] new b142160891d 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] new 3b5b213d20a 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 1106815ce30 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] new 52ea723fc05 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] new d73c9df9dfb 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] new 9e001e99302 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] new 07c0487a062 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] new a765ed1b485 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] new 296eb00d8e3 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] new 8f3a8b4c0bb 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 288d7dae10a 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 1f1f7532c12 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 656cb85ca46 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] new 8863887b137 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] new 79de98073a3 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] new ec0953f866c 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] new 42fcf2ade95 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] new c8f9942692f 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] new ff8614267f9 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] new 9fc4d544061 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] new a3f07fc4010 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 5b1da0e4986 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] new 7ba172f99fd 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] new ce885cf7f86 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] new 149eaae1699 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] new e7c8f067cb6 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 30923637f17 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] new 8548012eecd 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] new 09735762eeb 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] new 98c11e8769c 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] new ae5d2d3d7f6 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] new 102b70a5222 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] new ce47fe10500 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] new b7c93ec51f6 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] new 31b3bf26327 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] new 1312f18b8a6 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] new 4d827d99ce0 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] new 137cd24976c 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] new 4b75feab544 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] new 8e9fa868365 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] new aded149b5e4 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] new ccd3245929c 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] new 9b1b8b18cd7 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] new f70c029340b 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 7071273ca87 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 5928d82eb6e 192: onsuccess: #1848: 7: Success after linux: 213 commits new a95b8c4bcf7 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] new 1ae7b16b97e 194: force: #1853: 7: Success after gcc: 26 commits new a261a7af176 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] new c51b248d032 196: onsuccess: #1855: 4: Success after gcc: 30 commits new b5c5ee67535 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] new e9e6c66e00e 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] new 8e0210adce0 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] new 633eda97f6f 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] new 823fb08fbad 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] new 02a61060a70 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] new 83677fa5206 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] new af7780cb6bf 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] new 8be59c4afa0 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] new c11b3495ced 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] new 4fcb90b5de6 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] new 4ee9e6d9a7e 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new 29955343097 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] new 296f5c0f041 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] new 716e5775311 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] new a5bf2cfa524 212: onsuccess: #1934: 7: Success after gcc: 3 commits new 46559daae47 213: onsuccess: #1935: 7: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (c081e32c528) \ 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 1716 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 31632 -> 31288 bytes 05-build_abe-stage1/console.log.xz | Bin 92276 -> 91288 bytes 07-build_abe-linux/console.log.xz | Bin 8660 -> 8704 bytes 08-build_abe-glibc/console.log.xz | Bin 236888 -> 236780 bytes 09-build_abe-stage2/console.log.xz | Bin 225480 -> 223888 bytes 10-build_abe-gdb/console.log.xz | Bin 38732 -> 38336 bytes 11-build_abe-qemu/console.log.xz | Bin 31476 -> 30800 bytes 12-check_regression/console.log.xz | Bin 3456 -> 3336 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++------ 17 files changed, 51 insertions(+), 51 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allmodconfig updated (31153022aae -> 98bf370f662)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 31153022aae 42: onsuccess: #514: 23023: Success after binutils/llvm/lin [...] new 98bf370f662 43: onsuccess: #516: 23023: Success after binutils: 87 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32044 -> 30964 bytes 04-build_kernel_llvm/console.log.xz | Bin 65736 -> 65744 bytes 05-build_abe-qemu/console.log.xz | Bin 30660 -> 30804 bytes 06-build_linux/console.log.xz | Bin 5208 -> 5224 bytes 08-check_regression/console.log.xz | Bin 4320 -> 2908 bytes 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 | 25 +++++++++++-------------- 13 files changed, 16 insertions(+), 19 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

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

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 66a84e86850 29: onsuccess: #575: 33: Success after binutils/gcc/linux/q [...] new adda00497c0 30: onsuccess: #576: 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 1704 -> 1944 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 32584 -> 32104 bytes 04-build_abe-stage1/console.log.xz | Bin 91308 -> 92208 bytes 05-build_abe-qemu/console.log.xz | Bin 31312 -> 30560 bytes 06-build_linux/console.log.xz | Bin 4740 -> 4948 bytes 08-check_regression/console.log.xz | Bin 4396 -> 4420 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.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap updated (888a70e1b3e -> 406ecde017b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap in repository toolchain/ci/base-artifacts. from 888a70e1b3e 37: onsuccess: #160: 1: Success after binutils/gcc: 12 commits new 406ecde017b 38: onsuccess: #161: 1: Success after binutils/gcc: 6 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 1680 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 50760 -> 52112 bytes 04-build_abe-bootstrap/console.log.xz | Bin 466336 -> 461944 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3852 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2788 -> 2452 bytes 07-check_regression/console.log.xz | Bin 5488 -> 4900 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 49 +- 07-check_regression/results.compare | 32 +- 07-check_regression/results.compare2 | 47 +- 07-check_regression/results.regressions | 42 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 51 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 42 - sumfiles/g++.log.xz | Bin 2810360 -> 2798036 bytes sumfiles/g++.sum | 114 +- sumfiles/gcc.log.xz | Bin 2461920 -> 2494692 bytes sumfiles/gcc.sum | 4154 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 951940 -> 940140 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2308 -> 2304 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206608 -> 207244 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2728 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 460948 -> 472308 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2236 insertions(+), 2411 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (8bac11c1fed -> 291ced2be33)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 8bac11c1fed 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 7e4bb2cd048 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] discards 9851aa5b177 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] discards 27c6b7c0943 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 23c06b9dbb8 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] discards e498afb716f 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards da7004c44f8 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] discards 1023805d9f8 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 37b2b197236 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] discards a3c759b0270 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] discards 72a98b0b0e8 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] discards e4d1e822a5a 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] discards 85b68221514 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] discards 5c91ff3f3a8 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] discards eb4a908c555 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] discards 60560cae43c 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 2f44adaa9d7 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] discards f253cd825f6 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] discards d5754db2eff 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] discards b8ae7ba5893 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] discards efd545ed415 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 6e4df948a97 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] discards e7b4e0dcccf 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] discards 9f40eb8a3d2 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] discards d0b3628a195 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] discards b4e0e96e970 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards c9b8c0c13e0 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards d846c70b16c 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] discards ae3a799295c 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards b2390be4d9c 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] discards 28539d6d7a7 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] discards 3f8562f8802 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] discards cd44e7d93b1 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards ff097030f67 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] discards 6937b328da8 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] discards 4e8a1416ea6 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] discards 60ea7df1c84 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] discards 60372933e81 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] discards 2649ccbb3a7 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] discards f0d6469910f 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards a4c65e9f348 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] discards c23cf68bccb 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] discards 3db566e6a7d 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] discards 6e5cae2da58 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] discards f5fd77fe8fa 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] discards 7259c86f575 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] discards 0cb5575c387 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards b5b55211278 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] discards fc14c494985 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 832acbca6ae 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 1d91281793f 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] discards f83de116cfc 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards cf3561db76f 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] discards 2a4875caab2 152: force: #1605: 7: Success after gcc: 9 commits discards 28936ce6e1f 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] discards bf39f96a378 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] discards 6e667b4228e 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] discards 4e7b6d2f3e2 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] discards 125bbff5b07 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] discards 3de67871690 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] discards 6b24cf50aee 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] discards 909966a999a 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards a8481c3aa71 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] discards cf5d8c70d8e 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] discards 7761d630f2b 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] discards 6027d649011 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] discards 4b567bcf88d 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] discards 60cc89a8a0d 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] discards ddecfe05482 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 11c82bff2c5 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] discards 44162e03c35 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] discards ea697fa3751 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] discards 2f285af6e2c 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] discards 945da0bdc4a 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] discards 34bef0469d1 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] discards 3e8280d4151 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 744d78885f9 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] discards b5131f3ffa7 128: onsuccess: #1579: 7: Success after linux: 12 commits discards d6798257887 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] discards f3072a754b5 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 5ff098f663c 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] discards 53e18cc0a09 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 102a83dbbff 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] discards 7e204442f63 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] discards 7136413666e 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] discards 288f2739cb2 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] discards 9760347d885 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] discards 12c8500a131 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 [...] discards fa3c50b1118 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qe [...] discards d7e6f2fdad1 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/ [...] discards 9e16f3cb96e 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 1 [...] discards 62aae4b6afc 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 1b6d7ea6979 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/ [...] discards fbaa83acc60 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/ [...] discards 6ac7b86feb3 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/ [...] discards 0d2ce29bb2e 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards e6bc892d6a7 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 [...] discards ecc11596ac4 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-2 [...] discards 7eca9edfdb9 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/ [...] discards a1c0cbb0a69 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/ [...] discards 531a69b0643 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38edde [...] new b79693b7e88 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38edde [...] new a2aa9744f26 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/ [...] new b668362b24f 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/ [...] new 8346137303a 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-2 [...] new 06c215ad643 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 [...] new 0a861436d12 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 786c3110e9c 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/ [...] new bf0f1f482c9 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/ [...] new c75f03212dd 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/ [...] new a9c635cfe0c 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 438fb2d0c80 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 1 [...] new 7cc1df8349c 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/ [...] new 2d9a95e75f6 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qe [...] new 79812b3f717 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 [...] new f11c237d39c 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/ [...] new 915dc04d1b3 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/ [...] new 85b7680b80b 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/ [...] new 538c8413efe 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/ [...] new 60de1b7f64c 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/ [...] new 824709f66a9 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new f1feae4cbe1 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 [...] new d377c8c8e3c 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 2fe16c0d0c6 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 [...] new 5f3dd4990cf 128: onsuccess: #1579: 7: Success after linux: 12 commits new d9a3ff528a0 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] new 8984076f121 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 1a5b33b5e9a 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] new f38185d6051 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] new 96337f4f056 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] new ae9acd170d3 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] new ab83017fc44 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] new f18b8f6aea4 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] new 7cedb3619bf 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 8bda638b456 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] new 64e12d68e6d 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] new 23939bbf05b 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] new 0a555c4714a 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] new 35c3567ffac 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] new bdb39d37ea2 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] new a01a8f97091 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 9fe27f71f9b 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] new 4fc3e0b4ca1 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] new 67f5d545f95 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] new 3312469de3d 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] new 203db3f98b5 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] new e14e539d585 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] new 10d748c38ff 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] new f283bc6e272 152: force: #1605: 7: Success after gcc: 9 commits new 70ccdfc3b5f 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] new fe1c8a3ac92 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 0b8b7a68afe 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] new 23d251d6792 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 98b5c9960d7 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 90c286703de 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] new f6f7f57dd47 159: onsuccess: #1612: 7: Success after gcc: 4 commits new ebb5a4a50d8 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] new 2fb761eff10 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] new 805bcc370df 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] new 69e570eeabf 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] new 674ec279f3f 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] new 29df376f438 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] new 9b04d3ff39a 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new fd242445481 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] new 6e266cb1958 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] new 4e1e662068b 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] new bf2579e1b35 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] new 0dd159266fd 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] new 2f329d2a527 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] new 426c58b2e65 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new 226343d65ad 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] new bd7ca3235b5 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] new a02e7b728ff 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] new 4ccaea66f9b 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new 6860d572169 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] new d8c0453722d 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new 6a12734c824 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 3a7c9c311c6 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] new c8948314e4a 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] new 94f195c5df9 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] new f8b395f3784 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] new 6b6735293ca 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new 72f787b6db1 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] new b5fedff723d 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] new 30dd5795fd6 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] new 89635e2d8d5 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] new 17d781af94d 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 07f8b3213eb 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] new ee439163917 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] new 53f04eb27fa 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] new 5477b3cdbca 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] new 30e7ba05b04 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] new 83eee43191a 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] new d8b35414796 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] new 1f2faa03e91 198: onsuccess: #1852: 7: Success after gcc: 5 commits new f593fe5b149 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] new cfb442ca76f 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new 3feeb870d28 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] new f1153e8fba8 202: onsuccess: #1856: 7: Success after gcc: 2 commits new 3874f98c70e 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] new 8dd5013d49f 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] new a84ddbc01f4 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 291ced2be33 206: onsuccess: #1860: 7: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (8bac11c1fed) \ 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 1760 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 31776 -> 31764 bytes 05-build_abe-stage1/console.log.xz | Bin 72980 -> 73740 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8692 -> 8708 bytes 08-build_abe-glibc/console.log.xz | Bin 244256 -> 245336 bytes 09-build_abe-stage2/console.log.xz | Bin 204344 -> 204500 bytes 10-build_abe-gdb/console.log.xz | Bin 38792 -> 38800 bytes 11-build_abe-qemu/console.log.xz | Bin 30588 -> 30796 bytes 12-check_regression/console.log.xz | Bin 3336 -> 3164 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 ++++++------- 18 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (dad22d3986a -> bcaa95a0951)

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 dad22d3986a 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards 7301856e9e4 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] discards 585a4ce975a 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards c62cfd6aec8 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards 4537c35d42e 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards dc1084f4d2a 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards 390c496e00d 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 91612b6cda0 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards 7e4c73ea113 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 27810f41c4a 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards 01000e8a222 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards 0beed4b1b4b 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards 8c4756c2925 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 2eb0a987d70 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards 16b97534b5a 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards 422529f3aeb 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards da7819e6c19 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 0d194f67651 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards 65b1ceffc1f 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards 52beb1d72d3 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards e0d070b82bc 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards 94655624190 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards ef901050a5e 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards cf64008f42e 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards da918056e92 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards 8535b27479c 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 4b0f1b86aa5 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards 7cb37b6b525 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 90b4be4501a 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 1afb0ee5f80 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards 0a1cac26e39 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards dffbb293bb7 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards f1842c9136d 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards a56cb6af631 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards 050c1ca3265 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards 9c8e27623e1 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards d776eb9ab20 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards bb5f207ab68 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards f131d3ec17c 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 8b4019ede9d 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 94b9beeff85 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards 6ee161bafeb 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 515e574eff7 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 2ce6270e62c 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 38724dbbe31 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards c183bd62a06 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 8ad4bee3f80 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards 74a00d337cd 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards f16f3794026 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 0ebd471c7ed 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards 837898ee5f7 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards 4c99120b83d 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards c7b168b10b6 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards b3d5d38d287 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards 12c082f16f2 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards 2cf05c8f851 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards 8f4faa05c84 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards cb75506db5c 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards 108d1d8f7a2 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards 214fe3c59bd 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards 5f657c3479f 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards fb949bc6db1 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards 655097d3bb8 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards 6cc1acaf3ee 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards 9c16f0de42d 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards a3aaf118280 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards 0dc948e7100 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards 66529be0d2c 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards 0d7002d6915 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 2610d862fbd 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] discards 46908f013e7 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards 834fe521846 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] discards f467f7b6606 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] discards 9e5e4cfcbaa 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] discards 6300d20754c 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] discards b1c8fbba32b 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards b89e00f88f0 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards 8b033b60374 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards 564ea23ba75 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards bb2929c4cd0 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards ce49d6b5b74 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards e059d631849 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards 30fb2c44b4f 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards c914ec413f4 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards fa8720d670d 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits discards 92a287c5e81 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits discards 1bfd9feab92 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits discards a34a03ac25c 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits discards 3bb91dc3c54 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits discards 2d815d5561f 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits discards 5fcb9450b63 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits discards 8b71b2c2743 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits discards 759a90af8e3 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits discards f90ba28c957 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits discards 8d63e21a46d 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits discards ec54b1b9d24 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits discards 2cb367bc2bb 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits discards 5ca48e3e8bf 283: onsuccess: #2222: 1: Success after gcc: 4 commits discards c5099bdc535 282: onsuccess: #2221: 1: Success after gcc: 2 commits discards eff5cb5c002 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits discards 1ffd9ce0f4f 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits new fea6075d4da 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits new ee7a25d7010 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits new b7ee533d7fe 282: onsuccess: #2221: 1: Success after gcc: 2 commits new d3984cb48b0 283: onsuccess: #2222: 1: Success after gcc: 4 commits new d03a908b74d 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits new 9f774961f2a 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits new 116e57ab40f 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits new 5905be6f1e8 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits new ecfc760d926 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new 01236fb583e 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits new 080ffdbf152 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits new 1e510d70fad 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits new d2f124ea723 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits new 64728bfd278 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits new 5d00ba312ba 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits new 3e5139039ec 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits new f2d68f61f7f 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new 58db3c547f2 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new 65bb09bad02 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new 4c3dfc3839d 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new cfb5a050f52 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new 827bc21a427 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new 0bd31f080d0 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new 8a8ad0dbb7b 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new 11ef093f43d 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new 23be70514e3 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new df48181f928 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] new ebf371e12bf 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] new 77cb2926fbd 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] new 7a642d587d4 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] new affd2087300 310: onsuccess: #2259: 1: Success after binutils: 2 commits new 1eeb2355450 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] new 25701727bba 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 6e96dabe895 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new 792e04626f3 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new c7c84f3bcab 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new c151e922aa5 316: onsuccess: #2270: 1: Success after gcc: 2 commits new 9afedf114e1 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new ba87118ee8b 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 98af4136c49 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 22b2381a0fb 320: onsuccess: #2274: 1: Success after gcc: 5 commits new afab57c9509 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 406affd03de 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new fed9b562e1a 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 1cffd4ecd52 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new d74babcc1f1 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new b38097a4890 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new b268204cb81 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 32c8a63a8a7 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new 94ef36f4c19 329: onsuccess: #2285: 1: Success after gcc: 8 commits new bf0430510c0 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 35a2ffa6949 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new e53398ea02e 332: onsuccess: #2288: 1: Success after gcc: 2 commits new 83f853bb132 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new a7b9635b767 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new ff01446f20a 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 2f53e8de988 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 76f6485cd2c 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 49e259a4437 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new e011cdbbc61 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new 647f3d22b38 340: onsuccess: #2296: 1: Success after gcc: 3 commits new dd5bf1d22ef 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new a8ab7992c63 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 9f2af8daff2 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 88e7f7dfa0a 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new 034b68b982d 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new 52aa06c68c0 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new be087db4336 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new dde8669dd93 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new dc37266a827 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new b36ca694545 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 980e47c181f 351: onsuccess: #2307: 1: Success after binutils: 2 commits new c5914a4c9d7 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new fb19e425df1 353: onsuccess: #2309: 1: Success after gcc: 7 commits new ae18a3a6348 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new f6c6a75403b 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 17eafe20d6a 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 5a46dcef592 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new 3411fc18061 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new a3a71cf193b 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new 98258d558f0 360: onsuccess: #2317: 1: Success after binutils: 4 commits new f23c903d6f5 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new 34e8e66533e 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 3f293563473 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new 8a6fefb2803 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new 8bca1a9eaf3 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new a4005488bb0 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new 395b0f0ed8c 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new 925ad874aec 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new 8ab1b9156da 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new 490b267735b 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new b5cf4aaff71 371: onsuccess: #2333: 1: Success after binutils: 5 commits new dcdb5535483 372: onsuccess: #2334: 1: Success after gcc: 5 commits new e5f072502f9 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 2ec7d9ea95f 374: onsuccess: #2336: 1: Success after gcc: 4 commits new b3dd378562c 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new e40fda5d5cb 376: onsuccess: #2338: 1: Success after gcc: 2 commits new 47b1fbf6f02 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new f1f52f551c3 378: onsuccess: #2340: 1: Success after binutils: 2 commits new 4913abd6a8e 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] new 2873af135ec 380: onsuccess: #2342: 1: Success after gcc: 3 commits new bcaa95a0951 381: onsuccess: #2343: 1: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (dad22d3986a) \ 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 1796 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39328 -> 39588 bytes 04-build_abe-gcc/console.log.xz | Bin 215160 -> 215896 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3884 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2720 bytes 07-check_regression/console.log.xz | Bin 4548 -> 4608 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 57 +- 08-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 3616548 -> 3636044 bytes sumfiles/g++.sum | 129 +- sumfiles/gcc.log.xz | Bin 3144672 -> 3143160 bytes sumfiles/gcc.sum | 5474 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1044464 -> 1047744 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219220 -> 218624 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451876 -> 455068 bytes sumfiles/libstdc++.sum | 12 +- 30 files changed, 2924 insertions(+), 2902 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[gcc] branch master updated (079add3ad39 -> 98d6e4b6f10)

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 079add3ad39 c++: pack in requires-expr parm list [PR107417] new 9123863828b Fortran: error recovery handling invalid CLASS variable [PR107899] new 98d6e4b6f10 Fortran: fix typo in documentation of intrinsic FLOOR [PR107870] The 2 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/fortran/intrinsic.texi | 60 +++++++++++++++++----------------- gcc/fortran/resolve.cc | 2 +- gcc/testsuite/gfortran.dg/pr107899.f90 | 13 ++++++++ 3 files changed, 44 insertions(+), 31 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/pr107899.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug updated (590d0234344 -> 55ddf822886)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug in repository toolchain/ci/base-artifacts. from 590d0234344 37: onsuccess: #160: 2: Success after binutils/gcc: 12 commits new 55ddf822886 38: onsuccess: #161: 2: Success after binutils/gcc: 6 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 1696 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 51864 -> 50860 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 461780 -> 461156 bytes 06-check_regression/console.log.xz | Bin 2900 -> 2616 bytes 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 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022