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 f5811bb45c 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards e62a3ce56e 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits discards adbb96bc8b 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits discards b3bb296759 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits discards d514c97052 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards 16d1e24d59 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards 335f3d9644 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards 95b7fd1e28 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards 3f3bf707d5 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards f66d08b6d1 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 0d9c49f67b 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards ee805ec76e 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards ea7474e7e4 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 8bcb43b264 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards cd98fe18f9 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards fe942db1b4 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards 376c2717b4 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards 33dc0b3922 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards f11bd5db01 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards addde5d08c 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 40c3bf6fdc 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 4b542203ec 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 741a0c721c 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards 10d18b5d71 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards a3a67e7ca0 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 2c607665e4 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 19ae80df4c 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 259006e154 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards d7e64b9d6b 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 28aadddf2a 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards 402f7cafc7 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards 705b05d85a 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards c016e54d92 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 2aa828afda 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards bfb7e1daa2 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards ce48cb240c 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards c753691235 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 955fb1a2c2 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards 5682c20ae6 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards 1275d5b10d 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 754be6352e 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards bcaaa21d8b 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards e4c93dbb54 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards ef98896099 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 2cb594c8fe 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards f253c3196f 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 7e6bccbcfe 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 0e7609f15b 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards eb3ec2f04e 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards 0f11ffd07d 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 86fcab4bc2 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 2e5095ea30 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 3ca02fac2b 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 079def301c 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 0fc45e718a 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 6e9b3d7844 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 9c686f5478 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards fc0fe4560a 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards cbbbc17698 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards 05002b1fc1 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards 7aeb0aebef 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards 7912b67786 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards 6bc4cffac1 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards cf22c01e5e 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards aa5c0101a9 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards bcf9f695c5 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 20fd9e7940 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 5bb90f90d0 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 5f4927efb2 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards 1a3e762588 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards ff01becfa6 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards fc6091fe15 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards 1cdc8f06c5 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards 55ed16f7be 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards a625cf9673 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards a0b5a47e0a 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards d738791ac0 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 726f233bfb 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 3dc551e21d 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards fb74ba663f 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 98482e9f24 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 2520c12fe0 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards c17695eb9e 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 52265cd780 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards f833c9cbbf 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 677c6c7161 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 3068e08332 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards 2a54aa87b1 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards cee7db964a 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 00887b63bd 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 7e2c0709d3 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 84cc530a93 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards efbe376b7b 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards b20bdf1379 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards efa5d379a4 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 04115b03e9 305: force: #2006: 7: Success after gdb: 2 commits discards a6050931b4 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 73898ad3fd 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards b3d277cf25 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards fdb943535d 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards d0c0da3e0d 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 3b65d1499b 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new b43af7f0f1 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 8b2f35bc35 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 1b8b3f69db 303: onsuccess: #2001: 7: Success after binutils: 4 commits new cf08b5c54c 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 07bc42926a 305: force: #2006: 7: Success after gdb: 2 commits new 2979414b5c 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 72c977749f 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new e3ad36fc64 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new a6854a023d 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 120754f11c 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 9b817c293a 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 3c504b8e57 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new a360791e88 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 00fdafc20f 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 5c21f4a90e 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 25feef1b79 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new a73db0af40 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new e3478be89b 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new a5806494ab 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 7b11637d80 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 0222a192fa 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new c5f5cc84bd 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new b4cdffef29 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new dcbab66e2f 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 2ccf0ccc6a 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new c696f647fc 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 379764d080 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 0f19782e41 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 08865afb72 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 907b2be865 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 3f11e36f3c 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 5089172f9b 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 28e08e6756 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 58732f7fc1 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new 4070a0f841 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 7334ac4aca 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 625132fa45 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new b86b53e62f 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new cbdec8298e 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new be1461c3d2 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new b4c0deaaf2 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new d5cde7d867 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 2ca54d4c97 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 61dfe72b2f 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 3790625bc6 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new e27b5b974b 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new cdc3353092 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 78b2fc2723 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new 430e191a73 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new c6e9b3b22b 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new 1b3b10dc8b 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 270d43b72f 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new 441c2daf94 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 890dfc58fc 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new f730cfbef6 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new cf240bc194 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new f3e19943b9 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new c7ad23f810 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new d19b020525 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new e3d57dfcd4 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 9cdd876f8e 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new df6c8a09a5 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 4debf72588 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new a6aee8a95a 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new b534779ec0 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new 1121d34048 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new ec6473571f 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 52a2ee606a 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new dbe9b2e0cc 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new b4bc33204a 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new fbddfdb8e0 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new ab010ba546 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 99a73bea48 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 8054f874bd 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new 72321302fb 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new f7cd92684e 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 5cd5b5865b 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new 3620aad799 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new aa01cfb6ae 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new 9b480b7b1f 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new a7a75424c7 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new f5b5729b71 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 3e181df52f 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 389e53241f 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new 2703519356 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new fe8d71ac25 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 0b193417ab 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 2580dfbd2c 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new f306255da7 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new cbb3cfd98c 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new ca4d8a01b5 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new cc97184585 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new 254ea51b32 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new fd89dcd6c2 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new 7f09942d9b 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new 1c9d261279 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new 5366eba6c2 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits new f7a61c8b71 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits new 591ec0e93f 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits new a5290b5a17 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 841f43cbaa 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...]
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 (f5811bb45c) \ 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 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 31168 -> 33736 bytes 05-build_abe-stage1/console.log.xz | Bin 73048 -> 73344 bytes 07-build_abe-linux/console.log.xz | Bin 8640 -> 8692 bytes 08-build_abe-glibc/console.log.xz | Bin 244744 -> 245344 bytes 09-build_abe-stage2/console.log.xz | Bin 204036 -> 205360 bytes 10-build_abe-gdb/console.log.xz | Bin 38452 -> 41080 bytes 11-build_abe-qemu/console.log.xz | Bin 31592 -> 31876 bytes 12-check_regression/console.log.xz | Bin 3708 -> 3692 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(-)