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-arm in repository toolchain/ci/base-artifacts.
discards 465497132f 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards f763dc34f8 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards 47a54738c7 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards 9e2374b886 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards 4ddb8b1fe0 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards 33e44ffd56 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards 2c7f38dc74 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards 309a9e80f4 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 65d64712b7 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards fd9cf18d8c 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards 5698a99d01 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards d3b800b445 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 6ce70c31a5 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 491c459672 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 797cc07e6d 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 379ad7d981 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards ac2a621b0f 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards eb6692698b 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards a9e1bffec9 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 418b9b01ba 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 84794f9200 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 3900e6ff1e 321: force: #2055: 7: Success after gdb: 2 commits discards ee9e9d4142 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 20468b3f65 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards bf293a5d23 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards 9cf25af31e 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards 81fc560658 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 4b3988c8d6 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 59defc9e2a 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 4756ccdd90 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards 665b747041 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards e1eb154f9a 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards 86d23e8e98 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 5efd2de368 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 5f765ca416 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 82b7e12fe9 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 6c233f02bc 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards 3aa74d9c3d 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards ac0ed1869f 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards 6ff1b74020 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards a9a077c08a 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards 4ed060fdef 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards a7c5681ba9 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards e425cd3159 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards bf04fe9b4c 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards 3f64614fba 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards 066bda411a 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards 78261dc5de 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards 4e974cd1c3 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards c2aa81aee9 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards 60211bbd4c 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards 8544b14483 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards 8f89cc6e26 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards e5098c0199 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards ddd6a527b9 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards f21ca833ac 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards a6d318a5c5 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards 25c752e1d6 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards da9104703f 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards 4e1e23fd52 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 1c39361bac 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards b802178686 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards f4f1cbd86f 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards e798827c65 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards 8e2596b41a 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 731a52a612 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 8ba27a7131 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards 9c70e167b9 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards 4b4ccc093b 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards eeba1d394b 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards 4a394f449d 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards e64340e683 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards 52120027c4 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 230036ff93 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards ffac3c1b16 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards 41f2d34ca4 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 9ec5708b3d 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards 1e7698e459 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards 51fbbd6890 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards 9a60ec1318 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards 1eaef989fd 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards 6cd18fda65 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] discards 5ab1f079c5 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] discards 78bb412742 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] discards f0bcf4b068 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] discards d40c86c1e5 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards d4baf63be7 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] discards ab0599c5d3 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] discards bef5f86c5a 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] discards b7d5db0159 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] discards 9e2daf0f37 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] discards 2fb6620d99 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] discards 0ba6c88a1c 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] discards 833e7e3b25 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] discards d3e94a1a24 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] discards 6cc9da2df0 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] discards a489a7f326 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] discards 0d997ebe37 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] discards fc367a3ae8 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 519bd92e5c 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] discards 68b37c2886 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] new 0ad20e66c4 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] new a9cae9d05d 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] new eb1cca72ba 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new f9d57e23c8 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] new 68736bc9c6 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] new 04259dbfa5 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] new 708e28ea4f 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] new 80faf5b270 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] new c56305a0ca 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] new e48f7969b1 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] new 266e260f9d 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] new b9e628cc00 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] new bdaaea3fa2 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new 1ce1420b50 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] new f2009d0fc6 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] new 26c9153068 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new be042cd164 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] new 511de033a9 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] new 09514d5a12 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] new 87cf1db251 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] new d1017f3632 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new 12183e4465 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new 8a651dceb5 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new cb9c8acafa 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new 1e736d066f 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new 7aa085f993 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new 0e2c8d880e 268: onsuccess: #1997: 7: Success after glibc: 2 commits new badf93d8dc 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new 8d5dcd4dd5 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 1e781aa1c0 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new 781cb0d052 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new 944c6bfcb6 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new b4ee86490d 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 814e36deb0 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new 669cb58698 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new 5d84585680 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new 2dc5625dd1 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new c849d5c027 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new c0bff3a5a1 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 604ea772e5 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new d25e623aa7 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new b8db79ae18 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new d22090d53e 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new 531147dd06 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new 1d474054c6 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new 51b0f0e866 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new 97bda02b22 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new 431c530ec0 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new e78e99929c 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new bafdceabf2 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new 600a3fb5de 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new 5ee65a0918 293: onsuccess: #2022: 7: Success after gcc: 2 commits new bd090ff2db 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 661b545b6c 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new cb7f1131fe 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new 5e638fe01b 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new a953fa2124 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new b183156529 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new 59c15d3465 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new 4c874d0490 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 3f0cd79a86 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new 54d980fd43 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new b7f731316b 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new cdaef70f27 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 59a706925a 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new f86c251694 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new 12f557e64c 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 5242ba8c58 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new 245a8f5e24 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new a3402838b2 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 1aa4a590eb 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new 3c5bed9228 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new ca1622c88c 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 132f7ce870 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new f497102eaf 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new cdad80ccb3 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 11362618b0 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new 5a73e3f2d5 319: onsuccess: #2049: 7: Success after binutils: 4 commits new b7a0d61118 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 4c048b6884 321: force: #2055: 7: Success after gdb: 2 commits new 2cd36cdad5 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 335bd17ca8 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new c5650d15b7 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 7bd7ef9d5d 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new 93ef2f26bd 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 651404fc46 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 19df97723d 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new cb21322e7b 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 1ede503e15 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new b6247e3a64 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 2dc43ed3e8 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new d7f8284aeb 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new e425e949a7 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new d41df29521 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 6ee33ff193 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 077de1c6f3 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new bdb578789f 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new b8e6b8a83c 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 4af8dfc495 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 4d2b882496 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new 10bfa98097 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new 3a2cbf19e7 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...]
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 (465497132f) \ 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 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 32248 -> 31756 bytes 05-build_abe-stage1/console.log.xz | Bin 92000 -> 91956 bytes 07-build_abe-linux/console.log.xz | Bin 8880 -> 8840 bytes 08-build_abe-glibc/console.log.xz | Bin 236896 -> 236224 bytes 09-build_abe-stage2/console.log.xz | Bin 229468 -> 228140 bytes 10-build_abe-gdb/console.log.xz | Bin 39724 -> 39084 bytes 11-build_abe-qemu/console.log.xz | Bin 31524 -> 31160 bytes 12-check_regression/console.log.xz | Bin 3576 -> 4416 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/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 ++++++++++----------- 20 files changed, 61 insertions(+), 61 deletions(-)