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 594cce8ac7 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] discards 836512b8e6 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] discards 0728cfd57d 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 358c814206 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits discards b70ed19ad4 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits discards c238c7192b 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits discards 7f21d60e00 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards 80e2c45ea8 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards 7a8bd72b7a 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards 55e2b7cc44 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards d7a58731d1 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards 10b1687330 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards fd85f29883 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards a172ef3dd4 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards 8dc4dbbde8 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 21305b0be4 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards f2f5f83537 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 17e59403e9 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards b9ec63bdc3 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards e7e10a8fb7 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards f59b833646 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards a551aed462 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 392fdb7e30 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards ffe45d3f7b 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 9b603b58a3 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards 364855e3d7 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards d5701b5197 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 63ffea63fe 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards f54851e532 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 61f3649658 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards adb7c9e75f 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards bb085e05b1 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards 14c726e099 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards ceda781a76 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards 6956a0c9aa 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards e4c3578dfa 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards 6b9aeea255 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards e36f74e953 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards 4e0b68e172 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 0d902e03f9 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards 782da2f969 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards 2789afc519 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards dc9e7753d7 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards c37b706eee 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards ae14fb700e 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 957e058266 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 0684246895 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards cc1939d9f4 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 06211ac3e6 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards ef17a306ba 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards c515915571 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards 1ded0586f2 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards ec8487a882 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 4913627759 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 94ee650172 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 11405b9650 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 198a49902f 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 5413ac868b 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards aa1bd8ed20 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 056edfe902 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 4ffdf1e410 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards 0677087e2e 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards 19f361738f 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards 0df16c4cf9 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards 68ff072569 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards b52114af6e 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 31f5593c7b 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 97a2dd4193 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 3a53385f24 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 7c4eff472b 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 4f64d6eb07 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards d573d115e7 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards 1fceb2346b 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 01272738e3 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards 177d212506 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards a704488d41 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards bee08fc425 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 8221928899 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 03541ad972 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 83380b4854 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 8853f76565 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 4c706f6272 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards c97d76a3cd 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 1e3f4dc5dc 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 0e2676ffef 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 9b1cc94a89 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards b3334c4528 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 8c98028d3d 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 61b99e0d67 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards 0bb845a1e2 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 0202b64b07 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 1e37c307d1 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 75c7639cd1 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 36268c3237 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards cac5a5183d 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 61a4616307 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 00d1710797 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 04ee3461a7 305: force: #2006: 7: Success after gdb: 2 commits discards b94e1e72f2 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 2a8fdbd402 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 528f46baf8 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 210f3f077e 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 457045811d 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 242b770a26 304: onsuccess: #2002: 7: Success after gcc: 4 commits new ae802c4b45 305: force: #2006: 7: Success after gdb: 2 commits new 9fed74fb20 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new e2dd27aac9 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new 20be0f316f 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new f8a530b117 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 11a6542d01 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 39f45ddda0 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 7f71b17d0b 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new d25c30bdf8 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new a8d40f31c9 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new ffb7d51f68 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new f93d30bcdc 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new c31162abe8 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 4511f9c8e2 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 2576597b4d 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new d34d1d35f1 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new ec7e20d972 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 718288d51a 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new b872993dff 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 4bdad2cf2e 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 9ce5f6d1c2 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new 48326b914c 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new da89f13f44 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 25e2d309b2 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 51eb13a874 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new d42ebc54c9 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 7856db9f56 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new b513b8b706 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new bb28656dbd 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new a19d15e2cc 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new a4478ce68c 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 3d01be8a4d 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new a945c49535 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new 1413395212 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new cb53aeaab3 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 2bda1fcbe4 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 23d0d625ed 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new 02df1ff409 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 50d57d9c85 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 5129850192 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new a5b0514c83 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 119bcb89ca 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 05cc96683a 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 4d0bad871f 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new 9d4c8ef667 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new b0a978ab36 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new 486d1c1a66 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 57a98e3c62 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new 46fd331762 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 0520c5a826 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new f5776849f9 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new 02a9e886b3 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new 778ca1333d 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 48a09b2896 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new 2484857db4 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new 69b6398e88 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new bae63d061e 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 540c7fa86b 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new cfa652933d 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new 26bdd05677 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 5759a91863 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new f44ac1a5d0 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new 7aef680897 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new f2e0d5de00 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 6c0879e8f4 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 6c71251d0f 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new 7b783d1e6b 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new 9f70248551 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 8655a4dc40 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 8dc54c71ce 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new 7d8f824a41 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new 9dd5947d49 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new a7ad51f464 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new bccf8cf016 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new ac2db09247 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new 5ce90cc403 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new 6bc5e53ad1 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new b604a45d18 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 6844469d8d 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 711a7f649d 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new b14e75cebc 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new ecfda82d47 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new d2c5d301eb 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 629872359c 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new da95cb771e 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new 178150d4fb 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new 3572ca871b 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 477013f0bd 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new 73c1607e3a 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new 3f6bd01492 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new 59a793432e 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new 4f72e04964 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new a1732b5be5 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits new ec38ffadd1 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits new 43fe246e12 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits new e18cd19c51 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 30c86b875a 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] new a92d0c9973 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] new 096704821f 403: onsuccess: #2106: 7: Success after glibc: 12 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 (594cce8ac7) \ 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 1776 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 31308 -> 31592 bytes 05-build_abe-stage1/console.log.xz | Bin 72924 -> 73416 bytes 07-build_abe-linux/console.log.xz | Bin 8636 -> 8668 bytes 08-build_abe-glibc/console.log.xz | Bin 244928 -> 245144 bytes 09-build_abe-stage2/console.log.xz | Bin 205100 -> 204856 bytes 10-build_abe-gdb/console.log.xz | Bin 38544 -> 38756 bytes 11-build_abe-qemu/console.log.xz | Bin 31624 -> 32192 bytes 12-check_regression/console.log.xz | Bin 3692 -> 3456 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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 | 22 ++++++------ 17 files changed, 49 insertions(+), 49 deletions(-)