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 b81c257a47 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards f533ab93bf 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards fd1ab12aa6 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards 2f249bcdbb 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards cc1ef6c520 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards 24fe26504c 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards a7aa994dcd 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards 9b658d7b18 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards cfb9c7194b 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards a3fd88f78d 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards 765e477aaa 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 90e83a6649 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards 574cbab016 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards b20059bde6 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 43710033a7 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 5820350cdf 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards e6d95b1861 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 6bf248ea38 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards e20e2d8245 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards 2ce5309e41 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards d84b1cfac4 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 06532799c8 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 9113b33c59 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards bac3c94ed7 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards 96eebe9cbe 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 5b612913ef 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards f2f72c5577 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards 9e9af92460 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards 135dac1872 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards d5c6774811 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards 8d3ec522f6 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards b963f7e1cd 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards 39aab2718b 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards bbfc8b9501 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards 9f50753dd4 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards 52b86a6593 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 04941348e3 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards adbf435467 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards 7b84b2b198 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 46107a3c83 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards cc628d511e 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards c286d4f793 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards c02c425111 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 9b653bf1e7 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards 8f6847014e 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards ae0b8d8c8b 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards ed2d7b9fc1 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards f6c6963648 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 0fb95eb989 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 09416f5103 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 084f424c40 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 85b531d8c4 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 08d605a0e0 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 39b9a50a47 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 7fdfb6d55f 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards c82c8d8511 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards 7ad880c0a6 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards 3cf1759390 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards ac750cb259 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards e012179f73 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 9afcbc5382 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards cc6de6593d 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 6d4131c75b 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 1efa946931 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards d05ab3213f 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards 1ff9354042 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards c98223d89f 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 20879f4352 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards f5438e75ae 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards c1fb350437 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards a6e497ce80 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards b888e08632 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards eeb5bb286a 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 842f6404c4 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 155b907565 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 8655264f57 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 5721391bd0 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 3ac67834c1 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 95102daa5e 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards ae9aad49a5 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards 04c23a418a 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 9184d291f1 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 645e7949cc 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards 12a54764a0 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 4fd5b951fd 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 563d0203e5 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards f69a1d5dc7 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 7b8b2a14cc 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 4d77e74d73 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards a5ea67fadc 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 432feb1f82 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards b4af3c0fd0 305: force: #2006: 7: Success after gdb: 2 commits discards a1281c3d01 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 827ad20e71 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards a794cd5be9 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards 9b1e8b5177 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 66aa808a01 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 88cf902b66 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 9572ce9e2b 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards a28eb6cbd1 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 1c676131fb 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 62703e603b 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new b9fa14ddd6 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new f24e08b0e9 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 94363f663c 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new f47e67e39a 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 51c6caed04 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 9d417d6f0d 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 2c3427d75d 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 1d5a9d7aa7 304: onsuccess: #2002: 7: Success after gcc: 4 commits new ad2141cdc1 305: force: #2006: 7: Success after gdb: 2 commits new 3fa5ea2f80 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new bb5547005d 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new 2d4a7abaeb 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new cd591dd776 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 37d612a5da 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 8957d53b0a 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new f74a54eac1 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 3c4f1f4f58 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 2de5b1f281 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 8235fb8867 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 99f6dfef83 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new ac0ab5b80b 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 9e0c17798b 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 01ac87b24e 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 0adddc1933 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 904368f500 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new dc73e5c1ec 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new ca15cf4a2c 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new a524d50a7b 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 69e0c4d0c6 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new 6c230a9697 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 38625532f4 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 03cdd217c5 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 899957ce18 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 07b3e8e418 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 8e982283c6 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new d564da8cd9 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 63547b6bf9 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 1b2a530020 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new 457f15e506 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 3c97d8938f 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new bd8ed033c9 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new de9154d190 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new fff1078024 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 5ffdb2c381 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 7fe8b41908 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new c4c2f7a0d2 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 35bc5951c9 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new cd331171fd 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 6a389e6ad2 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new fe6c20bf94 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new a1e3599c70 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 35abb44917 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new 04132ba525 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 98d1ca507b 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new a111868072 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new e4f0bfbc48 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new f852d53c84 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new df4b4faf10 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new a19bcaf430 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new c0a74684b9 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new a7ab91c5ba 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 2a9149bb00 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new 7e2a140a73 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new ec2140df5a 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 87598c03af 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new b2b7f77e8b 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new e8c4013da9 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new 508d061b69 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 28f8d196eb 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new a53bca6f39 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new 70920ad74a 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 5544c06a6e 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new fcc2379e58 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new a0a6e9194e 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new ec092a28e6 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new ef8eb3964b 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 8f37837797 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 1e4f38552e 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new 9189faa45e 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new 083b7e02de 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 37061ff0ee 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new 0ef184dcb2 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new 5a3e3cdb46 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new b2763e7742 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new c466f945d7 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new d76c49382b 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 000ba0fa90 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 14332af1d3 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new 9a2717ddd0 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new 1c155abcfa 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 52351663e8 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 088c898042 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 85be856420 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new d92b5fa677 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new eabf951066 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 5cfaf5c375 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new 568af9e9c6 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new e2c936e32d 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new a5e202e725 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new d35432bbb0 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new 1b44a61e3b 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 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 (b81c257a47) \ 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 1764 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 30972 -> 31748 bytes 05-build_abe-stage1/console.log.xz | Bin 72960 -> 73028 bytes 07-build_abe-linux/console.log.xz | Bin 8680 -> 8688 bytes 08-build_abe-glibc/console.log.xz | Bin 245164 -> 244704 bytes 09-build_abe-stage2/console.log.xz | Bin 204648 -> 204504 bytes 10-build_abe-gdb/console.log.xz | Bin 38372 -> 39084 bytes 11-build_abe-qemu/console.log.xz | Bin 31640 -> 31516 bytes 12-check_regression/console.log.xz | Bin 4192 -> 3496 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++---------- 19 files changed, 56 insertions(+), 56 deletions(-)