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 7c652e3d80 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits discards 958a8b7085 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits discards 094e40af74 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits discards 5b901eb26f 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards b6b13619f4 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards 249a3fcf9c 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards 495a287d09 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards b110a3103d 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards f75c9066d5 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards aaff384c19 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards f709d76bd3 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards 5d2f278217 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards b24ce1211b 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards c46180169b 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards b75027045a 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards 407a56676d 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards b81873219e 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 48e997a0f8 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 4daf4b8a4a 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards d580a9890f 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 5760616978 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 3e704ed8a1 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards c090128d54 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards eab4401cdc 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 391f0575f5 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards a20457e0de 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards eaa3e7441f 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards 2e713f2e30 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 0389fb9e94 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards 62b5c2953b 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards 8593893ef1 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards 1b280473d0 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 723f9c2687 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards bbde672c61 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards 2b3978e595 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards 2a8dfda127 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 0d967b7f16 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards e84e943866 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards 6195425d11 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 1d68d458bc 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 0c6e41c561 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards 8797ddcdee 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards fb38212291 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 7b28da287c 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards f9a4181579 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards ef58987760 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 0733793eb1 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards b96949d4e2 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards 5e1ee1cfeb 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 1fcdb35b7a 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 0c57271a99 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 1100f74f61 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 48f60f0f52 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 0eba1a9ade 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 33967e2b7e 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 7a25871b61 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 6bbdfa7145 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards dc0d506748 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards e12d0fcb9b 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards 160233a7f4 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards 33c266ea9e 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards 62d3fec377 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards 42bdc280e3 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 301630682c 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 23e323180a 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 17d68b776e 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 614a39a334 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards ffa32ab33f 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards da2609e4b1 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards d3b4a6b5e0 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 99765e76a3 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards d1f4abbfde 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards 852cde4090 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards cbefc2a8b8 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards bfb6c27387 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 870d62e461 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 1b66cca842 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 87f1ee13ff 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 53fa8948ca 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 55264802d7 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 3000e9f366 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 86a8a26495 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 3bf6376c8e 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards efccc205bf 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards bfccbb02cf 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards ccd5726873 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards ddb9e75a72 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 0770e9e61a 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 6d59e0df13 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards a4eef89d57 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 313d1af234 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 3149579141 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 7408add924 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 9ac11a679e 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards ef3ca40d25 305: force: #2006: 7: Success after gdb: 2 commits discards 0d90b15ad9 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 73d777dd4d 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards a782e3d255 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards b98c05850d 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 1f81910729 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 10aad79a49 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new e955ca3f4f 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new d0c0da3e0d 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new fdb943535d 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new b3d277cf25 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 73898ad3fd 303: onsuccess: #2001: 7: Success after binutils: 4 commits new a6050931b4 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 04115b03e9 305: force: #2006: 7: Success after gdb: 2 commits new efa5d379a4 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new b20bdf1379 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new efbe376b7b 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 84cc530a93 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 7e2c0709d3 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 00887b63bd 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new cee7db964a 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 2a54aa87b1 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 3068e08332 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 677c6c7161 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new f833c9cbbf 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new 52265cd780 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new c17695eb9e 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 2520c12fe0 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 98482e9f24 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new fb74ba663f 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 3dc551e21d 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new 726f233bfb 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new d738791ac0 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new a0b5a47e0a 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new a625cf9673 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 55ed16f7be 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 1cdc8f06c5 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new fc6091fe15 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new ff01becfa6 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 1a3e762588 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 5f4927efb2 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 5bb90f90d0 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 20fd9e7940 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new bcf9f695c5 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new aa5c0101a9 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new cf22c01e5e 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new 6bc4cffac1 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new 7912b67786 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 7aeb0aebef 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 05002b1fc1 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new cbbbc17698 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new fc0fe4560a 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 9c686f5478 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 6e9b3d7844 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 0fc45e718a 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 079def301c 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 3ca02fac2b 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new 2e5095ea30 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 86fcab4bc2 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new 0f11ffd07d 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new eb3ec2f04e 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new 0e7609f15b 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 7e6bccbcfe 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new f253c3196f 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new 2cb594c8fe 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new ef98896099 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new e4c93dbb54 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new bcaaa21d8b 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new 754be6352e 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 1275d5b10d 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 5682c20ae6 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 955fb1a2c2 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new c753691235 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new ce48cb240c 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new bfb7e1daa2 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new 2aa828afda 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new c016e54d92 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 705b05d85a 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 402f7cafc7 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new 28aadddf2a 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new d7e64b9d6b 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 259006e154 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 19ae80df4c 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new 2c607665e4 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new a3a67e7ca0 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 10d18b5d71 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new 741a0c721c 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new 4b542203ec 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new 40c3bf6fdc 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new addde5d08c 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new f11bd5db01 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 33dc0b3922 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 376c2717b4 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new fe942db1b4 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new cd98fe18f9 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 8bcb43b264 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new ea7474e7e4 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new ee805ec76e 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new 0d9c49f67b 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new f66d08b6d1 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 3f3bf707d5 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new 95b7fd1e28 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new 335f3d9644 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new 16d1e24d59 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new d514c97052 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new b3bb296759 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits new adbb96bc8b 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits new e62a3ce56e 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits new f5811bb45c 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/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 (7c652e3d80) \ 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 1696 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 31416 -> 31168 bytes 05-build_abe-stage1/console.log.xz | Bin 74004 -> 73048 bytes 07-build_abe-linux/console.log.xz | Bin 8692 -> 8640 bytes 08-build_abe-glibc/console.log.xz | Bin 244948 -> 244744 bytes 09-build_abe-stage2/console.log.xz | Bin 205740 -> 204036 bytes 10-build_abe-gdb/console.log.xz | Bin 38588 -> 38452 bytes 11-build_abe-qemu/console.log.xz | Bin 31960 -> 31592 bytes 12-check_regression/console.log.xz | Bin 3508 -> 3708 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++---------- 20 files changed, 59 insertions(+), 59 deletions(-)