Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[gcc] branch master updated (a6504f13a05 -> aed5584ff68)

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 a6504f13a05 coroutines: Accept 'extern "C"' coroutines. new aed5584ff68 Fortran: a C interoperable function cannot have the CLASS a [...] 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/decl.cc | 12 ++++++++---- gcc/testsuite/gfortran.dg/bind_c_procs_4.f90 | 17 +++++++++++++++++ 2 files changed, 25 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/bind_c_procs_4.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/gnu-release-aarch64-next-defconfig updated (78c4e62bf042 -> dcd1bdfa2311)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-defconfig in repository toolchain/ci/base-artifacts. from 78c4e62bf042 30: onsuccess: #558: boot: Success after binutils/gcc/linu [...] new dcd1bdfa2311 31: onsuccess: #559: boot: Success after binutils/gcc/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 1772 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30300 -> 30340 bytes 04-build_abe-stage1/console.log.xz | Bin 68560 -> 68736 bytes 05-build_abe-qemu/console.log.xz | Bin 31588 -> 31136 bytes 06-build_linux/console.log.xz | Bin 3068 -> 3072 bytes 07-boot_linux/console.log.xz | Bin 6132 -> 6116 bytes 08-check_regression/console.log.xz | Bin 4136 -> 4216 bytes 08-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 18 files changed, 25 insertions(+), 25 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_gcc_bootstrap/master-aarch64-bootstrap updated (dfc13ecc4788 -> 7ee9af8c870b)

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/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards dfc13ecc4788 444: onsuccess: #1883: 2: Success after binutils/gcc: 16 commits discards 958e7d5232d1 443: onsuccess: #1882: 1: Success after basepoints/gcc-13- [...] discards d42d4c453e08 442: force: #1881: 1: Failure after basepoints/gcc-13-4795 [...] discards 437d95a6692c 441: force: #1880: 2: Success after gcc: 15 commits discards aeb6061b3069 440: onsuccess: #1877: 2: Success after binutils: 6 commits discards 8acb9917394d 439: onsuccess: #1875: 2: Success after binutils/gcc: 23 commits discards 5ddf4c731ed4 438: onsuccess: #1874: 2: Success after binutils/gcc: 2 commits discards 89550b519600 437: onsuccess: #1873: 2: Success after basepoints/gcc-13- [...] discards b9e43bd7c88d 436: onsuccess: #1872: 2: Success after binutils/gcc: 3 commits discards 3f24cde18317 435: onsuccess: #1871: 2: Success after binutils/gcc: 3 commits discards a6412f82f470 434: onsuccess: #1870: 2: Success after binutils/gcc: 3 commits discards 5fba92864f10 433: onsuccess: #1869: 2: Success after basepoints/gcc-13- [...] discards fc5aaffbe90a 432: onsuccess: #1868: 2: Success after binutils: 3 commits discards ba22f9f3c046 431: onsuccess: #1867: 2: Success after binutils/gcc: 7 commits discards 521a7a565937 430: onsuccess: #1866: 2: Success after binutils/gcc: 10 commits discards 440e87b17629 429: onsuccess: #1865: 2: Success after binutils/gcc: 9 commits discards 6cfa5ba0623b 428: onsuccess: #1864: 2: Success after binutils/gcc: 14 commits discards 0958f86403a2 427: onsuccess: #1863: 2: Success after binutils/gcc: 6 commits discards 6da9df402cb4 426: onsuccess: #1862: 2: Success after binutils/gcc: 11 commits discards 50375da111da 425: onsuccess: #1861: 2: Success after binutils/gcc: 9 commits discards aba217430d78 424: onsuccess: #1860: 2: Success after binutils/gcc: 13 commits discards 905f06e9c662 423: onsuccess: #1859: 2: Success after basepoints/gcc-13- [...] discards 2dbf47e8e266 422: onsuccess: #1858: 2: Success after binutils/gcc: 3 commits discards e42d9c0196f5 421: onsuccess: #1857: 2: Success after gcc: 10 commits discards 5929998a9908 420: onsuccess: #1856: 2: Success after binutils/gcc: 19 commits discards 16aa7ff2d3c3 419: onsuccess: #1855: 2: Success after binutils/gcc: 6 commits discards 889edd8312d1 418: onsuccess: #1854: 2: Success after binutils/gcc: 12 commits discards fce5bc2cd164 417: onsuccess: #1853: 2: Success after binutils/gcc: 12 commits discards ae3ff5bbab5e 416: onsuccess: #1852: 2: Success after binutils/gcc: 52 commits discards 9d8af6d32a04 415: onsuccess: #1851: 2: Success after binutils: 5 commits discards 88f49b711a07 414: onsuccess: #1850: 2: Success after binutils/gcc: 4 commits discards d2e13b778983 413: onsuccess: #1849: 2: Success after binutils/gcc: 12 commits discards 6f9f306e5623 412: onsuccess: #1848: 2: Success after binutils/gcc: 24 commits discards 9336349932a0 411: onsuccess: #1847: 2: Success after binutils/gcc: 7 commits discards 94c32dab983e 410: onsuccess: #1846: 2: Success after binutils/gcc: 2 commits discards 09ec32dd95d0 409: onsuccess: #1845: 2: Success after gcc: 5 commits discards cddc5bb69d42 408: onsuccess: #1844: 2: Success after binutils/gcc: 5 commits discards 203167a0050c 407: onsuccess: #1843: 2: Success after binutils/gcc: 3 commits discards 7140f54481da 406: onsuccess: #1842: 2: Success after binutils/gcc: 13 commits discards 43e7c0d5b4d5 405: onsuccess: #1841: 2: Success after binutils: 6 commits discards 6d41aa5668d8 404: onsuccess: #1840: 2: Success after binutils/gcc: 6 commits discards d1c12a48c22c 403: onsuccess: #1839: 2: Success after gcc: 6 commits discards 7d1b7dae08d8 402: onsuccess: #1838: 2: Success after binutils/gcc: 8 commits discards dacb97fb89fd 401: onsuccess: #1837: 2: Success after binutils/gcc: 25 commits discards f68236cbd1f2 400: onsuccess: #1835: 2: Success after binutils/gcc: 6 commits discards bff6259977da 399: onsuccess: #1834: 2: Success after binutils/gcc: 11 commits discards ee4441f38b09 398: onsuccess: #1833: 2: Success after gcc: 5 commits discards f85569544373 397: onsuccess: #1832: 2: Success after binutils: 5 commits discards 7e38d8f1cb16 396: onsuccess: #1831: 2: Success after binutils/gcc: 13 commits discards 9c3ff5870ec1 395: onsuccess: #1830: 2: Success after binutils/gcc: 7 commits discards 117632d6ebc9 394: onsuccess: #1829: 2: Success after binutils/gcc: 21 commits discards 6911a4e25653 393: onsuccess: #1828: 2: Success after binutils/gcc: 6 commits discards 1a76b5230eba 392: onsuccess: #1827: 2: Success after binutils/gcc: 12 commits discards 22e851cca385 391: onsuccess: #1826: 2: Success after binutils/gcc: 5 commits discards ebe85fe74af2 390: onsuccess: #1825: 2: Success after binutils/gcc: 15 commits discards 78074bc3a94d 389: onsuccess: #1824: 2: Success after binutils/gcc: 2 commits discards 8a1ec220ce96 388: onsuccess: #1823: 2: Success after binutils/gcc: 5 commits discards d1070e955d9c 387: onsuccess: #1822: 2: Success after gcc: 5 commits discards db6e631ee3fb 386: onsuccess: #1821: 2: Success after gcc: 3 commits discards d4d688e484f2 385: onsuccess: #1820: 2: Success after binutils/gcc: 2 commits discards 3a0b9660f562 384: onsuccess: #1819: 2: Success after binutils/gcc: 4 commits discards eb4ffbd4cb6b 383: onsuccess: #1818: 2: Success after binutils/gcc: 8 commits discards 5ff0dd1103ce 382: onsuccess: #1817: 2: Success after binutils/gcc: 6 commits discards cbe1d7f57d5f 381: onsuccess: #1816: 2: Success after binutils/gcc: 12 commits discards 3010a6eb04c7 380: onsuccess: #1815: 2: Success after binutils/gcc: 5 commits discards 12eb8486c2a4 379: onsuccess: #1814: 2: Success after binutils/gcc: 4 commits discards 9130ab53fa18 378: onsuccess: #1813: 2: Success after binutils/gcc: 20 commits discards e5f90c860999 377: onsuccess: #1812: 2: Success after binutils/gcc: 16 commits discards b049abadc8da 376: onsuccess: #1811: 2: Success after binutils/gcc: 14 commits discards 54ad2024e1a5 375: onsuccess: #1810: 2: Success after binutils/gcc: 8 commits discards babc7be97f03 374: onsuccess: #1809: 2: Success after binutils/gcc: 14 commits discards b6064b318e91 373: onsuccess: #1808: 2: Success after binutils/gcc: 11 commits discards 560dc2028bcd 372: onsuccess: #1807: 2: Success after binutils/gcc: 8 commits discards 7346c9c3fb0b 371: onsuccess: #1806: 2: Success after binutils/gcc: 8 commits discards af81c6cd42a3 370: onsuccess: #1805: 2: Success after binutils/gcc: 7 commits discards a8543003c162 369: onsuccess: #1804: 2: Success after gcc: 7 commits discards 6f0d9e773e8e 368: onsuccess: #1803: 2: Success after binutils/gcc: 3 commits discards 48624de0fa7b 367: onsuccess: #1802: 2: Success after binutils/gcc: 22 commits discards 24584f0f8322 366: onsuccess: #1801: 2: Success after binutils/gcc: 31 commits discards ec830ecf936a 365: onsuccess: #1800: 2: Success after binutils/gcc: 59 commits discards 7b1783fedf82 364: onsuccess: #1799: 2: Success after binutils/gcc: 5 commits discards 4376b143c350 363: onsuccess: #1798: 2: Success after binutils/gcc: 4 commits discards ab397c8148e2 362: onsuccess: #1797: 2: Success after binutils: 2 commits discards 5c73a2def3fb 361: onsuccess: #1796: 2: Success after gdb-12-branchpoint [...] discards 5b172ea7a2f6 360: onsuccess: #1795: 2: Success after binutils/gcc: 2 commits discards 3c1432a2cf1b 359: onsuccess: #1794: 2: Success after basepoints/gcc-13- [...] discards 34c00f406e99 358: onsuccess: #1793: 2: Success after binutils: 4 commits discards 985460dd2cd7 357: onsuccess: #1792: 2: Success after binutils/gcc: 2 commits discards 04af65c2ac00 356: onsuccess: #1791: 2: Success after gcc: 6 commits discards a098543d1ceb 355: onsuccess: #1790: 2: Success after binutils/gcc: 10 commits discards 3385caebee01 354: onsuccess: #1789: 2: Success after binutils/gcc: 2 commits discards 76fc9120827c 353: onsuccess: #1788: 2: Success after binutils/gcc: 3 commits discards 97176902152f 352: onsuccess: #1787: 2: Success after binutils: 16 commits discards cfe6b2568863 351: onsuccess: #1786: 2: Success after binutils/gcc: 14 commits discards e7aed95f4f04 350: onsuccess: #1785: 2: Success after binutils/gcc: 10 commits discards 99ee5544904e 349: onsuccess: #1784: 2: Success after binutils/gcc: 8 commits discards baaf48b6c4a0 348: onsuccess: #1783: 2: Success after gcc: 4 commits discards 8f9dd7d61ff7 347: onsuccess: #1782: 2: Success after binutils/gcc: 17 commits discards a8bb2753b8a3 346: onsuccess: #1781: 1: Success after gcc: 4 commits discards 6b8f4f331cbf 345: force: #1780: 1: Failure after basepoints/gcc-13-4252 [...] discards d709e7252a6d 344: force: #1779: 2: Success after gcc: 6 commits new 08c384236bce 344: force: #1779: 2: Success after gcc: 6 commits new af8f18f465cc 345: force: #1780: 1: Failure after basepoints/gcc-13-4252 [...] new e660a468b70b 346: onsuccess: #1781: 1: Success after gcc: 4 commits new 7842804b85eb 347: onsuccess: #1782: 2: Success after binutils/gcc: 17 commits new f0181b58de4c 348: onsuccess: #1783: 2: Success after gcc: 4 commits new bfb83af233ee 349: onsuccess: #1784: 2: Success after binutils/gcc: 8 commits new a46184009341 350: onsuccess: #1785: 2: Success after binutils/gcc: 10 commits new 58f4fedd3e84 351: onsuccess: #1786: 2: Success after binutils/gcc: 14 commits new e0b5ec4e45c4 352: onsuccess: #1787: 2: Success after binutils: 16 commits new 87674ade5cd3 353: onsuccess: #1788: 2: Success after binutils/gcc: 3 commits new 33719ac10b48 354: onsuccess: #1789: 2: Success after binutils/gcc: 2 commits new 8f65aa3f8bc9 355: onsuccess: #1790: 2: Success after binutils/gcc: 10 commits new 20ca975c272d 356: onsuccess: #1791: 2: Success after gcc: 6 commits new 935cce8ebc73 357: onsuccess: #1792: 2: Success after binutils/gcc: 2 commits new 4074cf7f6de1 358: onsuccess: #1793: 2: Success after binutils: 4 commits new 1d4819426518 359: onsuccess: #1794: 2: Success after basepoints/gcc-13- [...] new 2e6d7e2c5e95 360: onsuccess: #1795: 2: Success after binutils/gcc: 2 commits new b153562545e4 361: onsuccess: #1796: 2: Success after gdb-12-branchpoint [...] new b1d5f608cd23 362: onsuccess: #1797: 2: Success after binutils: 2 commits new 03656859c33d 363: onsuccess: #1798: 2: Success after binutils/gcc: 4 commits new 12be7567f903 364: onsuccess: #1799: 2: Success after binutils/gcc: 5 commits new bfddbbce54c8 365: onsuccess: #1800: 2: Success after binutils/gcc: 59 commits new 1e123d4374ed 366: onsuccess: #1801: 2: Success after binutils/gcc: 31 commits new 9b45d7110a85 367: onsuccess: #1802: 2: Success after binutils/gcc: 22 commits new 83adaa59adbe 368: onsuccess: #1803: 2: Success after binutils/gcc: 3 commits new 989a2aa8f28a 369: onsuccess: #1804: 2: Success after gcc: 7 commits new 637133ce973a 370: onsuccess: #1805: 2: Success after binutils/gcc: 7 commits new 548a023762d2 371: onsuccess: #1806: 2: Success after binutils/gcc: 8 commits new 85563d4729e1 372: onsuccess: #1807: 2: Success after binutils/gcc: 8 commits new 638dcdb2857e 373: onsuccess: #1808: 2: Success after binutils/gcc: 11 commits new bb5d9227db89 374: onsuccess: #1809: 2: Success after binutils/gcc: 14 commits new 7e47e9f1e766 375: onsuccess: #1810: 2: Success after binutils/gcc: 8 commits new 8325155a2b20 376: onsuccess: #1811: 2: Success after binutils/gcc: 14 commits new 4d7e7d46fc5e 377: onsuccess: #1812: 2: Success after binutils/gcc: 16 commits new a7f0e7087b15 378: onsuccess: #1813: 2: Success after binutils/gcc: 20 commits new b83135922f71 379: onsuccess: #1814: 2: Success after binutils/gcc: 4 commits new 51656071e09c 380: onsuccess: #1815: 2: Success after binutils/gcc: 5 commits new 56f3159700f4 381: onsuccess: #1816: 2: Success after binutils/gcc: 12 commits new 5ac912017a16 382: onsuccess: #1817: 2: Success after binutils/gcc: 6 commits new 51f03db71e0f 383: onsuccess: #1818: 2: Success after binutils/gcc: 8 commits new 16b1d4aa14fb 384: onsuccess: #1819: 2: Success after binutils/gcc: 4 commits new 302ab17fd0b3 385: onsuccess: #1820: 2: Success after binutils/gcc: 2 commits new 0ae8e1fb4933 386: onsuccess: #1821: 2: Success after gcc: 3 commits new 94cebe875210 387: onsuccess: #1822: 2: Success after gcc: 5 commits new 8d02231225fc 388: onsuccess: #1823: 2: Success after binutils/gcc: 5 commits new d987a7c259e3 389: onsuccess: #1824: 2: Success after binutils/gcc: 2 commits new 3f80b792cd6e 390: onsuccess: #1825: 2: Success after binutils/gcc: 15 commits new c30b3fa98f2c 391: onsuccess: #1826: 2: Success after binutils/gcc: 5 commits new f86d9b3a1fde 392: onsuccess: #1827: 2: Success after binutils/gcc: 12 commits new 2e97472fc6b4 393: onsuccess: #1828: 2: Success after binutils/gcc: 6 commits new c261c88b3bf5 394: onsuccess: #1829: 2: Success after binutils/gcc: 21 commits new 1109785864d6 395: onsuccess: #1830: 2: Success after binutils/gcc: 7 commits new 730a749920a3 396: onsuccess: #1831: 2: Success after binutils/gcc: 13 commits new b4476f49aa00 397: onsuccess: #1832: 2: Success after binutils: 5 commits new d8ea90baeeca 398: onsuccess: #1833: 2: Success after gcc: 5 commits new 6941ba222e0f 399: onsuccess: #1834: 2: Success after binutils/gcc: 11 commits new 6394c3b9bd4a 400: onsuccess: #1835: 2: Success after binutils/gcc: 6 commits new 5d617028284a 401: onsuccess: #1837: 2: Success after binutils/gcc: 25 commits new 56b68e77a344 402: onsuccess: #1838: 2: Success after binutils/gcc: 8 commits new 9881d879e07f 403: onsuccess: #1839: 2: Success after gcc: 6 commits new 7221a339d3f6 404: onsuccess: #1840: 2: Success after binutils/gcc: 6 commits new e7fa0c5a1cb4 405: onsuccess: #1841: 2: Success after binutils: 6 commits new f5462fd7fc22 406: onsuccess: #1842: 2: Success after binutils/gcc: 13 commits new 4d739749f4b5 407: onsuccess: #1843: 2: Success after binutils/gcc: 3 commits new fefe98d2599b 408: onsuccess: #1844: 2: Success after binutils/gcc: 5 commits new 69d454aba5d0 409: onsuccess: #1845: 2: Success after gcc: 5 commits new a0e998b37b42 410: onsuccess: #1846: 2: Success after binutils/gcc: 2 commits new ffaff375c05f 411: onsuccess: #1847: 2: Success after binutils/gcc: 7 commits new dc6420f3f694 412: onsuccess: #1848: 2: Success after binutils/gcc: 24 commits new f36e538b93b9 413: onsuccess: #1849: 2: Success after binutils/gcc: 12 commits new 62aa791fa72b 414: onsuccess: #1850: 2: Success after binutils/gcc: 4 commits new e0ce36659c13 415: onsuccess: #1851: 2: Success after binutils: 5 commits new e548b9913a8f 416: onsuccess: #1852: 2: Success after binutils/gcc: 52 commits new 412d6078336a 417: onsuccess: #1853: 2: Success after binutils/gcc: 12 commits new 7b56b4320d1e 418: onsuccess: #1854: 2: Success after binutils/gcc: 12 commits new 040d7f82ce88 419: onsuccess: #1855: 2: Success after binutils/gcc: 6 commits new ada9f7725c92 420: onsuccess: #1856: 2: Success after binutils/gcc: 19 commits new 5855e7414cdc 421: onsuccess: #1857: 2: Success after gcc: 10 commits new f2c7b40bb7bd 422: onsuccess: #1858: 2: Success after binutils/gcc: 3 commits new 91e4fe6b1469 423: onsuccess: #1859: 2: Success after basepoints/gcc-13- [...] new 44d53d134ef6 424: onsuccess: #1860: 2: Success after binutils/gcc: 13 commits new 2730f53b7400 425: onsuccess: #1861: 2: Success after binutils/gcc: 9 commits new ad7b999dbf92 426: onsuccess: #1862: 2: Success after binutils/gcc: 11 commits new cfea6f8a4da2 427: onsuccess: #1863: 2: Success after binutils/gcc: 6 commits new c2bacb8e6e6d 428: onsuccess: #1864: 2: Success after binutils/gcc: 14 commits new 6b3026e89a06 429: onsuccess: #1865: 2: Success after binutils/gcc: 9 commits new f352c1bb6fa2 430: onsuccess: #1866: 2: Success after binutils/gcc: 10 commits new 0eacd8d0dbb4 431: onsuccess: #1867: 2: Success after binutils/gcc: 7 commits new 88f86c3b5b8a 432: onsuccess: #1868: 2: Success after binutils: 3 commits new c4d402621d79 433: onsuccess: #1869: 2: Success after basepoints/gcc-13- [...] new 377f86e34006 434: onsuccess: #1870: 2: Success after binutils/gcc: 3 commits new 5dc2458ceca2 435: onsuccess: #1871: 2: Success after binutils/gcc: 3 commits new 2571975a8765 436: onsuccess: #1872: 2: Success after binutils/gcc: 3 commits new 51fc3c1f0c72 437: onsuccess: #1873: 2: Success after basepoints/gcc-13- [...] new 3d765b04a782 438: onsuccess: #1874: 2: Success after binutils/gcc: 2 commits new da9b4a031381 439: onsuccess: #1875: 2: Success after binutils/gcc: 23 commits new 7aa1f443ce72 440: onsuccess: #1877: 2: Success after binutils: 6 commits new b3fe2bed75e1 441: force: #1880: 2: Success after gcc: 15 commits new 4650807c7c2e 442: force: #1881: 1: Failure after basepoints/gcc-13-4795 [...] new 42fcd49ab277 443: onsuccess: #1882: 1: Success after basepoints/gcc-13- [...] new fa692d34b565 444: onsuccess: #1883: 2: Success after binutils/gcc: 16 commits new 7ee9af8c870b 445: onsuccess: #1884: 2: Success after binutils/gcc: 4 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 (dfc13ecc4788) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1832 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 39792 -> 39952 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272724 -> 271496 bytes 06-check_regression/console.log.xz | Bin 3024 -> 2632 bytes 06-check_regression/mail-body.txt | 2 +- 07-update_baseline/console.log | 36 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++--------- 14 files changed, 35 insertions(+), 35 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-arm updated (aeaabda8f8f2 -> 29270ce7a6ae)

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 aeaabda8f8f2 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/q [...] discards 93ace0d3c87d 272: onsuccess: #2001: 7: Success after basepoints/gcc-13- [...] discards edc5528d1795 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: [...] discards 80f4139593a7 270: onsuccess: #1999: 7: Success after binutils/gcc/linux [...] discards 43f1cfdbb0e0 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc [...] discards e84d9f68d469 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards 5efd09135424 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc [...] discards 661f0942c459 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4a [...] discards c0c2258db096 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: [...] discards 6a6e81b7d3c3 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: [...] discards abdd4735dc84 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/q [...] discards fe87bc06ce75 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards a5f15507433a 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: [...] discards 589ca2b34b68 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/q [...] discards 6cb0ddf7249a 259: onsuccess: #1988: 7: Success after binutils/gcc/linux [...] discards 71348220842e 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/q [...] discards 04e3f7cf6dbf 257: onsuccess: #1986: 7: Success after binutils/gcc/linux [...] discards 317ed53fee6c 256: onsuccess: #1985: 7: Success after binutils/gcc/linux [...] discards 97e08c73d41a 255: onsuccess: #1984: 7: Success after binutils/gcc/linux [...] discards d2b20ecbd0d7 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/q [...] discards d34162cb2b61 253: onsuccess: #1982: 7: Success after basepoints/gcc-13- [...] discards 84827d7f311b 252: onsuccess: #1981: 7: Success after binutils/gcc/linux [...] discards a49eb98a18e7 251: onsuccess: #1980: 7: Success after binutils/gcc/linux [...] discards 7008115b311a 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: [...] discards 43b64c03b090 249: onsuccess: #1978: 7: Success after binutils/gcc/linux [...] discards d86d18b261b9 248: onsuccess: #1977: 7: Success after binutils/gcc/linux [...] discards 4fc6f6e096aa 247: onsuccess: #1976: 7: Success after binutils/gcc/linux [...] discards 57df1e963d0f 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: [...] discards e476127d3d8e 245: onsuccess: #1974: 7: Success after binutils/linux/gdb [...] discards b861afc8dab6 244: onsuccess: #1973: 7: Success after binutils/gcc/linux [...] discards 8d9d577d3089 243: onsuccess: #1972: 7: Success after binutils/gcc/linux [...] discards f40e81685e0f 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc [...] discards 402671492abe 241: onsuccess: #1970: 7: Success after binutils/gcc/linux [...] discards 8e5ba49118f9 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits discards ae328c0e5b05 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: [...] discards 6b2b6690e4fd 238: onsuccess: #1967: 7: Success after binutils/gcc/linux [...] discards dbf446364084 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits discards 26576f8e1529 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: [...] discards 4fc08eeb1124 235: onsuccess: #1964: 7: Success after binutils/linux/gli [...] discards 4d3a98bc0b9f 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: [...] discards ace347f694c1 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards 780fa13250d8 232: onsuccess: #1961: 7: Success after binutils/gcc/linux [...] discards 3cbb040fa67d 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc [...] discards 0e924e7da030 230: onsuccess: #1958: 7: Success after binutils/gcc/linux [...] discards c362da552722 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc [...] discards 738021043bc6 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards 3200e2ab9a56 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards 0407c29d14aa 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc [...] discards cd5a741188dd 225: onsuccess: #1953: 7: Success after binutils/gcc/linux [...] discards e7a5c786a14b 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/q [...] discards b09892a98f74 223: onsuccess: #1951: 3: Success after binutils/gcc/linux [...] discards cdb6ea4d7819 222: onsuccess: #1950: 3: Success after basepoints/gcc-13- [...] discards 2ee1a22a4675 221: force: #1949: 3: Failure after basepoints/gcc-13-4492 [...] discards fbe9a6cbd925 220: force: #1948: 5: Success after gcc: 4 commits discards 94ef87ebfb95 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards 5ba7fc1c3518 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards cc6211adc861 217: force: #1942: 5: Failure after gdb-12-branchpoint-294 [...] discards f676f0bc4c05 216: onsuccess: #1940: 7: Success after linux: 12 commits discards 0c66d38bdab9 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards b71ce16e6251 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards bb7f5a954e09 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards e23c4d8baeb3 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards f72f2ecb0818 211: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] discards 17b96a211a71 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: [...] discards 40b2225eec65 209: onsuccess: #1931: 7: Success after binutils/gcc/linux [...] discards 31403e0cb4c4 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards e53370ce7f02 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: [...] discards c5c6c363ff2e 206: onsuccess: #1927: 7: Success after binutils/gcc/linux [...] discards 63a87ed6860e 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: [...] discards 6e8933be1ca8 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: [...] discards 30bf99d6ee68 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: [...] discards f1df530368a2 202: onsuccess: #1923: 7: Success after binutils/gcc/linux [...] discards a6da3d9cecf4 201: onsuccess: #1905: 7: Success after binutils/gcc/linux [...] discards 65595f9b5277 200: onsuccess: #1899: 7: Success after binutils/gcc/linux [...] discards ec79a5ed13cb 199: onsuccess: #1881: 7: Success after binutils/gcc/linux [...] discards 31f5aab1e419 198: onsuccess: #1878: 7: Success after binutils/gcc/linux [...] discards ceb27d0873fd 197: onsuccess: #1856: 4: Success after binutils/gcc/linux [...] discards 48eb34a4fdba 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 8f8e29a378c5 195: force: #1854: 4: Failure after basepoints/gcc-13-3918 [...] discards 7b83aad7a08c 194: force: #1853: 7: Success after gcc: 26 commits discards 5512e3468508 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint [...] discards 8a52513f4826 192: onsuccess: #1848: 7: Success after linux: 213 commits discards abb63b3adb5d 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 65cd0b0b14e6 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 20a864abda62 189: onsuccess: #1829: 7: Success after binutils/gcc/linux [...] discards 0d02c0122d67 188: onsuccess: #1827: 7: Success after binutils/gcc/linux [...] discards c0edba3980ee 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc [...] discards 506a2df07d34 186: onsuccess: #1825: 7: Success after binutils/gcc/linux [...] discards 344938605583 185: onsuccess: #1815: 7: Success after binutils/gcc/linux [...] discards 028932d83837 184: onsuccess: #1777: 7: Success after binutils/gcc/linux [...] discards 2169e26347c4 183: onsuccess: #1776: 7: Success after binutils/gcc/linux [...] discards 1b13acb61ec0 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: [...] discards d85393719193 181: onsuccess: #1773: 7: Success after binutils/gcc/linux [...] discards a3fe91b96853 180: onsuccess: #1724: 7: Success after binutils/gcc/linux [...] discards b21958a1fbf2 179: onsuccess: #1696: 7: Success after binutils/gcc/linux [...] discards cdaed2b1a2df 178: onsuccess: #1694: 7: Success after binutils/gcc/linux [...] discards ac5e03744df3 177: onsuccess: #1692: 7: Success after binutils/gcc/linux [...] discards 7a001bf63038 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc [...] discards 3946a29d3808 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: [...] discards 03c7fa18a20c 174: onsuccess: #1689: 7: Success after binutils/gcc/linux [...] discards b281bb9fedf7 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qe [...] new b80107f2ecb9 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qe [...] new 7a38a02445d7 174: onsuccess: #1689: 7: Success after binutils/gcc/linux [...] new dbc3c7844c4b 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: [...] new 79459ed3e10e 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc [...] new 32a9f1574566 177: onsuccess: #1692: 7: Success after binutils/gcc/linux [...] new 4efa8a699fa5 178: onsuccess: #1694: 7: Success after binutils/gcc/linux [...] new 7dbc9f9eac8f 179: onsuccess: #1696: 7: Success after binutils/gcc/linux [...] new 0974889f1f12 180: onsuccess: #1724: 7: Success after binutils/gcc/linux [...] new 77f16079ad73 181: onsuccess: #1773: 7: Success after binutils/gcc/linux [...] new 9780e9611ff2 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: [...] new 0f2ecf164924 183: onsuccess: #1776: 7: Success after binutils/gcc/linux [...] new 3f2de244fc20 184: onsuccess: #1777: 7: Success after binutils/gcc/linux [...] new 4f1e42349370 185: onsuccess: #1815: 7: Success after binutils/gcc/linux [...] new a0742a65b15f 186: onsuccess: #1825: 7: Success after binutils/gcc/linux [...] new 0c767124d734 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc [...] new 336d6dc8145b 188: onsuccess: #1827: 7: Success after binutils/gcc/linux [...] new 64e90e4d97fa 189: onsuccess: #1829: 7: Success after binutils/gcc/linux [...] new f070a0a8597f 190: onsuccess: #1834: 7: Success after binutils: 25 commits new f1833c5fe34d 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 4c2a5b1c30fa 192: onsuccess: #1848: 7: Success after linux: 213 commits new 76717cd2b41f 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint [...] new c3353637f79c 194: force: #1853: 7: Success after gcc: 26 commits new 992f625bc73d 195: force: #1854: 4: Failure after basepoints/gcc-13-3918 [...] new 69c971157ab7 196: onsuccess: #1855: 4: Success after gcc: 30 commits new fd9f5053056b 197: onsuccess: #1856: 4: Success after binutils/gcc/linux [...] new 1d2295d2b74d 198: onsuccess: #1878: 7: Success after binutils/gcc/linux [...] new 10672bae8587 199: onsuccess: #1881: 7: Success after binutils/gcc/linux [...] new 611fb72199bf 200: onsuccess: #1899: 7: Success after binutils/gcc/linux [...] new d315223b9460 201: onsuccess: #1905: 7: Success after binutils/gcc/linux [...] new 96b954b84e36 202: onsuccess: #1923: 7: Success after binutils/gcc/linux [...] new 1f379cdd1084 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: [...] new 153cb39a1748 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: [...] new 0f32327ed9ef 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: [...] new 89ffffd32ea0 206: onsuccess: #1927: 7: Success after binutils/gcc/linux [...] new 782893097de3 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: [...] new 27a35ceabe68 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new fd6c663925f4 209: onsuccess: #1931: 7: Success after binutils/gcc/linux [...] new 77a76749e7f2 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: [...] new 46299ddc94a0 211: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] new 3567e08148ba 212: onsuccess: #1934: 7: Success after gcc: 3 commits new e6c2f875d351 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 82366ef4e2ba 214: onsuccess: #1937: 7: Success after binutils: 4 commits new 5dc13fe9fad0 215: onsuccess: #1938: 7: Success after gcc: 4 commits new 2a05db48c721 216: onsuccess: #1940: 7: Success after linux: 12 commits new 11ccd272c32e 217: force: #1942: 5: Failure after gdb-12-branchpoint-294 [...] new aba2ead8a386 218: onsuccess: #1943: 5: Success after gdb: 3 commits new bba2a6dc4795 219: onsuccess: #1945: 5: Success after binutils: 8 commits new 64a94aa6f6ea 220: force: #1948: 5: Success after gcc: 4 commits new a6ecc4f9e5a5 221: force: #1949: 3: Failure after basepoints/gcc-13-4492 [...] new 5b38dcc34e30 222: onsuccess: #1950: 3: Success after basepoints/gcc-13- [...] new 229d6a169dec 223: onsuccess: #1951: 3: Success after binutils/gcc/linux [...] new 47eed935c7c4 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/q [...] new 6285335cad41 225: onsuccess: #1953: 7: Success after binutils/gcc/linux [...] new 36b33d58abd1 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc [...] new 141709f766e3 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new c03e4b2624f5 228: onsuccess: #1956: 7: Success after gcc: 5 commits new 4ecd1c99edab 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc [...] new ce049c7c731c 230: onsuccess: #1958: 7: Success after binutils/gcc/linux [...] new 9842ed30de38 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc [...] new 5d7c9fbf925f 232: onsuccess: #1961: 7: Success after binutils/gcc/linux [...] new 29468f58cbc2 233: onsuccess: #1962: 7: Success after gcc: 6 commits new e56119fe831d 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: [...] new 9596b3d0a916 235: onsuccess: #1964: 7: Success after binutils/linux/gli [...] new efc2b8572b12 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: [...] new b52be447bcf5 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits new bac411393a9e 238: onsuccess: #1967: 7: Success after binutils/gcc/linux [...] new 80f7f73e1b44 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: [...] new 4d6c3838552f 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits new a4c41065f13f 241: onsuccess: #1970: 7: Success after binutils/gcc/linux [...] new b13c1f077e94 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc [...] new cb79ab938737 243: onsuccess: #1972: 7: Success after binutils/gcc/linux [...] new 02489cac4ad4 244: onsuccess: #1973: 7: Success after binutils/gcc/linux [...] new 6cbdb4cbad65 245: onsuccess: #1974: 7: Success after binutils/linux/gdb [...] new 62f32a6a69e2 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: [...] new ec8de17253cf 247: onsuccess: #1976: 7: Success after binutils/gcc/linux [...] new 26461ea8654c 248: onsuccess: #1977: 7: Success after binutils/gcc/linux [...] new 88397a3a1d06 249: onsuccess: #1978: 7: Success after binutils/gcc/linux [...] new 661be9eb7e85 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: [...] new 11d240bd630f 251: onsuccess: #1980: 7: Success after binutils/gcc/linux [...] new 64ab0c012807 252: onsuccess: #1981: 7: Success after binutils/gcc/linux [...] new e5e0e10b2664 253: onsuccess: #1982: 7: Success after basepoints/gcc-13- [...] new 8713684fd3a4 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/q [...] new 3167a9f317a9 255: onsuccess: #1984: 7: Success after binutils/gcc/linux [...] new a5d846f703bc 256: onsuccess: #1985: 7: Success after binutils/gcc/linux [...] new 9d21926b6206 257: onsuccess: #1986: 7: Success after binutils/gcc/linux [...] new e435836c4adb 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/q [...] new 94792c36733e 259: onsuccess: #1988: 7: Success after binutils/gcc/linux [...] new 11597624da9c 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/q [...] new 76426ceaf25a 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: [...] new bfa41b93da35 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new b3f03fc1f6c9 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/q [...] new 995edf7e3648 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: [...] new 050b875b1a9b 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: [...] new 49a87edd1a1d 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4a [...] new 8783640d668f 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc [...] new 49197a2dc3c4 268: onsuccess: #1997: 7: Success after glibc: 2 commits new d0f5b9d19f37 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc [...] new 6b0b87300f26 270: onsuccess: #1999: 7: Success after binutils/gcc/linux [...] new 7b5e6cd3c940 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: [...] new b0086468eebb 272: onsuccess: #2001: 7: Success after basepoints/gcc-13- [...] new d7770ab2d3d7 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/q [...] new 29270ce7a6ae 274: onsuccess: #2003: 7: Success after binutils/gcc/linux [...] 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 (aeaabda8f8f2) \ 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 1792 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2788 bytes 04-build_abe-binutils/console.log.xz | Bin 32436 -> 32508 bytes 05-build_abe-stage1/console.log.xz | Bin 92092 -> 93064 bytes 07-build_abe-linux/console.log.xz | Bin 9284 -> 8572 bytes 08-build_abe-glibc/console.log.xz | Bin 236892 -> 238448 bytes 09-build_abe-stage2/console.log.xz | Bin 226508 -> 227680 bytes 10-build_abe-gdb/console.log.xz | Bin 39444 -> 39680 bytes 11-build_abe-qemu/console.log.xz | Bin 30992 -> 31120 bytes 12-check_regression/console.log.xz | Bin 4004 -> 4508 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 ++++++++++++------------ 22 files changed, 67 insertions(+), 67 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_check_gcc/master-arm updated (6af1bfb0601a -> 4c0bf76a4841)

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_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 6af1bfb0601a 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: [...] discards 8aaaadc3da42 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: [...] discards 29aae136b0b4 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] discards fa43fdc7aa5c 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] discards fd322ec46f23 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] discards 804d58991000 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards c165db2acb6a 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards 4a378529691c 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards 9f27b2f68d7b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards d02e8dbaae2d 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 482d61606ace 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards 7353ca11c2fd 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1bc1d5445dcc 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards e3e6d36e2052 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards 008276d03e4f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 5b6d50e7b996 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 5d4fa79cec29 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards dfbaa54db459 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards f04c8d9cb62e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 4a7380338449 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards ece67097840a 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 8ff61fa7db1d 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 62dc3359ecc1 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 5139a9a3eee5 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards cef21c90934d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards a4268ac06760 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards 5d87560ebce9 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 72eb4f9008dd 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 214b7592b5ff 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards a52b4f337a4e 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 44a9fd5d047f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 99663b79112f 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards b4ba1d5a90a5 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 4aaee5387afc 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 5930aa804c66 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 68a31bc50264 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 8946e0c79e67 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 59e28369a227 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 0967f0eca425 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards a7057ec26c89 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards a0d88ed0d6e2 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards ee60809ef3ac 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 8f7334bb3db5 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 52feb55cf7fb 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 2d12518d8c35 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 7c436ddaebc0 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 565f4294b70a 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards eda613274b56 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 1d830ecfc546 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 9b7e659e35ee 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards f73a3e156667 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 8062c6e1b740 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 24f69be1711a 212: onsuccess: #2022: 1: Success after linux: 3 commits discards c457ee6fc2b2 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0560bf6f22e1 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 27d5673e6740 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards e591c42d7066 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 26509e8e2b77 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards b34d69507c9b 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards b3f8d4c7478a 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 2a1cbf2e33ff 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 4442466f38e8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 49000883f62a 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards 26e4a93eab8d 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards ecd22a2825a1 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 59a7511b9949 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 46ff526bf027 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards fcd9f55f1f8f 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards d483182f6636 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 889df6e6fcd0 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards dc2096b3ffd4 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 0a1e6a8a3c76 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards e1d4b9eb2418 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards c8a2710c493c 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 888e4974e41a 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 93bdb0e7dae9 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards 63c0248a969c 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 428000dfa7ad 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards d8367496b445 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 7dc88ad6712a 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 61d081f79de2 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 8dfe9f57694d 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 29c29671a77f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards faa390cdc7c7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards d119030ce51d 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 12f1dca33226 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 6953b0b61fb6 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards b9de9d52b3cf 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 969918467f03 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards e233a3e51234 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards ff372a46c5d4 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards dae122149f70 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards ac3aef2fcb5d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 52d7c0aeeed2 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 6be7602e4bab 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 4c42377d1750 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 7a7bd6431dfb 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards ad868496607b 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards fc24f8267a5a 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards eba85c20b736 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 6cfa18f5f8ef 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 92fb97ac987a 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 221c1816397a 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 755fee5f79f4 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new b7a6539efe6a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new a710336658a2 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new da60c1016d14 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new f957c3c10958 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 00b4ac95c2f7 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 4a5377179a14 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 9ff42175590e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 5edc588661cd 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new cdbc150f8187 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 3ab6c741dcd9 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 453d023edacd 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 0ac672e15ed1 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 83d6f60e78f8 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new 7af1cb888d21 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new a41d4bb36f76 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 6896a34046ef 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 2cbfee77f419 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 8c6d3f0548ea 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 97ac92d53967 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 62382ad03512 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 53ab9bedfc0f 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new 9333a235dd6a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 10b1e896d3f6 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 269f4f79b1aa 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 7024afa181e5 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new ff433e8d1c3f 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 479cfd2c0b2f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 563e56bf4d90 194: onsuccess: #1995: 1: Success after linux: 517 commits new 0037e1e12872 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 68313d43db66 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new be1e7794a8d5 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 53ab24de4443 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new c8c1592d541c 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 72d26660ddfc 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new c34fa302e4d6 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new fe44435a74ab 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new bfed67d6b7b8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new e399e7693cf6 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 01d0432e9cb2 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 55308e1b0886 206: onsuccess: #2007: 1: Success after gcc: 2 commits new f8c9d1936bae 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 67a2ef3894d7 208: onsuccess: #2012: 1: Success after linux: 12 commits new 2f583c48c6a5 209: onsuccess: #2014: 1: Success after binutils: 12 commits new b1d8ea8be3bd 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 07f7d0eb661f 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 7cd49c0b86ce 212: onsuccess: #2022: 1: Success after linux: 3 commits new 4c46db9fad50 213: onsuccess: #2024: 1: Success after binutils: 3 commits new ec8ecc1f2ac0 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new aba4c53a3320 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 2bb5260cfdd3 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new eaf0cd4d88eb 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new a807813bd79c 218: onsuccess: #2030: 1: Success after gcc: 5 commits new d8c875783bee 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 2068fae55d6d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 6b6f4e623ea5 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 4a6ad8741669 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new e66a2afb1826 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 7ae758cff252 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 0e39671f99e5 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 7b110a871065 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new a398c8035581 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 5ffa6dd86b65 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new dec23f50aba5 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 0a4ba0f1daa6 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 6fd993fc65de 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 40c12ab45417 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 590333ebae61 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 569119705fc2 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new bf2544077657 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 9722880bdf98 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 753f1b1d2e29 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new d197da01de9a 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new ce8060c5b3f2 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 3b665ebf3cb6 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new b87d3b80955c 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 82d15db5b859 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 4154110f0ba2 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 23299804e3ca 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 37e22d2b49d6 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 42f3a9ed7784 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new af74004031a8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 45ea130994c5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 5b283db447d5 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new a0af8e8150af 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new bedfbfc95cc0 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 1b42cfeea992 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new ebac41eee04d 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 6aad49ff4a4d 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new c6d030af3ea4 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new b97791554802 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new a6ef1666b25e 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new 1e450c16622e 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new 62ef64021b27 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 42aaef467d1a 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] new e212f2769853 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] new 0ba44380b6fd 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] new 0466d64f1539 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: [...] new 2dafbd656fe6 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: [...] new 4c0bf76a4841 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qe [...] 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 (6af1bfb0601a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 1776 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32332 -> 31920 bytes 04-build_abe-stage1/console.log.xz | Bin 92320 -> 92180 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9256 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 238404 -> 235820 bytes 08-build_abe-stage2/console.log.xz | Bin 226772 -> 225444 bytes 09-build_abe-gdb/console.log.xz | Bin 39484 -> 39248 bytes 10-build_abe-qemu/console.log.xz | Bin 30940 -> 30812 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2668 -> 3352 bytes 13-check_regression/console.log.xz | Bin 5916 -> 6300 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 61 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 2678088 -> 2689020 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 2246924 -> 2232244 bytes sumfiles/gcc.sum | 2793 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 895960 -> 890528 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214012 -> 214068 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 437856 -> 432180 bytes sumfiles/libstdc++.sum | 10 +- 44 files changed, 1674 insertions(+), 1700 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- 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 (115ce3adb6ba -> bc9fff453c2b)

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 115ce3adb6ba 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] new bc9fff453c2b 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] 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 1732 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 52640 -> 53216 bytes 04-build_abe-gcc/console.log.xz | Bin 233684 -> 233940 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9180 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 236296 -> 236112 bytes 08-build_abe-gdb/console.log.xz | Bin 51508 -> 51156 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3876 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2648 -> 2840 bytes 11-check_regression/console.log.xz | Bin 6276 -> 6036 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14452 -> 14484 bytes sumfiles/gdb.sum | 34 ++++++++++++++++---------------- 25 files changed, 49 insertions(+), 49 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 (d8313146ad3e -> 3751a2cbccbf)

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 d8313146ad3e 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: [...] discards 50a543d4a0e7 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: [...] discards 8eaca7740ca6 256: onsuccess: #1953: 7: Success after binutils/gcc/linux [...] discards 7f065e6b8649 255: onsuccess: #1952: 7: Success after binutils/gcc/linux [...] discards f773e77a132c 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc [...] discards 66fc5ddb87dd 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards ecee87d8e565 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc [...] discards c5c55d9db3e0 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4a [...] discards 8757f17f2649 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: [...] discards 05d80eb84c2b 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: [...] discards 7e626546be25 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/q [...] discards 28b1005ee6d7 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards a2e3388b00e0 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards 228480a6a599 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: [...] discards 574f678874b6 244: onsuccess: #1941: 7: Success after binutils/gcc/linux [...] discards 96fa26439582 243: onsuccess: #1940: 7: Success after binutils/gcc/linux [...] discards 3f459b2d082a 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/q [...] discards 904b16559a2e 241: onsuccess: #1938: 7: Success after binutils/gcc/linux [...] discards 38e0252b9f16 240: onsuccess: #1937: 7: Success after binutils/gcc/linux [...] discards 8f174fadb412 239: onsuccess: #1936: 7: Success after binutils/gcc/linux [...] discards 4c8917b2c8e3 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/q [...] discards aefe945e05fc 237: onsuccess: #1934: 7: Success after basepoints/gcc-13- [...] discards eaa774cd2120 236: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] discards 694597259cab 235: onsuccess: #1932: 7: Success after binutils/gcc/linux [...] discards 5c5d22cb0c76 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: [...] discards 39b2ce87d3d8 233: onsuccess: #1930: 7: Success after binutils/gcc/linux [...] discards 532feec48f45 232: onsuccess: #1929: 7: Success after binutils/gcc/linux [...] discards 6bee84f84aed 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards f97c1c6c5070 230: force: #1927: 3: Failure after basepoints/gcc-13-4618 [...] discards b7a0225a516e 229: force: #1926: 7: Success after gcc: 7 commits discards c71ac20b89dc 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint [...] discards 5deb236be3cb 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 3dca9f24535a 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: [...] discards b7c1103b559f 225: onsuccess: #1903: 7: Success after binutils/gcc/linux [...] discards 632bc399761f 224: onsuccess: #1902: 7: Success after binutils/gcc/linux [...] discards b9433b9eea30 223: onsuccess: #1901: 7: Success after basepoints/gcc-13- [...] discards 7ecfa1001659 222: onsuccess: #1900: 7: Success after binutils/gcc/linux [...] discards e6d54803a6a2 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: [...] discards 2268485dd99e 220: onsuccess: #1898: 7: Success after binutils/linux/gli [...] discards b28e6b1c5e64 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: [...] discards 46c30c20d75c 218: onsuccess: #1896: 7: Success after binutils/gcc/linux [...] discards 43ab00de9f2a 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: [...] discards 875fcde81dea 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards 0c689f12c539 215: onsuccess: #1891: 7: Success after binutils/gcc/linux [...] discards c482188d8600 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc [...] discards 7dc65652f251 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards fb26f21ac6ab 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc [...] discards 0567bcb16fad 211: onsuccess: #1887: 7: Success after binutils/gcc/linux [...] discards f723103c5079 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 976a63e56da6 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/q [...] discards f39c4794fbde 208: onsuccess: #1865: 7: Success after linux: 12 commits discards b166b93f32ae 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 143a8368a0d6 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards 7c8268644e86 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards fc0e2f4b4ca9 204: onsuccess: #1858: 7: Success after binutils/gcc/linux [...] discards d0237437de29 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: [...] discards ac237bad57d2 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 20892f60c13b 201: onsuccess: #1855: 7: Success after binutils/gcc/linux [...] discards 1624ad1d3a86 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards b595f2a2a38c 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: [...] discards 23f4db1ff254 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 549ad0a30ce0 197: onsuccess: #1851: 7: Success after binutils/gcc/linux [...] discards 5591dc87a71f 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: [...] discards 562caf9605a7 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: [...] discards 5ca3b86cbcbb 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: [...] discards 18d4b4f57d02 193: onsuccess: #1847: 7: Success after binutils/gcc/linux [...] discards fa90fd5ce090 192: onsuccess: #1816: 7: Success after binutils/gcc/linux [...] discards 4ca9eef51d59 191: onsuccess: #1808: 7: Success after binutils/gcc/linux [...] discards 84ef456eae95 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 5b1798a92a70 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: [...] discards 68215a75b2d2 188: onsuccess: #1765: 7: Success after binutils/gcc/linux [...] discards 5783e2707a93 187: onsuccess: #1763: 7: Success after binutils/gcc/linux [...] discards b3614e77bc1f 186: onsuccess: #1761: 7: Success after binutils/gcc/linux [...] discards 4de279fdc60c 185: onsuccess: #1716: 7: Success after binutils/linux/gdb [...] discards d862faecb84a 184: onsuccess: #1715: 7: Success after binutils/gcc/linux [...] discards 4106455ab810 183: onsuccess: #1712: 7: Success after binutils/gcc/linux [...] discards db3fb63af223 182: onsuccess: #1711: 7: Success after binutils/gcc/linux [...] discards 1f9962ce641b 181: onsuccess: #1700: 7: Success after binutils/gcc/linux [...] discards a2e0328d37f9 180: onsuccess: #1636: 7: Success after binutils/linux/gdb [...] discards a104a0597382 179: onsuccess: #1634: 7: Success after binutils/gcc/linux [...] discards 71120e47a8b1 178: onsuccess: #1631: 7: Success after binutils/gcc/linux [...] discards 0be78e1c3fb4 177: onsuccess: #1630: 7: Success after binutils/gcc/linux [...] discards 8a689879c350 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc [...] discards 760fbcb05849 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc [...] discards 8d2ea8670734 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: [...] discards ef5927ddf0d7 173: onsuccess: #1626: 7: Success after binutils/gcc/linux [...] discards ad83f8e6cd2d 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qe [...] discards c26ab88b3c35 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: [...] discards ffe0b762ab65 170: onsuccess: #1623: 7: Success after binutils/gcc/linux [...] discards 4f38461ce097 169: onsuccess: #1622: 7: Success after binutils/gcc/linux [...] discards bf45d75aabaf 168: onsuccess: #1621: 7: Success after binutils/gcc/linux [...] discards 085416bf5229 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: [...] discards 36205d5da4f1 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 37f2292a1f26 165: onsuccess: #1618: 7: Success after binutils/gcc/linux [...] discards 385e599f1778 164: onsuccess: #1617: 7: Success after binutils/gcc/linux [...] discards 18b451b0d6a8 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: [...] discards fa985d8167c7 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: [...] discards bcd27e8607c1 161: onsuccess: #1614: 7: Success after binutils/gcc/linux [...] discards 69c3ba27689a 160: onsuccess: #1613: 7: Success after binutils/gcc/linux [...] discards 934bb00f1de9 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 6f6494b02a62 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc [...] new b20adbd050f0 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc [...] new 99ae615a51ab 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 26720e63fc79 160: onsuccess: #1613: 7: Success after binutils/gcc/linux [...] new e0b5347d4cac 161: onsuccess: #1614: 7: Success after binutils/gcc/linux [...] new 479209dda98e 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: [...] new 7ddc054c7231 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: [...] new 162971ec5ce0 164: onsuccess: #1617: 7: Success after binutils/gcc/linux [...] new 2a359ba5a97a 165: onsuccess: #1618: 7: Success after binutils/gcc/linux [...] new 05c13317b72d 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new e8c4599e31a9 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: [...] new f5cb83f0b0e2 168: onsuccess: #1621: 7: Success after binutils/gcc/linux [...] new 48b220e0db1f 169: onsuccess: #1622: 7: Success after binutils/gcc/linux [...] new 8dfa00e09f07 170: onsuccess: #1623: 7: Success after binutils/gcc/linux [...] new 7a4d4c8c98da 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: [...] new 3595cdcd7b5b 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qe [...] new 502dca51f6d1 173: onsuccess: #1626: 7: Success after binutils/gcc/linux [...] new c3f3dabb261c 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: [...] new db5ba81a90b6 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc [...] new 9179ece06216 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc [...] new ecfb22ae07ac 177: onsuccess: #1630: 7: Success after binutils/gcc/linux [...] new ff5c5c0ca315 178: onsuccess: #1631: 7: Success after binutils/gcc/linux [...] new a1cb81021303 179: onsuccess: #1634: 7: Success after binutils/gcc/linux [...] new d980b91b9c00 180: onsuccess: #1636: 7: Success after binutils/linux/gdb [...] new c80099b562c6 181: onsuccess: #1700: 7: Success after binutils/gcc/linux [...] new 6f97b9c49b11 182: onsuccess: #1711: 7: Success after binutils/gcc/linux [...] new 2b5610e790c8 183: onsuccess: #1712: 7: Success after binutils/gcc/linux [...] new a37f34d011dc 184: onsuccess: #1715: 7: Success after binutils/gcc/linux [...] new 6accbc0d51b3 185: onsuccess: #1716: 7: Success after binutils/linux/gdb [...] new 7fe03d698f56 186: onsuccess: #1761: 7: Success after binutils/gcc/linux [...] new 6fc603330b12 187: onsuccess: #1763: 7: Success after binutils/gcc/linux [...] new b7aec6904537 188: onsuccess: #1765: 7: Success after binutils/gcc/linux [...] new da3d0f4da968 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: [...] new 6e30dac14ae2 190: onsuccess: #1774: 7: Success after binutils: 10 commits new e118192edf11 191: onsuccess: #1808: 7: Success after binutils/gcc/linux [...] new aa604a662d9b 192: onsuccess: #1816: 7: Success after binutils/gcc/linux [...] new f37bf4c7f027 193: onsuccess: #1847: 7: Success after binutils/gcc/linux [...] new 7e4a13eb71ec 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: [...] new 15b88e269b89 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: [...] new 00f92932bdfa 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: [...] new bb7860f0c840 197: onsuccess: #1851: 7: Success after binutils/gcc/linux [...] new 1dea0cb42e82 198: onsuccess: #1852: 7: Success after gcc: 5 commits new 8ec8d76470b3 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: [...] new 5e09a418dec2 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new c090abbb9c09 201: onsuccess: #1855: 7: Success after binutils/gcc/linux [...] new 84f919d01233 202: onsuccess: #1856: 7: Success after gcc: 2 commits new 2480013e1161 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: [...] new 0f102c89b5f5 204: onsuccess: #1858: 7: Success after binutils/gcc/linux [...] new 259f48acdcfd 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 4f15c70f2a99 206: onsuccess: #1860: 7: Success after gcc: 2 commits new 94e340279173 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 0db58183884c 208: onsuccess: #1865: 7: Success after linux: 12 commits new 1e916a902f36 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/q [...] new 73ff44e7560d 210: onsuccess: #1868: 7: Success after binutils: 7 commits new 836dc223c2c6 211: onsuccess: #1887: 7: Success after binutils/gcc/linux [...] new 189ddc31bb76 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc [...] new bac9180c58ae 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 0b7bdb9c07d4 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc [...] new 3cbbd9e8737c 215: onsuccess: #1891: 7: Success after binutils/gcc/linux [...] new 70b4b8df87d6 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new b4d61cb80ba5 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: [...] new 53c41d2a6cd3 218: onsuccess: #1896: 7: Success after binutils/gcc/linux [...] new 2024f0ea463e 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: [...] new 2de072c17300 220: onsuccess: #1898: 7: Success after binutils/linux/gli [...] new 8b4d434a48a0 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: [...] new a8e7ae9b9046 222: onsuccess: #1900: 7: Success after binutils/gcc/linux [...] new a0dd4d202ea1 223: onsuccess: #1901: 7: Success after basepoints/gcc-13- [...] new 69212fc9f32e 224: onsuccess: #1902: 7: Success after binutils/gcc/linux [...] new 43ec841b5c69 225: onsuccess: #1903: 7: Success after binutils/gcc/linux [...] new c006de4b02ef 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: [...] new 2c9a94d25ea5 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 8144d4723e45 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint [...] new 2e33a1534e10 229: force: #1926: 7: Success after gcc: 7 commits new bba5254a74ba 230: force: #1927: 3: Failure after basepoints/gcc-13-4618 [...] new 4e3c25988552 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 7c125e61ffbf 232: onsuccess: #1929: 7: Success after binutils/gcc/linux [...] new 9eed42ede9a7 233: onsuccess: #1930: 7: Success after binutils/gcc/linux [...] new 590979feb483 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: [...] new 878c2e247d2e 235: onsuccess: #1932: 7: Success after binutils/gcc/linux [...] new 569a67210f95 236: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] new 6e1978bc8843 237: onsuccess: #1934: 7: Success after basepoints/gcc-13- [...] new 9db0d8f63e4f 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/q [...] new 398c75e6a317 239: onsuccess: #1936: 7: Success after binutils/gcc/linux [...] new 60cc07d9abb3 240: onsuccess: #1937: 7: Success after binutils/gcc/linux [...] new 727f097d7e3a 241: onsuccess: #1938: 7: Success after binutils/gcc/linux [...] new 385e2d9c9a50 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/q [...] new d9e02c7ee424 243: onsuccess: #1940: 7: Success after binutils/gcc/linux [...] new ee7b76ce6680 244: onsuccess: #1941: 7: Success after binutils/gcc/linux [...] new 388370b50be7 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: [...] new 81525b921c91 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new fd7c0c442a78 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new efd6bd287f01 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/q [...] new bed240cda923 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: [...] new 1a0bc0cce1af 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: [...] new 213a346f333a 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4a [...] new e7604204c7a4 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc [...] new 7e2e45bc3c01 253: onsuccess: #1950: 7: Success after glibc: 2 commits new 1d2804167e76 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc [...] new c47db140eecf 255: onsuccess: #1952: 7: Success after binutils/gcc/linux [...] new 357424b018f2 256: onsuccess: #1953: 7: Success after binutils/gcc/linux [...] new e11ce6f49203 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: [...] new fe4e9b88ab4e 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: [...] new 3751a2cbccbf 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qe [...] 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 (d8313146ad3e) \ 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 1804 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2796 bytes 04-build_abe-binutils/console.log.xz | Bin 32960 -> 32520 bytes 05-build_abe-stage1/console.log.xz | Bin 74068 -> 74388 bytes 07-build_abe-linux/console.log.xz | Bin 9232 -> 8548 bytes 08-build_abe-glibc/console.log.xz | Bin 247388 -> 245264 bytes 09-build_abe-stage2/console.log.xz | Bin 207808 -> 207536 bytes 10-build_abe-gdb/console.log.xz | Bin 39464 -> 39804 bytes 11-build_abe-qemu/console.log.xz | Bin 32016 -> 31792 bytes 12-check_regression/console.log.xz | Bin 3572 -> 4288 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_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 | 38 ++++++++++----------- 20 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch gdb-13-branch updated (a47dacc45bd -> a444d5309de)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-13-branch in repository binutils-gdb. from a47dacc45bd gdb: fix command lookup in execute_command () new a444d5309de Fix install-strip target The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/Makefile.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch master updated (106791196f9 -> a61ce0ce48c)

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 binutils-gdb. from 106791196f9 bfd: Discard symbol regardless of warning flag new a61ce0ce48c Fix install-strip target The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/Makefile.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (49b6b7ac331 -> a6504f13a05)

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 49b6b7ac331 c++: NTTP object wrapper substitution fixes [PR103346, ...] new a6504f13a05 coroutines: Accept 'extern "C"' coroutines. 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/cp/mangle.cc | 23 +++--- .../g++.dg/coroutines/torture/extern-c-coroutine.C | 89 ++++++++++++++++++++++ 2 files changed, 101 insertions(+), 11 deletions(-) create mode 100644 gcc/testsuite/g++.dg/coroutines/torture/extern-c-coroutine.C -- 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