Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allmodconfig updated (1f16049f392d -> 61c1c6af8e29)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from 1f16049f392d 53: onsuccess: #591: 23766: Success after binutils/llvm/li [...] new 61c1c6af8e29 54: onsuccess: #592: all: Success after binutils/llvm/linu [...] 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 1792 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 32156 -> 32480 bytes 04-build_kernel_llvm/console.log.xz | Bin 66328 -> 66124 bytes 05-build_abe-qemu/console.log.xz | Bin 31460 -> 31520 bytes 06-build_linux/console.log.xz | Bin 3820 -> 3204 bytes 07-boot_linux/console.log.xz | Bin 0 -> 508 bytes 08-check_regression/console.log.xz | Bin 4544 -> 4532 bytes 08-check_regression/mail-body.txt | 6 ++++-- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 8 +++++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 4 +++- 20 files changed, 38 insertions(+), 32 deletions(-) create mode 100644 07-boot_linux/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_ubsan updated (2ac7de1dcdb0 -> a2d93b238970)

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-aarch64-bootstrap_ubsan in repository toolchain/ci/base-artifacts. from 2ac7de1dcdb0 39: onsuccess: #146: 2: Success after binutils/gcc: 11 commits new a2d93b238970 40: onsuccess: #147: 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 1740 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 38388 -> 37896 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 323648 -> 319620 bytes 06-check_regression/console.log.xz | Bin 2848 -> 2600 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 | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-defconfig updated (bef31d25d35e -> 22bca07530ce)

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-stable-defconfig in repository toolchain/ci/base-artifacts. from bef31d25d35e 34: onsuccess: #515: boot: Success after binutils/gcc/linu [...] new 22bca07530ce 35: onsuccess: #516: boot: Success after binutils/gcc/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 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31800 -> 32500 bytes 04-build_abe-stage1/console.log.xz | Bin 73864 -> 74176 bytes 05-build_abe-qemu/console.log.xz | Bin 31012 -> 31356 bytes 06-build_linux/console.log.xz | Bin 6580 -> 6512 bytes 07-boot_linux/console.log.xz | Bin 6224 -> 6256 bytes 08-check_regression/console.log.xz | Bin 4080 -> 3924 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 16 files changed, 20 insertions(+), 20 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (9fe322ae1605 -> 41858838b2ea)

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 9fe322ae1605 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: [...] discards c296782bab5b 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: [...] discards 75c705deeb8c 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/q [...] discards 9c63495effce 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 962199893943 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards a1e7bc1bc4c9 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: [...] discards 0c1e65ef1a10 244: onsuccess: #1941: 7: Success after binutils/gcc/linux [...] discards 26a36cbdc737 243: onsuccess: #1940: 7: Success after binutils/gcc/linux [...] discards 3adb7278ca37 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/q [...] discards 28f80365f9da 241: onsuccess: #1938: 7: Success after binutils/gcc/linux [...] discards a66c1ec12a37 240: onsuccess: #1937: 7: Success after binutils/gcc/linux [...] discards f88a3474c9b4 239: onsuccess: #1936: 7: Success after binutils/gcc/linux [...] discards a5fd7a108d97 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/q [...] discards 544b9bc82031 237: onsuccess: #1934: 7: Success after basepoints/gcc-13- [...] discards 3daecd335d54 236: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] discards 1b5e592b9aaa 235: onsuccess: #1932: 7: Success after binutils/gcc/linux [...] discards 3a8468842e83 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: [...] discards 901cfe03d9b1 233: onsuccess: #1930: 7: Success after binutils/gcc/linux [...] discards 92927b656ee0 232: onsuccess: #1929: 7: Success after binutils/gcc/linux [...] discards ddde65edd36e 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards 75d9ad0d3e0a 230: force: #1927: 3: Failure after basepoints/gcc-13-4618 [...] discards 7781ce167369 229: force: #1926: 7: Success after gcc: 7 commits discards 661279ea272e 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint [...] discards f72fb775a27b 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards c1c2ee718a94 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: [...] discards 416ae209947b 225: onsuccess: #1903: 7: Success after binutils/gcc/linux [...] discards 4d67c86f4c32 224: onsuccess: #1902: 7: Success after binutils/gcc/linux [...] discards fb5a438f311c 223: onsuccess: #1901: 7: Success after basepoints/gcc-13- [...] discards 0a411b5e05ee 222: onsuccess: #1900: 7: Success after binutils/gcc/linux [...] discards 8ca109f5659b 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: [...] discards aa7ca59ea711 220: onsuccess: #1898: 7: Success after binutils/linux/gli [...] discards d100e4e7b55c 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: [...] discards 73080156c696 218: onsuccess: #1896: 7: Success after binutils/gcc/linux [...] discards a1188522cabd 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: [...] discards 6ab073be545e 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards e88c57d565ba 215: onsuccess: #1891: 7: Success after binutils/gcc/linux [...] discards 4dbc76b9457d 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc [...] discards 3bb0ec144149 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 370edc776d8d 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc [...] discards 804effc462b7 211: onsuccess: #1887: 7: Success after binutils/gcc/linux [...] discards 7c62bc6ffbd3 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards c5904ef2c7f5 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/q [...] discards 885642ac0422 208: onsuccess: #1865: 7: Success after linux: 12 commits discards ac61141d21c5 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 239709a5b233 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards fca37e364148 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 5411f2654165 204: onsuccess: #1858: 7: Success after binutils/gcc/linux [...] discards ef9c4881103a 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: [...] discards 3e70fdab431b 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 08dce0725248 201: onsuccess: #1855: 7: Success after binutils/gcc/linux [...] discards 944f3f3cd64f 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards 510be2b4fa48 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: [...] discards b59a8a4009e1 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 2b17a99d58d9 197: onsuccess: #1851: 7: Success after binutils/gcc/linux [...] discards 1b59b7c947eb 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: [...] discards fcdb431f73fc 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: [...] discards bebeb457fb3c 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: [...] discards d907212f98b5 193: onsuccess: #1847: 7: Success after binutils/gcc/linux [...] discards ffd452d683a2 192: onsuccess: #1816: 7: Success after binutils/gcc/linux [...] discards 5c24f58437b6 191: onsuccess: #1808: 7: Success after binutils/gcc/linux [...] discards 5fb98eb56965 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 4feff557ec0f 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: [...] discards 58a18f7c2bb0 188: onsuccess: #1765: 7: Success after binutils/gcc/linux [...] discards 8ed3d8447d70 187: onsuccess: #1763: 7: Success after binutils/gcc/linux [...] discards f5cff190a9dc 186: onsuccess: #1761: 7: Success after binutils/gcc/linux [...] discards 28757c04ed81 185: onsuccess: #1716: 7: Success after binutils/linux/gdb [...] discards d8bea5b37ae4 184: onsuccess: #1715: 7: Success after binutils/gcc/linux [...] discards c7888b13dbe2 183: onsuccess: #1712: 7: Success after binutils/gcc/linux [...] discards 56e67fec81fb 182: onsuccess: #1711: 7: Success after binutils/gcc/linux [...] discards 5c3e54018ff8 181: onsuccess: #1700: 7: Success after binutils/gcc/linux [...] discards 3f33fadcce2b 180: onsuccess: #1636: 7: Success after binutils/linux/gdb [...] discards 20e935f71422 179: onsuccess: #1634: 7: Success after binutils/gcc/linux [...] discards c2526e0968e0 178: onsuccess: #1631: 7: Success after binutils/gcc/linux [...] discards 43bf02044122 177: onsuccess: #1630: 7: Success after binutils/gcc/linux [...] discards e55386d432a4 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc [...] discards bc7c2d9e4168 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc [...] discards 3eb46c55108a 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: [...] discards 956112d5bf26 173: onsuccess: #1626: 7: Success after binutils/gcc/linux [...] discards 63c3545432da 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qe [...] discards bbaa4691813a 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: [...] discards 8a7d8d2396ad 170: onsuccess: #1623: 7: Success after binutils/gcc/linux [...] discards b345e61bd01e 169: onsuccess: #1622: 7: Success after binutils/gcc/linux [...] discards 69a44b5ebce6 168: onsuccess: #1621: 7: Success after binutils/gcc/linux [...] discards 4c3e47d9a496 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: [...] discards 7c842b963f70 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 7effaaf93c00 165: onsuccess: #1618: 7: Success after binutils/gcc/linux [...] discards 08c1c77a07f8 164: onsuccess: #1617: 7: Success after binutils/gcc/linux [...] discards 10265b73aa87 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: [...] discards 312a5915d043 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: [...] discards 6cedb1f9cea1 161: onsuccess: #1614: 7: Success after binutils/gcc/linux [...] discards 05fd6dab3f1b 160: onsuccess: #1613: 7: Success after binutils/gcc/linux [...] discards 57afa3f86121 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 55d29eb5627e 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc [...] discards 161f09d5c8ae 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 9a5982ad3544 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 66473edc4146 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gd [...] discards 234fb84d9849 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards db242c97b3fd 153: force: #1606: 1: Failure after basepoints/gcc-13-3004 [...] discards f8ba556df827 152: force: #1605: 7: Success after gcc: 9 commits discards e9c75d0a9a65 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint [...] discards 576ddb321290 150: onsuccess: #1601: 7: Success after binutils/gcc/linux [...] new ea3337bdb1c4 150: onsuccess: #1601: 7: Success after binutils/gcc/linux [...] new f6858ff00752 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint [...] new 4499235134ff 152: force: #1605: 7: Success after gcc: 9 commits new 67a5fa570430 153: force: #1606: 1: Failure after basepoints/gcc-13-3004 [...] new c8fb4fe43b24 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 9b16838cee0e 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gd [...] new 8a89bcd137d4 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 76d280a2b1b8 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 64041b24bd24 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc [...] new e660503cd023 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 32ec725a3f21 160: onsuccess: #1613: 7: Success after binutils/gcc/linux [...] new 2dd4f9592bae 161: onsuccess: #1614: 7: Success after binutils/gcc/linux [...] new 94a91812ecc2 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: [...] new 2ea6b6508c25 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: [...] new 8a2c3dbf2cfb 164: onsuccess: #1617: 7: Success after binutils/gcc/linux [...] new f8d62350e182 165: onsuccess: #1618: 7: Success after binutils/gcc/linux [...] new ffdffa058816 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 66e92ce1e644 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: [...] new 2585bcd107eb 168: onsuccess: #1621: 7: Success after binutils/gcc/linux [...] new efbf27ec3a8c 169: onsuccess: #1622: 7: Success after binutils/gcc/linux [...] new 635143c0bca3 170: onsuccess: #1623: 7: Success after binutils/gcc/linux [...] new f88c86bbeed7 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: [...] new cba2a30c513e 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qe [...] new 512b45f03a9a 173: onsuccess: #1626: 7: Success after binutils/gcc/linux [...] new 7f6f28a4fc16 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: [...] new 305a6f738077 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc [...] new 714ff684c09a 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc [...] new 6e22d36fc3b4 177: onsuccess: #1630: 7: Success after binutils/gcc/linux [...] new f525b4813100 178: onsuccess: #1631: 7: Success after binutils/gcc/linux [...] new d24c59497853 179: onsuccess: #1634: 7: Success after binutils/gcc/linux [...] new ecce37649015 180: onsuccess: #1636: 7: Success after binutils/linux/gdb [...] new 766d1e4be366 181: onsuccess: #1700: 7: Success after binutils/gcc/linux [...] new 3afac4661d39 182: onsuccess: #1711: 7: Success after binutils/gcc/linux [...] new 883605b9c402 183: onsuccess: #1712: 7: Success after binutils/gcc/linux [...] new b03a81b3a6d6 184: onsuccess: #1715: 7: Success after binutils/gcc/linux [...] new cc910573406c 185: onsuccess: #1716: 7: Success after binutils/linux/gdb [...] new 669d681b3b24 186: onsuccess: #1761: 7: Success after binutils/gcc/linux [...] new 304324f33f57 187: onsuccess: #1763: 7: Success after binutils/gcc/linux [...] new 8cfd32886629 188: onsuccess: #1765: 7: Success after binutils/gcc/linux [...] new b844ed0ea6de 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: [...] new d887af8e37cd 190: onsuccess: #1774: 7: Success after binutils: 10 commits new cf3761f58385 191: onsuccess: #1808: 7: Success after binutils/gcc/linux [...] new 8a14a2c1a136 192: onsuccess: #1816: 7: Success after binutils/gcc/linux [...] new f08c430c2ca0 193: onsuccess: #1847: 7: Success after binutils/gcc/linux [...] new 7e4f6ecb707b 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: [...] new 250fe570d599 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: [...] new 54bf0af8037a 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: [...] new 2fe29c6012f2 197: onsuccess: #1851: 7: Success after binutils/gcc/linux [...] new de40bc9b7a20 198: onsuccess: #1852: 7: Success after gcc: 5 commits new 848349fb463f 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: [...] new 53da2c4a2f21 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new 62248868d273 201: onsuccess: #1855: 7: Success after binutils/gcc/linux [...] new a89c900b6176 202: onsuccess: #1856: 7: Success after gcc: 2 commits new 3a57226d5f47 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: [...] new 39d4c0fcd23e 204: onsuccess: #1858: 7: Success after binutils/gcc/linux [...] new 9a725e6d4ecc 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 771e195b4b61 206: onsuccess: #1860: 7: Success after gcc: 2 commits new 372cc8ff7d31 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 121c8cb60877 208: onsuccess: #1865: 7: Success after linux: 12 commits new 1048b24adfd4 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/q [...] new 6403c7dbf777 210: onsuccess: #1868: 7: Success after binutils: 7 commits new d7003cef0586 211: onsuccess: #1887: 7: Success after binutils/gcc/linux [...] new 09e80e31e441 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc [...] new dd79c972a815 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 221de2dda8e7 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc [...] new 579c9004a854 215: onsuccess: #1891: 7: Success after binutils/gcc/linux [...] new 1900dd79f276 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new d87cac197791 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: [...] new b1c20fc766fa 218: onsuccess: #1896: 7: Success after binutils/gcc/linux [...] new 008eef6668dd 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: [...] new 4c7f5cee6707 220: onsuccess: #1898: 7: Success after binutils/linux/gli [...] new c851f82796a9 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: [...] new 6144ff403aee 222: onsuccess: #1900: 7: Success after binutils/gcc/linux [...] new cb24740a3a0d 223: onsuccess: #1901: 7: Success after basepoints/gcc-13- [...] new d310322e229e 224: onsuccess: #1902: 7: Success after binutils/gcc/linux [...] new 0c72b4b89b9b 225: onsuccess: #1903: 7: Success after binutils/gcc/linux [...] new 30376a5cd9cf 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: [...] new ea0643efc817 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 535fcaccc34d 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint [...] new 203f4b9525be 229: force: #1926: 7: Success after gcc: 7 commits new 47a25248c300 230: force: #1927: 3: Failure after basepoints/gcc-13-4618 [...] new 78cb188f1258 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 2a83ca2fda59 232: onsuccess: #1929: 7: Success after binutils/gcc/linux [...] new aa72f5e2c6f3 233: onsuccess: #1930: 7: Success after binutils/gcc/linux [...] new 6897eb293f27 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: [...] new dd7d1ecbf119 235: onsuccess: #1932: 7: Success after binutils/gcc/linux [...] new ef14a1321eda 236: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] new 1006f89774ec 237: onsuccess: #1934: 7: Success after basepoints/gcc-13- [...] new 242bac7c9762 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/q [...] new 6bdcd0833f0c 239: onsuccess: #1936: 7: Success after binutils/gcc/linux [...] new 73c45898d7ed 240: onsuccess: #1937: 7: Success after binutils/gcc/linux [...] new 3244f7594481 241: onsuccess: #1938: 7: Success after binutils/gcc/linux [...] new 5dd427d2c1a1 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/q [...] new 5f4534335faa 243: onsuccess: #1940: 7: Success after binutils/gcc/linux [...] new 9d8b63dd5137 244: onsuccess: #1941: 7: Success after binutils/gcc/linux [...] new 9eba29b88887 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: [...] new 25d2c731e822 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new f66dd5a462fe 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 98f7571a52f2 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/q [...] new 32acc3627410 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: [...] new 415a51ef0112 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: [...] new 41858838b2ea 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4a [...] 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 (9fe322ae1605) \ 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 1720 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2800 bytes 04-build_abe-binutils/console.log.xz | Bin 32764 -> 32512 bytes 05-build_abe-stage1/console.log.xz | Bin 74204 -> 74052 bytes 07-build_abe-linux/console.log.xz | Bin 8696 -> 8660 bytes 08-build_abe-glibc/console.log.xz | Bin 245612 -> 244216 bytes 09-build_abe-stage2/console.log.xz | Bin 205588 -> 207432 bytes 10-build_abe-gdb/console.log.xz | Bin 39488 -> 39392 bytes 11-build_abe-qemu/console.log.xz | Bin 32188 -> 31164 bytes 12-check_regression/console.log.xz | Bin 3572 -> 3164 bytes 13-update_baseline/console.log | 52 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++++-------- 17 files changed, 42 insertions(+), 42 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch releases/gcc-10 updated (e85a0a23873 -> 6f2f588377e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from e85a0a23873 Daily bump. new 6f2f588377e Fortran: ICE on recursive derived types with allocatable co [...] 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/resolve.c | 3 ++- gcc/testsuite/gfortran.dg/pr107872.f90 | 40 ++++++++++++++++++++++++++++++++++ 2 files changed, 42 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gfortran.dg/pr107872.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (dc83705d2b38 -> 4076c64933ec)

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 dc83705d2b38 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] new 4076c64933ec 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 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 1788 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 52784 -> 52688 bytes 04-build_abe-gcc/console.log.xz | Bin 234156 -> 233664 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 234720 -> 234800 bytes 08-build_abe-gdb/console.log.xz | Bin 52572 -> 51124 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3824 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3028 -> 2580 bytes 11-check_regression/console.log.xz | Bin 5812 -> 5404 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- sumfiles/gdb.log.xz | Bin 14456 -> 14464 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 23 files changed, 43 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch releases/gcc-12 updated (3f578d958a1 -> 7a9741d7322)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 3f578d958a1 Daily bump. new 7a9741d7322 Fortran: ICE on recursive derived types with allocatable co [...] 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/resolve.cc | 3 ++- gcc/testsuite/gfortran.dg/pr107872.f90 | 40 ++++++++++++++++++++++++++++++++++ 2 files changed, 42 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gfortran.dg/pr107872.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch releases/gcc-11 updated (2e6c98ba5a3 -> cc956b955d1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 2e6c98ba5a3 Daily bump. new cc956b955d1 Fortran: ICE on recursive derived types with allocatable co [...] 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/resolve.c | 3 ++- gcc/testsuite/gfortran.dg/pr107872.f90 | 40 ++++++++++++++++++++++++++++++++++ 2 files changed, 42 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gfortran.dg/pr107872.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-defconfig updated (0cb316a5a7f7 -> 8d97ae1a63fe)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from 0cb316a5a7f7 31: onsuccess: #485: boot: Success after binutils/llvm/lin [...] new 8d97ae1a63fe 32: onsuccess: #486: boot: Success after binutils/llvm/qem [...] 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 1768 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32032 -> 32480 bytes 04-build_kernel_llvm/console.log.xz | Bin 66244 -> 66772 bytes 05-build_abe-qemu/console.log.xz | Bin 31592 -> 31904 bytes 06-build_linux/console.log.xz | Bin 3444 -> 3444 bytes 07-boot_linux/console.log.xz | Bin 6256 -> 6252 bytes 08-check_regression/console.log.xz | Bin 4360 -> 4196 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (0b2428ee830 -> fd69977febf)

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 0b2428ee830 PR-108122 Reduce sleep times in gm2/pimcoroutines/run/pass/ [...] new fd69977febf build: doc: Obsolete Solaris 11.3 support 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/config.gcc | 21 ++++++++++++++++----- gcc/doc/install.texi | 2 ++ 2 files changed, 18 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022