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 841f43cbaa 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] discards a5290b5a17 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 591ec0e93f 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits discards f7a61c8b71 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits discards 5366eba6c2 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits discards 1c9d261279 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards 7f09942d9b 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards fd89dcd6c2 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards 254ea51b32 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards cc97184585 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards ca4d8a01b5 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards cbb3cfd98c 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards f306255da7 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards 2580dfbd2c 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 0b193417ab 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards fe8d71ac25 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 2703519356 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards 389e53241f 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards 3e181df52f 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards f5b5729b71 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards a7a75424c7 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 9b480b7b1f 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards aa01cfb6ae 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 3620aad799 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards 5cd5b5865b 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards f7cd92684e 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 72321302fb 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 8054f874bd 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 99a73bea48 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards ab010ba546 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards fbddfdb8e0 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards b4bc33204a 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards dbe9b2e0cc 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards 52a2ee606a 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards ec6473571f 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards 1121d34048 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards b534779ec0 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards a6aee8a95a 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 4debf72588 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards df6c8a09a5 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards 9cdd876f8e 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards e3d57dfcd4 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards d19b020525 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards c7ad23f810 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards f3e19943b9 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards cf240bc194 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards f730cfbef6 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 890dfc58fc 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 441c2daf94 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards 270d43b72f 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards 1b3b10dc8b 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards c6e9b3b22b 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 430e191a73 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 78b2fc2723 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards cdc3353092 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards e27b5b974b 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 3790625bc6 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 61dfe72b2f 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 2ca54d4c97 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards d5cde7d867 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards b4c0deaaf2 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards be1461c3d2 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards cbdec8298e 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards b86b53e62f 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards 625132fa45 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 7334ac4aca 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 4070a0f841 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 58732f7fc1 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 28e08e6756 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 5089172f9b 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards 3f11e36f3c 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards 907b2be865 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 08865afb72 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards 0f19782e41 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards 379764d080 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards c696f647fc 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 2ccf0ccc6a 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards dcbab66e2f 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards b4cdffef29 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards c5f5cc84bd 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 0222a192fa 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 7b11637d80 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards a5806494ab 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards e3478be89b 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards a73db0af40 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards 25feef1b79 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 5c21f4a90e 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 00fdafc20f 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards a360791e88 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 3c504b8e57 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 9b817c293a 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 120754f11c 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards a6854a023d 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards e3ad36fc64 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 72c977749f 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 2979414b5c 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 07bc42926a 305: force: #2006: 7: Success after gdb: 2 commits discards cf08b5c54c 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 1b8b3f69db 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 8b2f35bc35 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards b43af7f0f1 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 095682cd56 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 528f46baf8 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 2a8fdbd402 303: onsuccess: #2001: 7: Success after binutils: 4 commits new b94e1e72f2 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 04ee3461a7 305: force: #2006: 7: Success after gdb: 2 commits new 00d1710797 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 61a4616307 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new cac5a5183d 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 36268c3237 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 75c7639cd1 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 1e37c307d1 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 0202b64b07 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 0bb845a1e2 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 61b99e0d67 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 8c98028d3d 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new b3334c4528 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new 9b1cc94a89 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 0e2676ffef 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 1e3f4dc5dc 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new c97d76a3cd 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 4c706f6272 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 8853f76565 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new 83380b4854 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 03541ad972 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 8221928899 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new bee08fc425 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new a704488d41 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 177d212506 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 01272738e3 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 1fceb2346b 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new d573d115e7 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 4f64d6eb07 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 7c4eff472b 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 3a53385f24 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new 97a2dd4193 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 31f5593c7b 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new b52114af6e 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new 68ff072569 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new 0df16c4cf9 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 19f361738f 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 0677087e2e 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new 4ffdf1e410 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 056edfe902 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new aa1bd8ed20 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 5413ac868b 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 198a49902f 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 11405b9650 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 94ee650172 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new 4913627759 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new ec8487a882 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new 1ded0586f2 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new c515915571 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new ef17a306ba 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 06211ac3e6 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new cc1939d9f4 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new 0684246895 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new 957e058266 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new ae14fb700e 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new c37b706eee 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new dc9e7753d7 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 2789afc519 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 782da2f969 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 0d902e03f9 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new 4e0b68e172 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new e36f74e953 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new 6b9aeea255 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new e4c3578dfa 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 6956a0c9aa 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new ceda781a76 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 14c726e099 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new bb085e05b1 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new adb7c9e75f 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 61f3649658 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new f54851e532 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new 63ffea63fe 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new d5701b5197 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 364855e3d7 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new 9b603b58a3 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new ffe45d3f7b 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new 392fdb7e30 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new a551aed462 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new f59b833646 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new e7e10a8fb7 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new b9ec63bdc3 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new 17e59403e9 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new f2f5f83537 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 21305b0be4 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 8dc4dbbde8 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new a172ef3dd4 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new fd85f29883 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new 10b1687330 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new d7a58731d1 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new 55e2b7cc44 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new 7a8bd72b7a 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new 80e2c45ea8 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new 7f21d60e00 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new c238c7192b 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits new b70ed19ad4 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits new 358c814206 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits new 0728cfd57d 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 836512b8e6 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] new 594cce8ac7 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...]
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 (841f43cbaa) \ 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 1740 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 33736 -> 31308 bytes 05-build_abe-stage1/console.log.xz | Bin 73344 -> 72924 bytes 07-build_abe-linux/console.log.xz | Bin 8692 -> 8636 bytes 08-build_abe-glibc/console.log.xz | Bin 245344 -> 244928 bytes 09-build_abe-stage2/console.log.xz | Bin 205360 -> 205100 bytes 10-build_abe-gdb/console.log.xz | Bin 41080 -> 38544 bytes 11-build_abe-qemu/console.log.xz | Bin 31876 -> 31624 bytes 12-check_regression/console.log.xz | Bin 3692 -> 3692 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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 | 30 ++++++++-------- 19 files changed, 55 insertions(+), 55 deletions(-)