Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/interesting-commits] branch master updated (360de347 -> 7e45f499)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 360de347 Add entry 5b49da02ddbe1b9082cfc9be1cd848375da178ea from https [...] new 7e45f499 Add entry 6493b7af37e473a89c67afab474330f931dd8447 from https [...] 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/basepoints/gcc-13-5807-g6493b7af37e | 1 + .../gnu-aarch64-master-O2}/build_url | 2 +- .../gnu-aarch64-master-O2/last_good | 1 + .../gnu-aarch64-master-O2/summary.txt | 7 +++++ .../tcwg_bmk-code_speed-spec2k6/status.txt | 36 ++++++++++++++++++++++ 5 files changed, 46 insertions(+), 1 deletion(-) create mode 120000 gcc/basepoints/gcc-13-5807-g6493b7af37e copy {binutils/sha1/4675859351582f017b495ff13fb2ea72a99834af/tcwg_bmk-code_speed-s [...] create mode 100644 gcc/sha1/6493b7af37e473a89c67afab474330f931dd8447/tcwg_bmk-code [...] create mode 100644 gcc/sha1/6493b7af37e473a89c67afab474330f931dd8447/tcwg_bmk-code [...] create mode 100644 gcc/sha1/6493b7af37e473a89c67afab474330f931dd8447/tcwg_bmk-code [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (f6b9eb5e296 -> 3eef3b2c2d8)

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 f6b9eb5e296 Automatic date update in version.in new 3eef3b2c2d8 objcopy memory leaks 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: binutils/objcopy.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-10 updated (80f9bda6cc2 -> 7bbed35a05d)

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 80f9bda6cc2 Daily bump. new ec4d91aa885 rs6000: Teach rs6000_opaque_type_invalid_use_p about inline [...] new 7bbed35a05d rs6000: Teach rs6000_opaque_type_invalid_use_p about gcall [...] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/rs6000/rs6000.c | 64 ++++++++++++++++++---- .../powerpc/{pr106736-3.c => pr108272-1.c} | 9 ++- .../powerpc/{pr106736-2.c => pr108272-2.c} | 8 +-- .../powerpc/{pr106736-3.c => pr108272-3.c} | 9 ++- .../powerpc/{pr106736-2.c => pr108272-4.c} | 9 +-- gcc/testsuite/gcc.target/powerpc/pr108348-1.c | 23 ++++++++ gcc/testsuite/gcc.target/powerpc/pr108348-2.c | 23 ++++++++ 7 files changed, 117 insertions(+), 28 deletions(-) copy gcc/testsuite/gcc.target/powerpc/{pr106736-3.c => pr108272-1.c} (82%) copy gcc/testsuite/gcc.target/powerpc/{pr106736-2.c => pr108272-2.c} (82%) copy gcc/testsuite/gcc.target/powerpc/{pr106736-3.c => pr108272-3.c} (80%) copy gcc/testsuite/gcc.target/powerpc/{pr106736-2.c => pr108272-4.c} (78%) create mode 100644 gcc/testsuite/gcc.target/powerpc/pr108348-1.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr108348-2.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-12 updated (b9f5d34ddc1 -> cb6861acc40)

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 b9f5d34ddc1 Daily bump. new e5a63c98697 rs6000: Teach rs6000_opaque_type_invalid_use_p about inline [...] new 3c7bb6c0b00 rs6000: Teach rs6000_opaque_type_invalid_use_p about gcall [...] new cb6861acc40 rs6000: Fix typo on vec_vsubcuq in rs6000-overload.def [PR108396] The 3 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/rs6000/rs6000-overload.def | 2 +- gcc/config/rs6000/rs6000.cc | 62 ++++++++++++++++++---- .../powerpc/{pr106736-4.c => pr108272-1.c} | 10 ++-- .../powerpc/{pr106736-2.c => pr108272-2.c} | 8 +-- .../powerpc/{pr106736-3.c => pr108272-3.c} | 9 ++-- .../powerpc/{pr106736-2.c => pr108272-4.c} | 9 ++-- gcc/testsuite/gcc.target/powerpc/pr108348-1.c | 23 ++++++++ gcc/testsuite/gcc.target/powerpc/pr108348-2.c | 23 ++++++++ gcc/testsuite/gcc.target/powerpc/pr108396.c | 14 +++++ 9 files changed, 130 insertions(+), 30 deletions(-) copy gcc/testsuite/gcc.target/powerpc/{pr106736-4.c => pr108272-1.c} (82%) copy gcc/testsuite/gcc.target/powerpc/{pr106736-2.c => pr108272-2.c} (82%) copy gcc/testsuite/gcc.target/powerpc/{pr106736-3.c => pr108272-3.c} (80%) copy gcc/testsuite/gcc.target/powerpc/{pr106736-2.c => pr108272-4.c} (78%) create mode 100644 gcc/testsuite/gcc.target/powerpc/pr108348-1.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr108348-2.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr108396.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-11 updated (11e6c122c54 -> 0e41d8a7788)

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 11e6c122c54 Daily bump. new 79a81d526ba rs6000: Teach rs6000_opaque_type_invalid_use_p about inline [...] new 0e41d8a7788 rs6000: Teach rs6000_opaque_type_invalid_use_p about gcall [...] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/rs6000/rs6000.c | 62 ++++++++++++++++++---- .../powerpc/{pr106736-4.c => pr108272-1.c} | 10 ++-- .../powerpc/{pr106736-5.c => pr108272-2.c} | 9 ++-- .../powerpc/{pr106736-3.c => pr108272-3.c} | 9 ++-- .../powerpc/{pr106736-5.c => pr108272-4.c} | 10 ++-- gcc/testsuite/gcc.target/powerpc/pr108348-1.c | 23 ++++++++ gcc/testsuite/gcc.target/powerpc/pr108348-2.c | 23 ++++++++ 7 files changed, 115 insertions(+), 31 deletions(-) copy gcc/testsuite/gcc.target/powerpc/{pr106736-4.c => pr108272-1.c} (82%) copy gcc/testsuite/gcc.target/powerpc/{pr106736-5.c => pr108272-2.c} (82%) copy gcc/testsuite/gcc.target/powerpc/{pr106736-3.c => pr108272-3.c} (80%) copy gcc/testsuite/gcc.target/powerpc/{pr106736-5.c => pr108272-4.c} (78%) create mode 100644 gcc/testsuite/gcc.target/powerpc/pr108348-1.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr108348-2.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (c8b7014788 -> 25623ba255)

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 c8b7014788 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards b417ce8c92 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards 1079d9570c 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] discards 4749132044 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] discards 9eaf2a3c76 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] discards 3b4db2747c 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits discards af00d699d6 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits discards 1587d8b086 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards 79e1f17677 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] discards 700c793cc2 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] discards 389a29043b 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] discards 37a17d1829 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] discards 4d08225c79 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] discards 0e3d1794a6 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] discards 6b5dd2cea3 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits discards a149b08daf 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] discards 631e5ba816 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] discards 368d97d0ca 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] discards 5496cf4184 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] discards 718e118aec 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] discards 677684654d 397: onsuccess: #2132: 7: Success after gcc: 2 commits discards 00c651f411 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards 1f778fbe67 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] discards 75095eeea4 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] discards a203cb8bc5 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits discards 63ad6b54dd 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] discards 59487eaa4c 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] discards 1be5e853af 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards a6d1a2c3ea 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards 474fb342c2 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards 7ceb0599af 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards 81c4f83c64 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards 9ba95a88b7 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards d5034639f8 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards 2479a37dd3 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards c8d6c842bb 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards 55489197e2 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards 91932ee743 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards a5adc77400 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards fd20d9bf3b 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards 8995bf3631 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards 23fdf91017 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards bcabb01dea 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards 390b421b29 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards 578d50dd16 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards 6229034621 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards b4f19b2639 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards 1845354a42 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards d5a3d6b3f3 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 5901fd8620 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards e6404bf2ed 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards bb27f0fa06 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards fc50db7770 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards 27680c355c 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 0372c1a61b 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards c0a779a406 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 8fd1d04da5 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards 15db38eeaf 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 81e9c195c4 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards 40bfab830d 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards be23343b55 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 71117c2c06 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 3b5a44a268 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards 0df8309fdc 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards e482fa2ba0 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 2bb624988c 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards 6c3eb90bc9 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards 0fde49a4d2 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 9940ded2cb 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards a85500e2d1 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 4fc9fea11f 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards 09528fa082 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards 92a82a8355 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards ec8a4152ba 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards 819e2e2e7d 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 1eb6ca2f81 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards 9f742ea370 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards 282e60d1d2 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards fa90aeed01 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards e5673e1a17 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards e6d8a43671 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards b7da69d6d0 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards 9105f15f64 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 30522c6a4c 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards fd5e4b1a15 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards 7391d46049 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 7787e3e0c4 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 336d77a332 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 993b8e95aa 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards c9a2245384 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards a20dcb4e9b 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 3053ec3704 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 71df71c9c1 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards 0f58a056bf 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards a27fcd6ec4 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 6d81c1c67c 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 7c8996ef06 321: force: #2055: 7: Success after gdb: 2 commits discards 2b8f01d212 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards d71c446143 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 5644659f10 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards b166617a4e 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new fd7a4003e7 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 98f46ce162 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new deed0768b9 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 924e6f480c 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 4519fc6a55 321: force: #2055: 7: Success after gdb: 2 commits new a91cf76cd7 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 798a359e3b 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new 56449edca9 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new c0901fa8bf 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new ab69ac22f1 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 2da14f593c 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 24f4cd8b99 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 39cb10dfca 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new ca6ecff860 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new 3e645b738d 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 290f15e268 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new a31f9ecb37 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new 525c69e929 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new d119f4388e 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 8855f173db 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new d4d3593068 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 34f3980087 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new eb16f58e12 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 3c14ae8d63 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 9e9c9483ac 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new ec94e4c837 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new a4d4bacca0 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new 7f6230e473 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 5a7f0df558 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new b251a893a5 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new 01f376b452 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 4a2d04aa87 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new ac8d28010c 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 3dae8da838 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 3aaf37ad8a 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new 9b52436722 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new a1ee132545 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new ff7745b601 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 802087bc5b 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new 452eac9991 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 51c4dbadd2 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new e6c19e7072 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new 8695fd4eda 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new 45d713dd10 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new f95c799ead 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 19db9752eb 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 1b13dfa6e8 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new bf09c470d3 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new 3e4eacd012 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new 841d0ad9d4 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new 06301e95ee 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new f1b7f239b3 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new ccf17fdca7 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 90322cd219 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new 212ad44051 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new fb622fcb9d 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new bb1097e468 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new 708ecd142c 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new 59f6009b31 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new f26f98823b 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new 383c4656b9 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new 5c3d147abb 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new a99e880616 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new c9547bda02 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new bf87adcc00 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new 11cc08b459 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new 71b58a0f2a 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new 479e12c0dd 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new e3a0bbe6c0 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new 45d88e7b0b 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new 884d1f39f1 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new e213bb0eb6 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new a1cf59e83d 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new 16766214d5 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new 7f8faa8a6c 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] new 5a5a20ef2e 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] new cf62941a02 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits new e7490c8d26 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] new dfa79dd24f 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] new d7ba39affd 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new 75d75887d9 397: onsuccess: #2132: 7: Success after gcc: 2 commits new 57675bd412 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] new 134ad31efc 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] new 43e53ad183 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] new 4301dc8d9a 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] new 0065a22757 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] new 3f5278b454 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits new 151025ea6c 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] new 83b39e5a63 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new 6275f83e8d 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] new d36a3fbd67 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] new 57e1e0a86e 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] new b3a3490418 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new 135d31da0a 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new c2dd829fef 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits new a57327f4e8 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits new c37712e026 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] new a46ad0e195 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] new 873a0a1a83 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] new d7ff2f14eb 416: onsuccess: #2152: 7: Success after gcc: 50 commits new 5a2f0ad4c0 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new 25623ba255 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (c8b7014788) \ 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 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 31304 -> 30776 bytes 05-build_abe-stage1/console.log.xz | Bin 91776 -> 91616 bytes 07-build_abe-linux/console.log.xz | Bin 8800 -> 8364 bytes 08-build_abe-glibc/console.log.xz | Bin 236256 -> 236220 bytes 09-build_abe-stage2/console.log.xz | Bin 229140 -> 227676 bytes 10-build_abe-gdb/console.log.xz | Bin 38572 -> 38288 bytes 11-build_abe-qemu/console.log.xz | Bin 31428 -> 31228 bytes 12-check_regression/console.log.xz | Bin 3808 -> 3836 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++---------- 20 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (7f6dfda467 -> c616c7acd5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 7f6dfda467 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards da7d44a7a9 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 833e2610fe 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 799e239af0 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 1318cdb1b1 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards cf34b04b1d 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards fe07993e3c 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards b97839cbce 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 784b5ec6c7 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 717d6741e5 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 9460cc22df 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 30d1672e35 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards fa3e631072 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 9ff59f3b5b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 50850dc485 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 97d9423853 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 68ebad0841 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards e40085b6f1 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 92697f9a50 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 86279ce97b 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 79f667c37a 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 47eced02f8 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards ac700446e8 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 32974fa165 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 741e0ea7e6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 526b75b255 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 9f3070c019 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards f6b8789332 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 02c4b3ce3d 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 592659f400 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards ef12fec9b9 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards e2aca5a54d 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards ffb7c29170 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards c2cc5a9435 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 2465c64cb1 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 66d79788a7 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards a805b898af 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards da112bb2d3 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 79ae7acdb1 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 9f3b64e204 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards a3f66f5371 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 9b8caebe8b 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 98f9a7f061 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 6fa3cc7059 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 06bb41e759 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 6d5121ec5e 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards c2b80aff3b 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards d40cbf7519 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards dc88ee8347 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards de647a87b2 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards c2b1c572b0 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 5a1c51ad72 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 2705e886ed 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 2ba9bc3a70 121: onsuccess: #908: 1: Success after glibc: 2 commits discards de6d372d11 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 52309741fb 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 1a19f322f8 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards ea971ee1e6 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 04ae9dce63 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards a2b0d5383d 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 56fa60d5e7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 1ad09a3d5e 113: onsuccess: #898: 1: Success after linux: 3 commits discards b3fce11d27 112: onsuccess: #896: 1: Success after binutils: 24 commits discards beb8090a82 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 8dbae88c16 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 5cad0646ef 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 09c6a523d2 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards fc00e6f363 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards a601c14845 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards c43e928d83 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 88cca05523 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 10e57ce087 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 972a2cb9a9 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 90c02d8c90 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards be6b425ef5 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 1a27196964 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards c857ac3ae1 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards ee2bec8c73 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards e9bbedb704 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards bf7ac424b8 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 2902931efd 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards e68d522bc6 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 89822c002e 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 3fd65d53a8 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 85f1edb786 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 9f05bb800e 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 94f55f1027 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards a072fa9a5f 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 9df7e3a6ec 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 5110f8e6a1 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards c2858bdde5 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 0fb19e456c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards b802f5b110 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 79467ac07f 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards e61ce8eea5 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 4e3cb02591 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards d65a54d2cb 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 00a7e6f755 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards efbc0eb77f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards c699fdd4eb 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards e35060f426 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 431ec9905d 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 4befbb3651 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new c0d8f21dd5 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 3a9ff89bc0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 453abcf0d8 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 58e2f9c7eb 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 9a65e505db 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 02c465957c 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 16d4e2d3df 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 4b0a6444d5 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 867fe48fcf 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 47d8188bb4 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 508f6be2c3 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new b1dbe6ae42 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 3af257b102 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 9816685380 89: onsuccess: #864: 1: Success after binutils: 25 commits new 77a3b9cb59 90: onsuccess: #867: 1: Success after binutils: 4 commits new 339d065897 91: onsuccess: #870: 1: Success after binutils: 5 commits new 2febb0326f 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 7e8f364048 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 67548b9fcb 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 6c358f37e1 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 06151a8b92 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 1d85552496 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new eb00b326d5 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new f718038988 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 43d34766e4 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new e248fdcf2d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 97bd043562 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 8e2871fa19 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new a7c2bb7568 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 004913ddec 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 904b8ec4f9 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 45ff04684e 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new f9ccb853ff 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 125db31f6f 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 6a5f7704ef 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new a2cd4c8c43 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 58b21ba7e2 112: onsuccess: #896: 1: Success after binutils: 24 commits new 5572fa54ea 113: onsuccess: #898: 1: Success after linux: 3 commits new f8aac07df3 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 5d1ca5fcfe 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 2f75f3086c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new f42e03bb07 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 3bd1345119 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new d26513c1e7 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 03084bb7f9 120: onsuccess: #906: 1: Success after binutils: 29 commits new f9ef43be1a 121: onsuccess: #908: 1: Success after glibc: 2 commits new 73181c4daf 122: onsuccess: #909: 1: Success after linux: 2753 commits new e29108f037 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new f33c637937 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new c26923bf10 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new e6453edb5b 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 4a053735d3 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 1aab89757c 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new c6fd351e6a 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 76be42b991 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new d59cedbc1a 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new fadf789bae 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new aee7cd1551 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 57bc16196d 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 0d8b6b60f9 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 9db898150b 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 47cc81da99 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new ec63a9ef0f 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new a86e2cceac 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 8612def4cc 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 96ec7ab80a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new d5e9157c59 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 4cc67c7e32 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 507432bb88 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new b6c29049ce 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 17ba9c4adf 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 5217c27c5d 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new d55a767b20 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 478e3eb932 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 75ffa7b383 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 5460e9ee33 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 7e3ffa4beb 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 6702b8df52 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new fb4f6e6f9e 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 3ae7340ddb 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 697ec86965 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 6cd73a5b88 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 6616b61e94 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new e1461d7d2a 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 46ac9b35e1 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 46499fd8a9 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 78f55c956a 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 2fa6952b52 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new bfc998de7a 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 3db77f79da 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 5e3411a0eb 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 094b6307aa 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 5fa178e565 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 49ac1adbf9 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new c885d216ba 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 199a2aae1e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new dd7dc3e8bc 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 2f939f10b4 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new fa0205823d 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new c616c7acd5 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] 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 (7f6dfda467) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 38932 -> 38808 bytes 04-build_abe-gcc/console.log.xz | Bin 213920 -> 213432 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8324 bytes 07-build_abe-glibc/console.log.xz | Bin 244924 -> 244280 bytes 08-build_abe-gdb/console.log.xz | Bin 38580 -> 38464 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3904 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2216 -> 2020 bytes 11-check_regression/console.log.xz | Bin 18796 -> 10504 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 43 +- 11-check_regression/mail-body.txt | 148 +- 11-check_regression/results.compare | 79 +- 11-check_regression/results.compare2 | 6410 +++++-------------------------- 11-check_regression/results.regressions | 79 +- 12-update_baseline/console.log | 62 +- 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 | 150 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 79 +- sumfiles/gdb.log.xz | Bin 1988872 -> 1954992 bytes sumfiles/gdb.sum | 5134 +++++++++++-------------- 31 files changed, 3546 insertions(+), 8692 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Oz updated (2407c6a2e1 -> 7d41b5dc30)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Oz in repository toolchain/ci/base-artifacts. from 2407c6a2e1 40: onsuccess: #9: 1: [TCWG CI] 471.omnetpp reduced in size [...] new 7d41b5dc30 41: onsuccess: #10: 1: [TCWG CI] No change after binutils/gc [...] 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 1800 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 32416 -> 31988 bytes 04-build_abe-stage1/console.log.xz | Bin 74528 -> 74224 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7964 -> 7992 bytes 07-build_abe-glibc/console.log.xz | Bin 246780 -> 246488 bytes 08-build_abe-stage2/console.log.xz | Bin 182644 -> 179356 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 63352 -> 63640 bytes 10-benchmark/benchmark-build.log | 92 +- 10-benchmark/benchmark.log | 90 +- 10-benchmark/console.log.xz | Bin 3904 -> 3904 bytes 11-check_regression/console.log.xz | Bin 13636 -> 12068 bytes .../csv-results-vs-first-1/md5sum.csv | 1911 +- .../csv-results-vs-first-1/perf.csv | 2500 +- .../csv-results-vs-first-1/results.csv | 20639 ++- .../csv-results-vs-first-1/size.csv | 152893 ++++++++++-------- 11-check_regression/csv-results-vs-first-1/sve.csv | 12 +- .../csv-results-vs-prev-0/md5sum.csv | 2021 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 2618 +- .../csv-results-vs-prev-0/results.csv | 28321 +--- 11-check_regression/csv-results-vs-prev-0/size.csv | 78858 ++++----- 11-check_regression/csv-results-vs-prev-0/sve.csv | 6 +- .../csv-results-vs-prev-1/md5sum.csv | 1911 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 2500 +- .../csv-results-vs-prev-1/results.csv | 20639 ++- 11-check_regression/csv-results-vs-prev-1/size.csv | 152893 ++++++++++-------- 11-check_regression/csv-results-vs-prev-1/sve.csv | 12 +- 11-check_regression/exe.improvement | 1 - 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 3 - 11-check_regression/mail-body.txt | 3 - 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-vs-first-brief.csv | 46 +- 11-check_regression/results-vs-first-full.csv | 2447 +- 11-check_regression/results-vs-first-internal.csv | 161 +- 11-check_regression/results-vs-first.csv | 161 +- 11-check_regression/results-vs-first.log | 872 +- 11-check_regression/results-vs-prev-brief.csv | 48 +- 11-check_regression/results-vs-prev-compare.csv | 5 +- 11-check_regression/results-vs-prev-full.csv | 2575 +- 11-check_regression/results-vs-prev-internal.csv | 165 +- 11-check_regression/results-vs-prev.csv | 165 +- 11-check_regression/results-vs-prev.log | 1024 +- 12-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../447.dealII/results-metadata.json | 16 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 16 +- .../453.povray/results-metadata.json | 16 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 16 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../482.sphinx3/results-metadata.json | 16 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 88 +- dashboard/squad-vs-first/summary-annotation.txt | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 59 +- mail/mail-body.txt | 59 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- 86 files changed, 253166 insertions(+), 223033 deletions(-) delete mode 100644 11-check_regression/exe.improvement -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (096704821f -> 58cd3fdb6d)

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 096704821f 403: onsuccess: #2106: 7: Success after glibc: 12 commits discards a92d0c9973 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] discards 30c86b875a 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] discards e18cd19c51 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 43fe246e12 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits discards ec38ffadd1 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits discards a1732b5be5 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits discards 4f72e04964 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards 59a793432e 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards 3f6bd01492 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards 73c1607e3a 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards 477013f0bd 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards 3572ca871b 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 178150d4fb 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards da95cb771e 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards 629872359c 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards d2c5d301eb 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards ecfda82d47 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards b14e75cebc 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards 711a7f649d 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards 6844469d8d 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards b604a45d18 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 6bc5e53ad1 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 5ce90cc403 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards ac2db09247 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards bccf8cf016 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards a7ad51f464 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards 9dd5947d49 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 7d8f824a41 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 8dc54c71ce 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 8655a4dc40 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards 9f70248551 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 7b783d1e6b 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards 6c71251d0f 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards 6c0879e8f4 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards f2e0d5de00 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 7aef680897 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards f44ac1a5d0 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards 5759a91863 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards 26bdd05677 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards cfa652933d 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards 540c7fa86b 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards bae63d061e 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 69b6398e88 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 2484857db4 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards 48a09b2896 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 778ca1333d 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 02a9e886b3 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards f5776849f9 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 0520c5a826 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 46fd331762 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards 57a98e3c62 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards 486d1c1a66 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards b0a978ab36 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 9d4c8ef667 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 4d0bad871f 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 05cc96683a 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 119bcb89ca 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards a5b0514c83 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 5129850192 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 50d57d9c85 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 02df1ff409 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards 23d0d625ed 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards 2bda1fcbe4 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards cb53aeaab3 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards 1413395212 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards a945c49535 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 3d01be8a4d 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards a4478ce68c 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards a19d15e2cc 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards bb28656dbd 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards b513b8b706 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards 7856db9f56 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards d42ebc54c9 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 51eb13a874 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards 25e2d309b2 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards da89f13f44 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards 48326b914c 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 9ce5f6d1c2 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 4bdad2cf2e 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards b872993dff 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 718288d51a 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards ec7e20d972 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards d34d1d35f1 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 2576597b4d 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 4511f9c8e2 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards c31162abe8 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards f93d30bcdc 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards ffb7d51f68 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards a8d40f31c9 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards d25c30bdf8 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 7f71b17d0b 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 39f45ddda0 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 11a6542d01 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards f8a530b117 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 20be0f316f 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards e2dd27aac9 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 9fed74fb20 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards ae802c4b45 305: force: #2006: 7: Success after gdb: 2 commits discards 242b770a26 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 457045811d 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 726080baf5 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 49e7b86450 304: onsuccess: #2002: 7: Success after gcc: 4 commits new c6ccd20790 305: force: #2006: 7: Success after gdb: 2 commits new 3ff6a60e64 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new a711a55666 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new 979762d8f2 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 85ad37a6b8 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new ab1a5c4c9e 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 8e49ae6605 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new c2ceddac0c 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new f1dfb3b60d 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new ed84da538f 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 32447aa583 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new d037629f83 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new f8d66d2589 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 3b26b4a4d0 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 4a5562505a 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 943b17cac5 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new c85c57621c 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new c617e4eb98 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new f86ad91cbc 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 1daa6a2a81 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 8b9d3e4414 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new bef1fcaf32 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 1ce882c4ae 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 548547cafd 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 36acfff711 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new fb13894735 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 52b659306a 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new a035186958 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new c6b95a5443 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new db2abdc044 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new 1b0de63004 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 1dbbb46b1e 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 9c5c27e1ee 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new f5c963268b 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new 03ffde0dba 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new bd3e069261 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new b997740a33 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new 66a3153097 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new c5a32f4d66 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new fb7ae6acf5 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new e7c2605926 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 99b4bd6995 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 05a53959be 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 6f3a81c993 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new e3bcfc1051 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 3cf19560ca 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new 50e9c95919 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 79a524e2d4 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new 75a1675218 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new f63266ced0 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new 46077adcdc 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new b57e263838 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new 63584fe943 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 843a54a83e 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new f668badbd7 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new dab7a684a7 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new d91cf55bee 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new b70dd52a9d 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 8c5627fbc0 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new 89eea3e9a9 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new a2f888b3bf 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new d016fff1a7 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new 0952075609 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 0c1c50c3ee 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 513345e5cf 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 3e1164d2ec 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new 4e38d78769 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new a5cfe5dc80 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 1202fe9060 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 31a2806d21 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new f1b8b32186 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new 2278838b50 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 29e31aceb9 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new dcd342c663 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new b9f6d4f973 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new 0bf8b8b621 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new 751169dd41 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new 3288f29700 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 1ae60ce636 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new c0911f4641 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new cc471599a9 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new 3e24ccff68 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 7c29d9c50f 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 0ab19af2d7 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 77c982b313 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new 0e123c75da 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new d58a1a9351 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new d22f637eca 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new f69cf620eb 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new 61d1f8348b 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new f29ce9ceb6 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new 1f3410b5f7 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new 0584f15f8f 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits new d3a21c5c3b 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits new 15e8dec583 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits new 38d34f2356 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 5b3eda590e 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] new a71aac199d 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] new 9f0ddaa73a 403: onsuccess: #2106: 7: Success after glibc: 12 commits new 58cd3fdb6d 404: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (096704821f) \ 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 1768 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 31592 -> 30996 bytes 05-build_abe-stage1/console.log.xz | Bin 73416 -> 72712 bytes 07-build_abe-linux/console.log.xz | Bin 8668 -> 8356 bytes 08-build_abe-glibc/console.log.xz | Bin 245144 -> 245028 bytes 09-build_abe-stage2/console.log.xz | Bin 204856 -> 204592 bytes 10-build_abe-gdb/console.log.xz | Bin 38756 -> 38356 bytes 11-build_abe-qemu/console.log.xz | Bin 32192 -> 31556 bytes 12-check_regression/console.log.xz | Bin 3456 -> 3796 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++---------- 20 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO updated (aa6fb3d288 -> 31744b6b2d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts. from aa6fb3d288 76: onsuccess: #30: 1: [TCWG CI] No change after binutils/gc [...] new 31744b6b2d 77: onsuccess: #31: 1: [TCWG CI] No change after binutils/gc [...] 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 1864 -> 1864 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31812 -> 32056 bytes 04-build_abe-stage1/console.log.xz | Bin 74292 -> 75060 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8672 -> 7924 bytes 07-build_abe-glibc/console.log.xz | Bin 246904 -> 246896 bytes 08-build_abe-stage2/console.log.xz | Bin 184628 -> 182360 bytes 09-benchmark/benchmark-build.log | 108 +- 09-benchmark/benchmark.log | 106 +- 09-benchmark/console.log.xz | Bin 3880 -> 3900 bytes 10-check_regression/console.log.xz | Bin 7648 -> 7424 bytes .../csv-results-vs-first-0/results.csv | 353882 ++++++------ .../csv-results-vs-first-0/size.csv | 521708 +++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 42 +- .../csv-results-vs-first-1/perf.csv | 175 +- .../csv-results-vs-first-1/results.csv | 39252 +- .../csv-results-vs-first-1/size.csv | 500539 ++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 40 +- .../csv-results-vs-first-1/vect.csv | 42 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 167 +- .../csv-results-vs-prev-0/results.csv | 26320 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 493956 +++++++++-------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 36 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 38 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 175 +- .../csv-results-vs-prev-1/results.csv | 39252 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 500539 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 40 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 42 +- 10-check_regression/mail-body.txt | 5 - 10-check_regression/results-vs-first-brief.csv | 66 +- 10-check_regression/results-vs-first-full.csv | 187 +- 10-check_regression/results-vs-first-internal.csv | 80 +- 10-check_regression/results-vs-first.csv | 80 +- 10-check_regression/results-vs-first.log | 1364 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-full.csv | 191 +- 10-check_regression/results-vs-prev-internal.csv | 82 +- 10-check_regression/results-vs-prev.csv | 82 +- 10-check_regression/results-vs-prev.log | 1570 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 14 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 14 +- .../squad-vs-first/403.gcc/results-metadata.json | 14 +- .../410.bwaves/results-metadata.json | 14 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 14 +- .../435.gromacs/results-metadata.json | 14 +- .../436.cactusADM/results-metadata.json | 14 +- .../437.leslie3d/results-metadata.json | 14 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../447.dealII/results-metadata.json | 14 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 14 +- .../453.povray/results-metadata.json | 14 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../459.GemsFDTD/results-metadata.json | 14 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 14 +- .../464.h264ref/results-metadata.json | 14 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 14 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../471.omnetpp/results-metadata.json | 14 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metadata.json | 14 +- .../482.sphinx3/results-metadata.json | 14 +- .../483.xalancbmk/results-metadata.json | 14 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 44 +- mail/mail-body.txt | 49 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1281720 -> 0 bytes save-temps/401.bzip2.tar.xz | Bin 94476 -> 0 bytes save-temps/403.gcc.tar.xz | Bin 3567072 -> 0 bytes save-temps/410.bwaves.tar.xz | Bin 15100 -> 0 bytes save-temps/416.gamess.tar.xz | Bin 4210492 -> 0 bytes save-temps/429.mcf.tar.xz | Bin 36580 -> 0 bytes save-temps/433.milc.tar.xz | Bin 167760 -> 0 bytes save-temps/434.zeusmp.tar.xz | Bin 126512 -> 0 bytes save-temps/435.gromacs.tar.xz | Bin 979240 -> 0 bytes save-temps/436.cactusADM.tar.xz | Bin 725464 -> 0 bytes save-temps/437.leslie3d.tar.xz | Bin 46336 -> 0 bytes save-temps/444.namd.tar.xz | Bin 168352 -> 0 bytes save-temps/445.gobmk.tar.xz | Bin 1833032 -> 0 bytes save-temps/447.dealII.tar.xz | Bin 6165516 -> 0 bytes save-temps/450.soplex.tar.xz | Bin 709924 -> 0 bytes save-temps/453.povray.tar.xz | Bin 1335448 -> 0 bytes save-temps/454.calculix.tar.xz | Bin 1232436 -> 0 bytes save-temps/456.hmmer.tar.xz | Bin 379444 -> 0 bytes save-temps/458.sjeng.tar.xz | Bin 148100 -> 0 bytes save-temps/459.GemsFDTD.tar.xz | Bin 145032 -> 0 bytes save-temps/462.libquantum.tar.xz | Bin 61684 -> 0 bytes save-temps/464.h264ref.tar.xz | Bin 563352 -> 0 bytes save-temps/465.tonto.tar.xz | Bin 2068872 -> 0 bytes save-temps/470.lbm.tar.xz | Bin 26328 -> 0 bytes save-temps/471.omnetpp.tar.xz | Bin 1066824 -> 0 bytes save-temps/473.astar.tar.xz | Bin 88336 -> 0 bytes save-temps/481.wrf.tar.xz | Bin 1583616 -> 0 bytes save-temps/482.sphinx3.tar.xz | Bin 254240 -> 0 bytes save-temps/483.xalancbmk.tar.xz | Bin 11851876 -> 0 bytes 122 files changed, 1251633 insertions(+), 1229302 deletions(-) delete mode 100644 save-temps/400.perlbench.tar.xz delete mode 100644 save-temps/401.bzip2.tar.xz delete mode 100644 save-temps/403.gcc.tar.xz delete mode 100644 save-temps/410.bwaves.tar.xz delete mode 100644 save-temps/416.gamess.tar.xz delete mode 100644 save-temps/429.mcf.tar.xz delete mode 100644 save-temps/433.milc.tar.xz delete mode 100644 save-temps/434.zeusmp.tar.xz delete mode 100644 save-temps/435.gromacs.tar.xz delete mode 100644 save-temps/436.cactusADM.tar.xz delete mode 100644 save-temps/437.leslie3d.tar.xz delete mode 100644 save-temps/444.namd.tar.xz delete mode 100644 save-temps/445.gobmk.tar.xz delete mode 100644 save-temps/447.dealII.tar.xz delete mode 100644 save-temps/450.soplex.tar.xz delete mode 100644 save-temps/453.povray.tar.xz delete mode 100644 save-temps/454.calculix.tar.xz delete mode 100644 save-temps/456.hmmer.tar.xz delete mode 100644 save-temps/458.sjeng.tar.xz delete mode 100644 save-temps/459.GemsFDTD.tar.xz delete mode 100644 save-temps/462.libquantum.tar.xz delete mode 100644 save-temps/464.h264ref.tar.xz delete mode 100644 save-temps/465.tonto.tar.xz delete mode 100644 save-temps/470.lbm.tar.xz delete mode 100644 save-temps/471.omnetpp.tar.xz delete mode 100644 save-temps/473.astar.tar.xz delete mode 100644 save-temps/481.wrf.tar.xz delete mode 100644 save-temps/482.sphinx3.tar.xz delete mode 100644 save-temps/483.xalancbmk.tar.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page: