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 6dec658a29 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards bb9b9c8ad8 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 37581f6b22 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards aff89d8b8e 305: force: #2006: 7: Success after gdb: 2 commits discards b15e0801af 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 741e6e1832 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 7ebbd24df3 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards 2f76eeb626 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 27106ed522 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 0fac5a9c9a 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 1f4115c57a 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards e58266e83f 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 2b5491119e 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 579de8dcb0 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards 6463a4a8cd 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 84bd3a8eb6 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 672c1c86b9 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards 659dd3b093 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards b45c9f6f24 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 5aaa86885c 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 60f4b98f6c 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards b3abcd4b59 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards 6fb542353f 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 181a8b4e53 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards fc2695d91e 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards f9b93caa36 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 037f6cc1e9 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards 51f2a7e502 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards e3b817faeb 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards 2a75c0574e 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards 442c068585 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards c1dd69b74a 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards fabed6ee5b 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 53f1c5dedb 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards f22e3dbc32 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards 25a68f7137 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards 5699edb2bc 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 806fd094c2 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards a0a04c8f35 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards 148b5722e5 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 87296be4e4 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 025fd71d47 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 3d86f280be 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards e6b88bf172 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 7a28afc1a9 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards c776efb59e 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards 5a0015ee1e 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 723f786d72 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards aa7f389a90 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards e9f15a8153 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 7d4e141296 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 2a8d54d75a 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 178a9b8c25 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 1e9b7974bc 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 60550ebe75 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards c00220ee4f 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards fe2a90be99 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards 241c1cceb0 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 145a2d0919 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards d28eb6d773 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards 460e9f0f29 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards df4c8a6c11 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards e02ecb0a4d 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards 748c9f7fdb 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards ba4dc0c6fc 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards 104caafd38 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards f23031ad2c 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 17f0b3cf40 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards ce0030fb7d 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards 982596b8ef 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards beddd166ba 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards c1efaa5d54 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards 0866c9e33e 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 41aeed74fe 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards 11d8fa6c5f 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 25cd18f87e 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards c029f0897e 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 1e06a2b626 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards a1a1a5a73c 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards d3b62186f6 229: force: #1926: 7: Success after gcc: 7 commits discards 2179b02590 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards 26478bf9b7 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 7bf175f48e 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 5852504b30 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards b89c7bc19c 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards c5a74fb3ff 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards 843f937dff 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards 68fcaab81a 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards e8fd724eb0 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards d8b3c343a1 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards 86a50aeab4 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards 985db2018a 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards 3cfa98ba61 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards 79c14aa55d 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards d5031a2d74 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards 23876094d2 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 35c49b6639 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards 7957ceb3a7 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards 17564e0368 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 845fdfa23c 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards d74711d863 208: onsuccess: #1865: 7: Success after linux: 12 commits new 0c96868540 208: onsuccess: #1865: 7: Success after linux: 12 commits new 3a530dc595 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new 1d0280d58f 210: onsuccess: #1868: 7: Success after binutils: 7 commits new 2836e5fea3 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new 49fe1bfb04 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new 07737db02f 213: onsuccess: #1889: 7: Success after gcc: 5 commits new cac3ed2841 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new a395dd6d80 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new 09c2b64c83 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 1ad60c72ff 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new 0110628b18 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new 141a0ae9b9 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new 407ab40921 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new 63a185fb5c 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new 2b3ff62228 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new 3f383f22d4 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new b818cae2a2 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new 5c668043b9 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new df74b99018 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new 49b67defb5 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 8aa593c132 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 4cd16c3b8f 229: force: #1926: 7: Success after gcc: 7 commits new 3406987f09 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 7eac393b02 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 3f875aa982 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new f986ddadb6 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new e49da849ca 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 97b3780821 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new a2a6fd5cb4 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new eede1a0ca4 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new 9ef3e42876 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new 690e09fef7 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new 386de31a56 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new 7e9541f6b5 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new 5482c73d2c 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new a6162bae1d 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 382632c57e 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new b0cd5a8af8 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new bd50e4dfa4 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 6fee62e763 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new c22f3ad80b 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 46e06b25ab 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 36833f68f8 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 3489a6a1d5 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new c1cad1680b 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new a946626fd1 253: onsuccess: #1950: 7: Success after glibc: 2 commits new 11b87ac205 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new cab127a749 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 8659fb97fe 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new bd4a21d5df 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new 6e45848069 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 9d3869bb22 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 7ca7c9cab6 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new 700da30756 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new e4fae1644c 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 72c34fd3dd 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new ae7cfd5171 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 20897be681 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 52945da89e 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new edcf3aab52 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new 533c261597 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new 4b9b46b91c 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new cfe6a95545 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new e840221c15 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new a031685202 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 99ae72aaf0 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new e7e42ab6b8 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 061b6086f3 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new 128bc540af 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new bdbfb93ab4 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 7aa8446dfb 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new 7daea71cff 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new bdeab5132c 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new 47f68b5237 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new cd673cca22 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new 15b21ffeeb 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 373da45d9f 284: onsuccess: #1981: 7: Success after gcc: 2 commits new 45177bd644 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 043cf807a8 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new eb0cd73bfd 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new fd804829f3 288: onsuccess: #1985: 7: Success after gcc: 17 commits new abcbd19f29 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new ff595f2598 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new a0164d3448 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 79a13d20ff 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new 4d98a8f27b 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new 42e6336e46 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 706fad589f 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new d18dbbb370 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new aecf434b60 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new 9a7977d7de 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 2fa53c060b 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new 26ee78198b 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new a54bf2fa51 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new d036af9fe0 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new dffc06aebb 303: onsuccess: #2001: 7: Success after binutils: 4 commits new b9fdb0ca9f 304: onsuccess: #2002: 7: Success after gcc: 4 commits new aebc3ba60e 305: force: #2006: 7: Success after gdb: 2 commits new bec7ac43d4 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new e5981b949e 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new d36d024b4b 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 411ecea84c 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/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 (6dec658a29) \ 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 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 32240 -> 32512 bytes 05-build_abe-stage1/console.log.xz | Bin 73556 -> 73592 bytes 07-build_abe-linux/console.log.xz | Bin 8868 -> 8872 bytes 08-build_abe-glibc/console.log.xz | Bin 244808 -> 245688 bytes 09-build_abe-stage2/console.log.xz | Bin 204728 -> 204636 bytes 10-build_abe-gdb/console.log.xz | Bin 39828 -> 40120 bytes 11-build_abe-qemu/console.log.xz | Bin 31812 -> 31644 bytes 12-check_regression/console.log.xz | Bin 4556 -> 3876 bytes 12-check_regression/mail-body.txt | 4 ++- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++---------- 21 files changed, 67 insertions(+), 63 deletions(-)