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 cd08ca76ac 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 31906d9238 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 6982fd25fb 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 2f68fd0264 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 2dc361986b 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 0209b07c1b 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 04d0c65c0a 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards d7aa788692 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards e11cae23ed 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 44c0dcd143 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards f9e7753f79 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards f8adc0a41c 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards a2d3674161 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards dc5a1311cf 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards 4ed4c78c9d 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards a154a5f71d 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 9dcd9fafbc 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 18b9702b5d 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 0b2a384dc5 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 3a8d76576a 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards f3ecfc42aa 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards 096569accd 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 83755cd6d0 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards 98995dc850 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards 158d632479 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards 2350e765f8 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards ab867ba94a 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards a9171d8c2e 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards fef93d6337 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 0e7038bd30 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards c6f06d7962 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 430e503823 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards e984f478ca 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 55153bb0d8 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 40e31198f7 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards 1078de499d 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards ade08e820e 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 002b24f64d 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards d3e7136beb 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 2611bfe80a 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 59e2504a31 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 911d4ba93a 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards c87cebd372 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 5397981dba 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 43083e8b63 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 7a0c7d9c17 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 321fb10f9e 305: force: #2006: 7: Success after gdb: 2 commits discards d917ad1908 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 3105b5ac76 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards b176883226 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards ea7756c516 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 75813ae1db 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 1189ec8d2d 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 1238cec190 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards a16507e633 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 5bc67bdd6a 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 65e3fe21b5 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards 5b4250f881 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 4d23fea5eb 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 48866b1c4c 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards 0767a92673 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 833e00bcc0 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 86d9a65c45 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 6a1d8f38e0 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards 1f90d4f41d 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards f64e002b92 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 8b9d319753 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards 4cb37d6ec5 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards 1ca9b6b55a 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 95514932e3 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards 97912ff2b6 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards 1d92065628 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards 45794291bc 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards aef827672f 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards d63a599351 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards e82bbf8f27 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 8afe5148d0 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards f6ecbc39b5 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards dd60a42c59 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards aa14d35306 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 9ea630ba0e 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards 1ecd4aad43 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards 35bea84b23 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards f6371d5ba5 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards f765f6a4fa 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 1e40366a1b 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards e05ac83fbb 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards cbb29e47ae 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards 8cea32ec14 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards d91927cff1 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 68c402905c 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards 97bae7dd7f 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 26d3384fbc 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 7abebb9334 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 0dfefc1a90 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards f61db1ac24 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 59033afe05 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards d9448fbe7d 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards dfcf839ced 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards 71977aab4c 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards f785a431bd 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new a6e6d6104d 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new aaf320f921 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new a5aea05220 253: onsuccess: #1950: 7: Success after glibc: 2 commits new 337dd9035e 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new f81f80fb71 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 247be38e91 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new f6d465b53f 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new 2314aef2af 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new bebf672f06 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 71026bfe05 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new ad3ad15504 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 1daa5c7d74 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 2b91f28194 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 53e6727c9d 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 52548a8118 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new a939434ef7 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new dd0207ecaf 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new 5d2451aec0 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new c80cf769c7 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new d408cc33ff 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 62389177a8 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new 5b8a99c49c 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 6faa6de059 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 72ae50e60b 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 9650224831 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new 918e802f1e 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new fd496b2714 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 85c6b0e4c1 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new b8646878df 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 0971ad4173 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new 680c5ffa47 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 606ef0eb14 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new 4ccae1ec9a 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 459df8f43d 284: onsuccess: #1981: 7: Success after gcc: 2 commits new ebfd9c804c 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 30fff7cf78 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 9d1c9b8832 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new 23dbc2a30d 288: onsuccess: #1985: 7: Success after gcc: 17 commits new 4f984bb0dc 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new eb4dbb3074 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new e53c29f87c 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 92ab0f39d5 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new c45366daf0 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new 0731b3e102 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new d1b62d88e5 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new 3bec9bba25 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new b70e39abf7 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new bce9940dfa 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 01cb8f4ca4 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new f39c02fd0f 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new bc3e45e6ed 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new a6ef618352 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 9e6854a6ba 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 65e99fb84d 304: onsuccess: #2002: 7: Success after gcc: 4 commits new e0f4bcd00b 305: force: #2006: 7: Success after gdb: 2 commits new f83f25f680 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 0e3ecdd1d5 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new 6cd552cff2 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 9358dc2c60 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 524be41879 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new e4c25d7155 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new b528f7e5e5 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new b2ec1c7121 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 30eb014b4d 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 6bd4286e46 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new a517cad27f 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new 62daf8af32 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 63eb66efa9 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new d5ffc8c1cb 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 2b1fab7491 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new ec507e1641 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 034f09a0c9 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new 5f2e8efb4e 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new cebffb76c3 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 7cdfffff8c 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new 4a581fc7be 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 58e930278e 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 3eb78fc2bf 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 03f3d7d2ec 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new caa1b5ed18 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 13142f9b36 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 15ffbc1b64 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 816c532514 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 63d5d5276a 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new a9a47efdfa 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 4bead7a4dd 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 8c0d8f67c4 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new b490a8c3bd 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new 8da18d673b 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 9c702ff8fa 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new d1723f51ac 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new 81f3e668c9 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 0ec62bcbb4 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 39370a5936 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new c0a983eae2 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 48559f44bc 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 344759b9c4 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new b1137b59c8 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new 71427a313e 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new ea53130307 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new 8b2eacba11 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 502b416666 352: onsuccess: #2053: 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 (cd08ca76ac) \ 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 31968 -> 31824 bytes 05-build_abe-stage1/console.log.xz | Bin 74268 -> 73072 bytes 07-build_abe-linux/console.log.xz | Bin 9188 -> 8580 bytes 08-build_abe-glibc/console.log.xz | Bin 247712 -> 244348 bytes 09-build_abe-stage2/console.log.xz | Bin 208908 -> 204544 bytes 10-build_abe-gdb/console.log.xz | Bin 39660 -> 39060 bytes 11-build_abe-qemu/console.log.xz | Bin 31384 -> 31904 bytes 12-check_regression/console.log.xz | Bin 4824 -> 5136 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 ++++++++++++------------ 22 files changed, 67 insertions(+), 67 deletions(-)