Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/interesting-commits] branch master updated (3bf45c7e -> 1fd1d208)

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 3bf45c7e Add entry de122cb920080fd9e24b2777114271fbef932d5e from https [...] new 1fd1d208 Add entry c476a78f19ef12f10230e6162c290c17e9c74933 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: .../tcwg_kernel/llvm-master-arm-next-allyesconfig/build_url | 2 +- .../c476a78f19ef12f10230e6162c290c17e9c74933/tcwg_kernel/status.txt | 2 +- 2 files changed, 2 insertions(+), 2 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_kernel/gnu-master-arm-stable-allnoconfig updated (57a27794c1 -> 4ed52e65eb)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 57a27794c1 41: onsuccess: #399: all: Success after binutils/gcc/linux/q [...] new 4ed52e65eb 42: onsuccess: #400: all: Success after binutils/gcc/qemu: 3 [...] 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 36256 -> 31564 bytes 04-build_abe-stage1/console.log.xz | Bin 93852 -> 93076 bytes 05-build_abe-qemu/console.log.xz | Bin 32108 -> 31848 bytes 06-build_linux/console.log.xz | Bin 4360 -> 4412 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4428 -> 3960 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 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_cross_build/master-arm updated (c6fd473e61 -> 1b49e7a9d8)

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 c6fd473e61 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] discards 9c183177f4 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] discards c02f455224 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards 414b6ccfdd 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards 9eba9e7a09 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards 8043c3b1cf 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards 78d248b209 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards 4c637e4756 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards 07fda628b2 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards f409fa63cc 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards 97aff66abc 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards e6eb28b122 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards 84743a6987 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards f5c9630a54 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards e3fdf48dc6 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards 730e8d0839 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards 656b66a60b 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 954fa0da37 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards 96631d385b 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards de97ab7f2d 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards fa5097f0d7 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards aeaf1aeaf7 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards 3c11cf8248 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards 84426c17f5 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 7d3552c012 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards 7441111e43 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards 83ad23e92d 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards 68e540cbf8 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards 3852892228 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 2cf7fbfca7 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards b274f74728 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 167b400ce9 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards c740abae5c 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards b44d54ffb3 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards 32350b6477 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards b3b21c05de 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards ba030f55e9 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 4cff682a32 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards a7fc2e57c3 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards 080ea7a4b2 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 1d69c0ae8a 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards 36f64f99e3 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards 033eccc0a5 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 7d45bb6e27 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 58f63bad61 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards ec627aefde 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards d791927b0a 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards 1ee4e7d7f0 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards 04aaa7a38a 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards 44726018f5 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 4ce68a9456 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards 611e3bfc59 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards dab745f4d5 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards 166eded2af 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards b44a30333c 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards 92a08b052f 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards 82aff7e27b 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards e117f29c0d 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 1ad7b90afc 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards 379b9b84fe 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards b5fef278f3 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 2a50784cf5 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 0edd81f94d 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 1ed21aea15 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 63f7c510ab 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 6ab0691189 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 5c6fb2f9b1 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 9f73cd6541 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards 2cdafa298a 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 7bf4bef9c2 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 8568d546d4 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards e91b6a8bb3 321: force: #2055: 7: Success after gdb: 2 commits discards fc77800179 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 1a33fd619e 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 4a7b7aeaa1 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards f0a38ca1d5 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards 18873b9234 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 561512a6b6 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 131f488650 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards f2939a58a5 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards 781faae889 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards 6cd368b3f4 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards 4c490f300f 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 2970f9755d 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 695ed7ff38 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 84cfb3d77f 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 52034c6f24 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards 5f85065e89 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards 0a08109beb 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards dc27e93927 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 1029861727 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards 2b814b4e09 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 5abbcea472 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards 66976b5833 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards 2fae492698 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards f04a1e97c7 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards 93794be332 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards 8c17fd3cd1 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards 94dd9e7339 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards 7aea4ebdbb 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards 3d9b9e5886 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new 18fc16af01 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new 155b70a55b 293: onsuccess: #2022: 7: Success after gcc: 2 commits new d46ad5b716 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 94cb6900dd 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new 35557796cd 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new 5c3ac4cad7 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 6a0648cb38 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new 36d036faf0 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new 130ffcf51d 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new 0c70669389 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 031bacb23b 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new 7c5ab1cced 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new fc21d39f95 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new 32d96f77d1 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new ee261d0db9 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new d0ac178b97 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new ff3e883985 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new ba1c658810 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new f92a2a01d6 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 58b5a9e866 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 0c3bfef385 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new 38f983a4eb 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new 538802d608 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 4894b0c99b 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 452ff40327 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new b6b42f45d5 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 802b35a976 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new 94ce536ef1 319: onsuccess: #2049: 7: Success after binutils: 4 commits new de869401c5 320: onsuccess: #2050: 7: Success after gcc: 4 commits new ead44d7b0d 321: force: #2055: 7: Success after gdb: 2 commits new 0d1f476e2f 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 2fdacc956a 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new 646beef2a1 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 366deb4357 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new b84539132f 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 3c5871d030 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new ce7d722c7d 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 74ea477780 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 99de259fc9 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new bd23a98389 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new e10067ceaf 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new 6f05caac39 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new e99b1c6e51 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new 12b422a460 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 5dc6b455ac 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new d66ab4dea9 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 679c3c70df 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new c46dc340a7 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 27ed159d8f 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 596bb3034c 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new d783262c1d 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new f2405a5eda 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new 8964a2cb16 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 0197c4e080 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new c9affb68e1 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new c143596868 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new f216b10de6 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new be0100aee8 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 23c612afa1 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 187412c9f7 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new 5845d0daa2 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new 3797754a77 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new e61383cd7d 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new b0f1b63bb1 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new 6e32d3e9d4 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new aea095b8b8 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new e96076ce79 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new 60686104e8 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new ac73a6e44c 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 0663fe4437 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 38ae69f3dc 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 4d8c456099 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new afa522a940 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new 6b92a5091d 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new 87f8d60a1a 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new c45253e376 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new c6273fef06 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new 4433e90a80 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 9c596baf32 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new 36a875d6fa 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new b5ee886302 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new b9d7ea1390 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new 7145311f4c 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new e1b1cc5020 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new 74d562dfe0 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new d09084092e 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new 75d77778ab 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new f84bf5c131 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new 90b5531137 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new 62837dcc1f 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new e849f798f6 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new aa7dee7b82 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new 619537ec3e 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new b8d2cdbb43 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new a25428d36e 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new 2c14caedbb 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new 30867d59d9 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new 3bf7862f13 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new 2004d87043 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new ceddc7910d 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] new 4c4c3766bc 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] new 1b49e7a9d8 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 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 (c6fd473e61) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 31216 -> 31156 bytes 05-build_abe-stage1/console.log.xz | Bin 91968 -> 92248 bytes 07-build_abe-linux/console.log.xz | Bin 9104 -> 9116 bytes 08-build_abe-glibc/console.log.xz | Bin 238376 -> 236844 bytes 09-build_abe-stage2/console.log.xz | Bin 229876 -> 229880 bytes 10-build_abe-gdb/console.log.xz | Bin 38688 -> 38688 bytes 11-build_abe-qemu/console.log.xz | Bin 31936 -> 31896 bytes 12-check_regression/console.log.xz | Bin 3200 -> 3516 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++-------- 18 files changed, 56 insertions(+), 56 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_kernel/llvm-master-arm-next-allyesconfig updated (53a823ce64 -> 2492306c08)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig in repository toolchain/ci/base-artifacts. from 53a823ce64 67: force: #560: all: Success after linux: 47576 commits new 2492306c08 68: force: #564: 21030: Failure after linux: 14595 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1840 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32320 -> 31696 bytes 04-build_kernel_llvm/console.log.xz | Bin 65476 -> 65216 bytes 05-build_abe-qemu/console.log.xz | Bin 31748 -> 31560 bytes 06-build_linux/console.log.xz | Bin 3496 -> 3780 bytes 07-boot_linux/console.log.xz | Bin 496 -> 0 bytes 08-check_regression/console.log.xz | Bin 2980 -> 3416 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 32 ++++++++++++++++---------------- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 11 +++++++++++ 08-check_regression/trigger-bisect | 2 ++ dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 32 ++++++++++++++++---------------- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- results | 15 ++++++++++++--- 20 files changed, 73 insertions(+), 51 deletions(-) delete mode 100644 07-boot_linux/console.log.xz create mode 100644 08-check_regression/results.regressions create mode 100644 08-check_regression/trigger-bisect -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[linux] branch master updated (870c3a9a2bc4 -> c608f6b58f30)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from 870c3a9a2bc4 Merge tag 'fbdev-for-6.2-rc7' of git://git.kernel.org/pub/ [...] new b0576ade3aaf nvmem: brcm_nvram: Add check for kzalloc new c151d5ed8e8f nvmem: sunxi_sid: Always use 32-bit MMIO reads new 3bd747c7ea13 nvmem: core: initialise nvmem->id early new 569653f022a2 nvmem: core: remove nvmem_config wp_gpio new 560181d3ace6 nvmem: core: fix cleanup after dev_set_name() new ab3428cfd9aa nvmem: core: fix registration vs use race new edcf2fb66052 nvmem: core: fix device node refcounting new db3546d58b5a nvmem: core: fix cell removal on error new 0c4862b1c146 nvmem: core: fix return value new 1ca7fca34931 nvmem: qcom-spmi-sdam: fix module autoloading new 65ea840afd50 fpga: stratix10-soc: Fix return value check in s10_ops_wri [...] new 60ce26d10e58 fpga: m10bmc-sec: Fix probe rollback new bf29ce87ba13 Merge tag 'fpga-for-6.2-final' of git://git.kernel.org/pub [...] new cc3304052a89 iio: adc: stm32-dfsdm: fill module aliases new cbd3a0153cd1 iio: adc: berlin2-adc: Add missing of_node_put() in error path new 6794ed0cfcc6 iio: adc: xilinx-ams: fix devm_krealloc() return value check new 0fc3562a993c iio: imx8qxp-adc: fix irq flood when call imx8qxp_adc_read_raw() new f804bd0dc286 iio:adc:twl6030: Enable measurements of VUSB, VBAT and others new 429e1e8ec696 iio: imu: fxos8700: fix map label of channel type to MAGN sensor new c68b44bc7d9b iio: imu: fxos8700: fix swapped ACCEL and MAGN channels readback new 37a94d86d705 iio: imu: fxos8700: fix incomplete ACCEL and MAGN channels [...] new a53f945879c0 iio: imu: fxos8700: fix IMU data bits returned to user space new 9d61c1820598 iio: imu: fxos8700: fix ACCEL measurement range selection new bffb7d9d1a3d iio:adc:twl6030: Enable measurement of VAC new c9c1d6d82091 iio: imu: st_lsm6dsx: fix build when CONFIG_IIO_TRIGGERED_ [...] new f7b23d1c35d8 iio: hid: fix the retval in accel_3d_capture_sample new eb50cd5bfdac iio: hid: fix the retval in gyro_3d_capture_sample new ee3c5b644a0f iio: light: cm32181: Fix PM support on system with 2 I2C r [...] new 78ad6864e9e0 iio: imu: fxos8700: fix incorrect ODR mode readback new eb6d8f8705bc iio: imu: fxos8700: fix failed initialization ODR mode assignment new ff5e2cd92ffd iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN new 2acd031347f6 iio: imu: fxos8700: fix MAGN sensor scale and unit new 9944028659e6 Merge tag 'iio-fixes-for-6.2a' of https://git.kernel.org/p [...] new 6dfb0771429a HV: hv_balloon: fix memory leak with using debugfs_lookup() new d83d7ed26028 kernel/irq/irqdomain.c: fix memory leak with using debugfs [...] new d3feaff4d949 Merge tag 'char-misc-6.2-rc7' of git://git.kernel.org/pub/ [...] new 3f6c02fa712b serial: stm32: Merge hard IRQ and threaded IRQ handling in [...] new 31352811e13d serial: 8250_dma: Fix DMA Rx completion race new 57e9af7831dc serial: 8250_dma: Fix DMA Rx rearm race new 226fae124b2d vc_screen: move load of struct vc_data pointer in vcs_read [...] new dc0ce181af6d Merge tag 'tty-6.2-rc7' of git://git.kernel.org/pub/scm/li [...] new fa003a3c11ef MAINTAINERS: Add myself as UVC Gadget Maintainer new eb320f76e31d usb: dwc3: qcom: enable vbus override when in OTG dr-mode new 921deb9da158 usb: gadget: f_fs: Fix unbalanced spinlock in __ffs_ep0_qu [...] new 2fa89458af99 usb: gadget: f_uac2: Fix incorrect increment of bNumEndpoints new 30d09b3131f5 usb: gadget: udc: do not clear gadget driver.bus new f82060da749c usb: typec: ucsi: Don't attempt to resume the ports before [...] new c608f6b58f30 Merge tag 'usb-6.2-rc7' of git://git.kernel.org/pub/scm/li [...] The 48 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: MAINTAINERS | 1 + drivers/fpga/intel-m10-bmc-sec-update.c | 17 +++-- drivers/fpga/stratix10-soc.c | 4 +- drivers/hv/hv_balloon.c | 2 +- drivers/iio/accel/hid-sensor-accel-3d.c | 1 + drivers/iio/adc/berlin2-adc.c | 4 +- drivers/iio/adc/imx8qxp-adc.c | 11 +++- drivers/iio/adc/stm32-dfsdm-adc.c | 1 + drivers/iio/adc/twl6030-gpadc.c | 32 +++++++++ drivers/iio/adc/xilinx-ams.c | 2 +- drivers/iio/gyro/hid-sensor-gyro-3d.c | 1 + drivers/iio/imu/fxos8700_core.c | 111 +++++++++++++++++++++++++------- drivers/iio/imu/st_lsm6dsx/Kconfig | 1 + drivers/iio/light/cm32181.c | 9 +-- drivers/nvmem/brcm_nvram.c | 3 + drivers/nvmem/core.c | 60 ++++++++--------- drivers/nvmem/qcom-spmi-sdam.c | 1 + drivers/nvmem/sunxi_sid.c | 15 ++++- drivers/tty/serial/8250/8250_dma.c | 21 ++++-- drivers/tty/serial/stm32-usart.c | 33 ++-------- drivers/tty/vt/vc_screen.c | 9 +-- drivers/usb/dwc3/dwc3-qcom.c | 2 +- drivers/usb/fotg210/fotg210-udc.c | 1 - drivers/usb/gadget/function/f_fs.c | 4 +- drivers/usb/gadget/function/f_uac2.c | 1 + drivers/usb/gadget/udc/bcm63xx_udc.c | 1 - drivers/usb/gadget/udc/fsl_qe_udc.c | 1 - drivers/usb/gadget/udc/fsl_udc_core.c | 1 - drivers/usb/gadget/udc/fusb300_udc.c | 1 - drivers/usb/gadget/udc/goku_udc.c | 1 - drivers/usb/gadget/udc/gr_udc.c | 1 - drivers/usb/gadget/udc/m66592-udc.c | 1 - drivers/usb/gadget/udc/max3420_udc.c | 1 - drivers/usb/gadget/udc/mv_u3d_core.c | 1 - drivers/usb/gadget/udc/mv_udc_core.c | 1 - drivers/usb/gadget/udc/net2272.c | 1 - drivers/usb/gadget/udc/net2280.c | 1 - drivers/usb/gadget/udc/omap_udc.c | 1 - drivers/usb/gadget/udc/pch_udc.c | 1 - drivers/usb/gadget/udc/snps_udc_core.c | 1 - drivers/usb/typec/ucsi/ucsi.c | 9 ++- include/linux/nvmem-provider.h | 2 - kernel/irq/irqdomain.c | 2 +- 43 files changed, 248 insertions(+), 127 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_kernel/gnu-master-aarch64-stable-allyesconfig updated (08fb308d84 -> f5e1d58447)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 08fb308d84 45: onsuccess: #517: 33: Success after binutils/gcc/linux/qe [...] new f5e1d58447 46: onsuccess: #518: 33: Success after binutils/gcc/qemu: 32 [...] 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 1784 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2808 bytes 03-build_abe-binutils/console.log.xz | Bin 36768 -> 31836 bytes 04-build_abe-stage1/console.log.xz | Bin 74544 -> 74144 bytes 05-build_abe-qemu/console.log.xz | Bin 32708 -> 32276 bytes 06-build_linux/console.log.xz | Bin 6180 -> 5052 bytes 08-check_regression/console.log.xz | Bin 4536 -> 3900 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[linux] branch master updated (837c07cf68fe -> 870c3a9a2bc4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from 837c07cf68fe Merge tag 'powerpc-6.2-4' of git://git.kernel.org/pub/scm/ [...] new 4f64a6c9f6f1 perf: Fix perf_event_pmu_context serialization new de506eec89d8 Merge tag 'perf_urgent_for_v6.2_rc7' of git://git.kernel.o [...] new 9d2c7203ffdb x86/debug: Fix stack recursion caused by wrongly ordered D [...] new 9e482602c594 Merge tag 'x86_urgent_for_v6.2_rc7' of git://git.kernel.or [...] new 5b3fc9988d1e fbdev: aty128fb: Use backlight helper new 1535ec976414 fbdev: atyfb: Use backlight helper new c28509ef9c22 fbdev: radeon: Use backlight helper new 973fcf37c267 fbdev: mx3fb: Use backlight helper new 1cc17590ddfe fbdev: nvidia: Use backlight helper new 450afd92d9cb fbdev: omapfb: panel-dsi-cm: Use backlight helper new 8791906e667e fbdev: riva: Use backlight helper new ee4202db16e5 fbdev: atmel_lcdfb: Rework backlight status updates new 67a90bccad3d fbdev: fbmon: fix function name in kernel-doc new ee9fffdc3887 fbdev: omapfb: Use kstrtobool() instead of strtobool() new 2b09d5d36498 fbcon: Check font dimension limits new 870c3a9a2bc4 Merge tag 'fbdev-for-6.2-rc7' of git://git.kernel.org/pub/ [...] The 16 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: arch/x86/include/asm/debugreg.h | 26 +++++++++++++-- drivers/video/fbdev/atmel_lcdfb.c | 22 +----------- drivers/video/fbdev/aty/aty128fb.c | 6 ++-- drivers/video/fbdev/aty/atyfb_base.c | 8 +---- drivers/video/fbdev/aty/radeon_backlight.c | 6 +--- drivers/video/fbdev/core/fbcon.c | 7 ++-- drivers/video/fbdev/core/fbmon.c | 2 +- drivers/video/fbdev/mx3fb.c | 7 +--- drivers/video/fbdev/nvidia/nv_backlight.c | 8 +---- .../fbdev/omap2/omapfb/displays/panel-dsi-cm.c | 8 +---- .../video/fbdev/omap2/omapfb/dss/display-sysfs.c | 7 ++-- .../video/fbdev/omap2/omapfb/dss/manager-sysfs.c | 7 ++-- .../video/fbdev/omap2/omapfb/dss/overlay-sysfs.c | 3 +- drivers/video/fbdev/omap2/omapfb/omapfb-sysfs.c | 3 +- drivers/video/fbdev/riva/fbdev.c | 8 +---- include/linux/spinlock.h | 9 +++++ kernel/events/core.c | 39 ++++++++++------------ lib/dec_and_lock.c | 31 +++++++++++++++++ 18 files changed, 108 insertions(+), 99 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_cross_build/master-aarch64 updated (3937b97deb -> af0ca75b3e)

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 3937b97deb 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards c4d1c59ee2 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards d649fac0c8 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 2dad050990 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 52a055bf9a 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards cd665576a9 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards c9873c619b 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards ea07f0bb4d 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards bc42780ad8 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards f7d0111dd6 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards b06d169499 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards b90da7931f 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards 9ea915fe70 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards 177acfc700 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 5c4024315c 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards 1d6e142915 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards ccd340c306 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 447f6c5a65 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 67456caf41 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards fcbf542ae7 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 8b7062b04a 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards b8b2853c32 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards cfee2f4cb2 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards ef8f63a602 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 425e6d417e 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards 9e61ff71ce 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards e5f0617be2 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards bd6d86b23b 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 0e008db40c 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 32331d9f5e 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 07d6da003a 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 54df6f3e3b 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 0c2305a281 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards e3c54b8818 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 5ea0585e0f 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards b9423fb4ff 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards 2f4f056564 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards a141232842 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards 7a9a736ec5 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards ae28f66342 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards d2daac7505 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 71d0577dce 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards ca3dcb120f 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 3f02d5b996 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 98683369f8 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 284c0f7030 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards 390c5cea20 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards 8c028121c4 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards c2cd1cda0d 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards 2095383f7a 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards ffdf8315f1 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards 1651a4b0fa 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards cf0b14ea4a 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 2ba1240b41 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 5c89958b13 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 8421a17589 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards fb3077e77c 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards cff7c52ad6 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 36e8618c58 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards a0ec0f5745 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards fcaab365bf 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards c837f428ab 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 6dede52a14 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards e96c500402 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards 0bef5e5e5f 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards ba154430df 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 353503caeb 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards dfb3d359bd 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 82dbfc6a2b 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards eff3dea30a 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 8d7766c0ae 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards b595d44787 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 10ba49772f 305: force: #2006: 7: Success after gdb: 2 commits discards e08d2ef31d 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 9512197fe2 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards f73bceca12 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards becf8681c9 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards eb684052e0 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards c9cf68a676 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 75cd989c26 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 530fd468ba 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards fc47c3fac9 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 0cc71e3471 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards 9aa7a72eab 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 1e5135b4d6 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards a12fdca0a8 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards 70ab108b84 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 7a40cf618d 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 8b667f68d6 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards bd2241f979 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards d95bd3098a 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards 5d7e794ded 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 7c9a78e927 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards 19963759f5 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards c06a9f12f4 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 982976288a 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards 5507ae7e04 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards b27e75ee33 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards 4a3c04b43a 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards b6df3d568c 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards eada9ab025 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 36816f3196 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 4b8d297814 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new 294d2c1981 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 1b03dbb6f9 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new 31d06779ff 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new ad1df90a31 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new d0bfc2a54b 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new b08f2fcdf3 284: onsuccess: #1981: 7: Success after gcc: 2 commits new 324929f7df 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new ca3c786b77 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 45f8edfe69 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new 6b84feb90f 288: onsuccess: #1985: 7: Success after gcc: 17 commits new 025badc481 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new ef3590dab2 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new 76454ab015 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 73a94cad83 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new fab07c994a 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new acc35278c4 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 1715506731 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new 2ddeebe74c 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 8a6e8d806d 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new 4bae4a5dea 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 2b2bc09b77 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new 1592a884d8 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 91305c1d53 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new bab5418d08 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 139412e6a9 303: onsuccess: #2001: 7: Success after binutils: 4 commits new da1963bad9 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 8b969dd5d0 305: force: #2006: 7: Success after gdb: 2 commits new b3907dad98 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 94ae9a01a6 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new 428a9576a3 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new bcd417f62e 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new a0d493c4c4 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new f13efc95e8 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 208dc3d65b 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 8ca3e65365 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 339c2567bc 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 5add432976 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 0eaa64c23a 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new 10bae40c03 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new f17194b936 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 239e322f46 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 81b033ca00 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new bdfa704050 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 80daea578b 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new f1a45204d6 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new eaeb4023e0 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 34acc514cb 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new d8c0dc032b 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new b5da52783c 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new f5fec3d59a 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 481d8f08b1 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 92da2bcd44 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 6416ceaf84 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new ab4d4027e6 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 0ea795f6d3 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 6b065e186f 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new 4712e94fed 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 096d39018e 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 0d08beef20 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new 8cf730f045 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new 17c052fdb4 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 00f03096b0 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 26b3a6716f 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new 4e518f82dc 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new e62611cc31 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 3cca8ae14c 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new f9592e49a3 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 2153f029f1 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 868bbae430 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new a5bd8e36ee 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new e7572177c0 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 8046d3734a 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new 1de6101660 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 3b531c4a89 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new 1e148db1ee 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 58866a8e3a 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new 42ced0de2f 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new c109bff377 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new 15f0d2d054 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 2890216392 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new 687e9e4e95 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new ab601b1bf5 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 1a40459094 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 836e1dcc3f 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 5fe68ea7d9 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new 4179ec267f 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new e4d672a0b6 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new 4391f7a0cc 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new aa57b877e5 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 505ffa0fc9 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 00198c941f 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 8d8f7b70fe 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new 3ba49c6972 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new 9b18a56f7d 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new d745fa752c 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 236a7a155f 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new 14e8a05065 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new 81d22ebfb2 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 7ebb1c94fc 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new af0ca75b3e 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 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 (3937b97deb) \ 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 1808 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2792 bytes 04-build_abe-binutils/console.log.xz | Bin 31380 -> 31244 bytes 05-build_abe-stage1/console.log.xz | Bin 73412 -> 73220 bytes 07-build_abe-linux/console.log.xz | Bin 9008 -> 9032 bytes 08-build_abe-glibc/console.log.xz | Bin 246140 -> 245168 bytes 09-build_abe-stage2/console.log.xz | Bin 206872 -> 204524 bytes 10-build_abe-gdb/console.log.xz | Bin 38648 -> 38356 bytes 11-build_abe-qemu/console.log.xz | Bin 32636 -> 32440 bytes 12-check_regression/console.log.xz | Bin 3196 -> 3556 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++-------- 18 files changed, 55 insertions(+), 55 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_cross_check_gcc/master-arm updated (a977f2b46e -> 5730051ef8)

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 a977f2b46e 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards aff771b461 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 089b781634 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 4a342ab5e2 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards b249595f86 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 2693a40854 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 8bc4b08049 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards e3cb43811e 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards e16afdde0e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 980a41b7ca 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards ff95f8e2d3 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 83df08b678 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 313d2ede3d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 266d02e526 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 8e0a9ffbe0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 83d8900889 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards d14909de0e 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 44ab5483b1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards f335998590 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards b7ac50a573 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 08bb61b1a9 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards de01bcf28d 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 9cf60a095d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards c89716d056 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 70aed267c5 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards ef6354e64e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 46c671f1bb 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 01525088bd 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards e3c8587546 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d18c738d47 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards aa896c09dc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 6ef7614923 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards d82972d28f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 8a2db9d400 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards a6009ba2de 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 849c92a30d 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards c82da63f2f 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards db85138b62 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 9d449d44d3 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards e59aef22e6 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 430385b99e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards e502ae275b 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards e20d2f9b91 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 72e3d3d1b3 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 60973efba2 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 16eb5b73dc 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 6a695ff5b1 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards e2e1174d07 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 2b6914644e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 2c2abadb41 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 67c85eb561 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 746403d77e 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 4c7794b206 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 7e48d73740 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards e22e3a5feb 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards df83083ce9 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8de862b4b3 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 75c85a2270 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 6635ec04d7 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 226c3bac75 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 8853da5227 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 007a02a593 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 94c69e35ce 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 381099e3da 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 6db225ba6f 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards c1efae1e5a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 6756fe00ae 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards ab33e67079 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards be30d98236 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 5c87742a95 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 5e3cd088aa 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 100c5bed58 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 48303af927 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards a1abd52b19 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 05c00e63b4 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards dcf9aedd8f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 717769314e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 9254bb2a95 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 8e0f2a2caa 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 117ecdfa9e 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 51d25599d2 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 302776fc4c 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards a2331b137e 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 1a1dff1124 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 38d64db621 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 35cbb461b3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards a48e5bb469 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards d398c4d647 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 29a7bd5595 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 126494ab4d 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards fdc2efa2c2 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 8c37c81ba6 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 990dbf57a5 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 7152201260 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards a06a6d2106 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 662e5e86c2 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 06fd1ebc5b 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 5efc5f3799 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 71e1f028df 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 5c877888d6 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards b1c2a3c4ef 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new a1d4689ad7 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 182123ac73 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new ab9782927f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 4c08bd6d86 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new f9adbeb3bc 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 32eaa453a0 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 95dd9c1ded 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 7cf00488cc 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 7ede9cd3f0 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new ea970cfc85 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 57ca50d388 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 199ee622c0 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new dd37b22099 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 876641891b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 810adeafeb 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 4334d32e0c 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 6b3e33ff52 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new a6a8734760 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 96ccd65748 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 26603dda80 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 045e89fef1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 593c0a64cd 301: onsuccess: #2118: 1: Success after linux: 16 commits new 5c56d55ae6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new a0073e3fb3 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 53edd470ee 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 4e5a4941a7 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 4270c2a60f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 86e3e99bb1 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 8895d3ce04 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 84d2b31de3 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new bd61d7b1b7 310: onsuccess: #2129: 1: Success after binutils: 4 commits new bd1b209548 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 9bd6fbec2b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 7cf5a77e01 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 787482c853 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 537688b0ee 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 1dd8648e4a 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 7d8f3830a0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 7d3b0703bc 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 690b94b9f4 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new e4f78463e0 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new c0ae260f12 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new ccda61275f 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 1d6cfb50a0 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 6aacce8e84 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 8ac0299e4b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f686e53b8b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new c3251414fc 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new a8db67d6bd 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new bfbfd463f0 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 5779ff90a0 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 8705db7dbd 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 4446099b4d 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new aa473eb93d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new f5cd689d63 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5fe0743411 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 70041e930a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new cb122dd145 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f7e8e11215 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 8dfc42b6c1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 6eb17ad455 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 448f92fef6 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 7bc8e70a3c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 222ce5d2cf 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 2b7492e36c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new e4b53f1aaa 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 2f54736582 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 19ade12fb0 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new f601e666aa 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 9b8e7d3357 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 2a6e299461 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 6fe4bd4b75 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new e641566c61 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 2d62aa5984 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new a0174804bb 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 2feb7bcc55 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new c17a57e401 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 3e6e2326a6 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 6b796cb172 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 5e6248db39 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 71fd849bd0 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 4949f4f7fa 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 71e26698b4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 2e54ac205c 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 957a2b4eb8 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 73c1e5f346 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 7c0aa9cf7f 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new a130b75a5d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 4f9768ea90 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 90c550d02b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 76365fe755 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new ece08773cf 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 7ea70827dc 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 03560cb54d 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new ff1e1f42cc 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new d0418474eb 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 6ead0c1802 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 757594f9d7 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new c47be7da6c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 7224520f29 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new e751951428 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 5730051ef8 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-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 (a977f2b46e) \ 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 1812 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 30856 -> 30976 bytes 04-build_abe-stage1/console.log.xz | Bin 91704 -> 91656 bytes 06-build_abe-linux/console.log.xz | Bin 8980 -> 9064 bytes 07-build_abe-glibc/console.log.xz | Bin 235844 -> 236528 bytes 08-build_abe-stage2/console.log.xz | Bin 227452 -> 228720 bytes 09-build_abe-gdb/console.log.xz | Bin 38112 -> 38264 bytes 10-build_abe-qemu/console.log.xz | Bin 31800 -> 31852 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2632 -> 2644 bytes 13-check_regression/console.log.xz | Bin 5728 -> 5100 bytes 13-check_regression/results.compare | 12 +- 13-check_regression/results.compare2 | 34 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- sumfiles/g++.log.xz | Bin 2667840 -> 2635612 bytes sumfiles/g++.sum | 34 +- sumfiles/gcc.log.xz | Bin 2196680 -> 2207848 bytes sumfiles/gcc.sum | 2510 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 893752 -> 892704 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214336 -> 214464 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442836 -> 436188 bytes sumfiles/libstdc++.sum | 25 +- 35 files changed, 1370 insertions(+), 1379 deletions(-) -- 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 (516a10f8c4c -> 1e60e912454)

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 516a10f8c4c Daily bump. new 511928102dc Fortran: fix ICE in compare_bound_int [PR108527] new 1e60e912454 Fortran: error recovery on invalid array section [PR108609] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/fortran/expr.cc | 6 +++++- gcc/fortran/resolve.cc | 29 ++++++++++++++--------------- gcc/testsuite/gfortran.dg/pr108527.f90 | 10 ++++++++++ 3 files changed, 29 insertions(+), 16 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/pr108527.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page: