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 7bbc0b863098 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: [...] discards 7def9d7bc2d5 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: [...] discards a0c51649bb3a 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/q [...] discards 196f09f2b373 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards 0dc4cab7b447 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: [...] discards 1edd3ef8192a 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/q [...] discards 2454fb2b0519 259: onsuccess: #1988: 7: Success after binutils/gcc/linux [...] discards 93a981ad0ee6 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/q [...] discards 77f2967ec143 257: onsuccess: #1986: 7: Success after binutils/gcc/linux [...] discards 379219102a62 256: onsuccess: #1985: 7: Success after binutils/gcc/linux [...] discards d8d5ea0d0599 255: onsuccess: #1984: 7: Success after binutils/gcc/linux [...] discards 6694bdb67e93 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/q [...] discards 48acf05ad125 253: onsuccess: #1982: 7: Success after basepoints/gcc-13- [...] discards 26c011dbae1b 252: onsuccess: #1981: 7: Success after binutils/gcc/linux [...] discards 7937c656310d 251: onsuccess: #1980: 7: Success after binutils/gcc/linux [...] discards f16f9829bbf3 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: [...] discards a687c1d34eff 249: onsuccess: #1978: 7: Success after binutils/gcc/linux [...] discards b2b893855156 248: onsuccess: #1977: 7: Success after binutils/gcc/linux [...] discards 1cd74e0f4c04 247: onsuccess: #1976: 7: Success after binutils/gcc/linux [...] discards c6a443a73b88 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: [...] discards ddccf5f06af7 245: onsuccess: #1974: 7: Success after binutils/linux/gdb [...] discards 204c415bf923 244: onsuccess: #1973: 7: Success after binutils/gcc/linux [...] discards 861c05918645 243: onsuccess: #1972: 7: Success after binutils/gcc/linux [...] discards 13d15b028dab 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc [...] discards c50247a2643d 241: onsuccess: #1970: 7: Success after binutils/gcc/linux [...] discards 03f0e549c39a 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits discards 3dbc0324a5c4 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: [...] discards b821876873ea 238: onsuccess: #1967: 7: Success after binutils/gcc/linux [...] discards 833c18a21810 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits discards 25ca28b4a672 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: [...] discards 7b9c1a16bdc2 235: onsuccess: #1964: 7: Success after binutils/linux/gli [...] discards 97ddb862b859 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: [...] discards 17e3d5c66863 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards d6646a80c0c5 232: onsuccess: #1961: 7: Success after binutils/gcc/linux [...] discards fb7829db473b 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc [...] discards e84f6a335212 230: onsuccess: #1958: 7: Success after binutils/gcc/linux [...] discards 8a64c248a610 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc [...] discards ee339b8c4255 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards ef6cb10f2180 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards eec712b05093 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc [...] discards 33cede974414 225: onsuccess: #1953: 7: Success after binutils/gcc/linux [...] discards 7d28a92d5dc9 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/q [...] discards 9470f36d4984 223: onsuccess: #1951: 3: Success after binutils/gcc/linux [...] discards 3c001f023801 222: onsuccess: #1950: 3: Success after basepoints/gcc-13- [...] discards 4952ae95f24a 221: force: #1949: 3: Failure after basepoints/gcc-13-4492 [...] discards 96066fa0e3b4 220: force: #1948: 5: Success after gcc: 4 commits discards 43929dca9fb7 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards 22512c063aed 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards 86eabdcf554c 217: force: #1942: 5: Failure after gdb-12-branchpoint-294 [...] discards db9239efb9a0 216: onsuccess: #1940: 7: Success after linux: 12 commits discards b698d5e14484 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards 136410007df4 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards e32edb89176f 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards abf5f829de66 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards 4bbbfc6ac34c 211: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] discards ee954509c655 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: [...] discards 7597e5a24d44 209: onsuccess: #1931: 7: Success after binutils/gcc/linux [...] discards 2ee50b41e0ab 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 16426c8a9451 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: [...] discards 0ce44707765b 206: onsuccess: #1927: 7: Success after binutils/gcc/linux [...] discards a158542d202b 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: [...] discards f10db6ae5ff7 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: [...] discards da7847b1a84f 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: [...] discards 382ce5b3e574 202: onsuccess: #1923: 7: Success after binutils/gcc/linux [...] discards 365e698cd19c 201: onsuccess: #1905: 7: Success after binutils/gcc/linux [...] discards 666da7e17d5f 200: onsuccess: #1899: 7: Success after binutils/gcc/linux [...] discards be099b9aefd6 199: onsuccess: #1881: 7: Success after binutils/gcc/linux [...] discards 34a2060276a1 198: onsuccess: #1878: 7: Success after binutils/gcc/linux [...] discards c71a76b837cb 197: onsuccess: #1856: 4: Success after binutils/gcc/linux [...] discards 62f7a8aca246 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 31a4f3dee1d3 195: force: #1854: 4: Failure after basepoints/gcc-13-3918 [...] discards d510f38f7fcc 194: force: #1853: 7: Success after gcc: 26 commits discards 6cf535e0e838 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint [...] discards d98205562afe 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 00eb820b70f9 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards c434bbbb3056 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 144d91715727 189: onsuccess: #1829: 7: Success after binutils/gcc/linux [...] discards ad0335ec5217 188: onsuccess: #1827: 7: Success after binutils/gcc/linux [...] discards 6fea82b0fe03 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc [...] discards 993454578c0f 186: onsuccess: #1825: 7: Success after binutils/gcc/linux [...] discards 1a58519796ba 185: onsuccess: #1815: 7: Success after binutils/gcc/linux [...] discards c472870f8593 184: onsuccess: #1777: 7: Success after binutils/gcc/linux [...] discards 66087cabe815 183: onsuccess: #1776: 7: Success after binutils/gcc/linux [...] discards 283334cbf813 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: [...] discards 8681f4d970c4 181: onsuccess: #1773: 7: Success after binutils/gcc/linux [...] discards 38978bb06d7b 180: onsuccess: #1724: 7: Success after binutils/gcc/linux [...] discards 122593f0dd65 179: onsuccess: #1696: 7: Success after binutils/gcc/linux [...] discards 79882ed38a06 178: onsuccess: #1694: 7: Success after binutils/gcc/linux [...] discards 4dd5ded41269 177: onsuccess: #1692: 7: Success after binutils/gcc/linux [...] discards 53b8951777ea 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc [...] discards e58aa774b1cf 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: [...] discards 43efd7144e20 174: onsuccess: #1689: 7: Success after binutils/gcc/linux [...] discards 846ce3325bc1 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qe [...] discards 1e395bfe7a4a 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards d0682d71b353 171: onsuccess: #1686: 7: Success after binutils/gcc/linux [...] discards 107d30993c6d 170: onsuccess: #1685: 7: Success after binutils/gcc/linux [...] discards e8dc6f5b970b 169: onsuccess: #1684: 7: Success after binutils/gcc/linux [...] discards d04a642a5743 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: [...] discards 4bff8a0bbae8 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 91e391564e6e 166: onsuccess: #1681: 7: Success after binutils/gcc/linux [...] discards ab6f41df1367 165: onsuccess: #1680: 7: Success after binutils/gcc/linux [...] new 5d788706ee2a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux [...] new acaf619a17ff 166: onsuccess: #1681: 7: Success after binutils/gcc/linux [...] new 3d02b2cd291e 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 2cda5b1c19d2 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: [...] new 6ea9e0df5881 169: onsuccess: #1684: 7: Success after binutils/gcc/linux [...] new ab88bf6460a2 170: onsuccess: #1685: 7: Success after binutils/gcc/linux [...] new 12d8173785d7 171: onsuccess: #1686: 7: Success after binutils/gcc/linux [...] new 72ab4c88ff19 172: onsuccess: #1687: 7: Success after gcc: 11 commits new cf5fc70866b5 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qe [...] new 3147748f7bbc 174: onsuccess: #1689: 7: Success after binutils/gcc/linux [...] new 5d310e049c48 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: [...] new ed52809e43f3 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc [...] new 4ad41072e044 177: onsuccess: #1692: 7: Success after binutils/gcc/linux [...] new 3954e22671ab 178: onsuccess: #1694: 7: Success after binutils/gcc/linux [...] new 1b76f73e7eda 179: onsuccess: #1696: 7: Success after binutils/gcc/linux [...] new 1b82228b8b5d 180: onsuccess: #1724: 7: Success after binutils/gcc/linux [...] new 498eae893d52 181: onsuccess: #1773: 7: Success after binutils/gcc/linux [...] new 5c0eb4cce99d 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: [...] new 4330dd349240 183: onsuccess: #1776: 7: Success after binutils/gcc/linux [...] new 50e28e2d5c72 184: onsuccess: #1777: 7: Success after binutils/gcc/linux [...] new b6bd63fc9f54 185: onsuccess: #1815: 7: Success after binutils/gcc/linux [...] new 72af5b03ed7b 186: onsuccess: #1825: 7: Success after binutils/gcc/linux [...] new d6e7336c27cf 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc [...] new 37f112283d5f 188: onsuccess: #1827: 7: Success after binutils/gcc/linux [...] new a85e67e34107 189: onsuccess: #1829: 7: Success after binutils/gcc/linux [...] new 451066993910 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 79182ac87511 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 80c19177ab57 192: onsuccess: #1848: 7: Success after linux: 213 commits new 7fc345124e2f 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint [...] new cfdbef0a1d2b 194: force: #1853: 7: Success after gcc: 26 commits new ea151f06be1a 195: force: #1854: 4: Failure after basepoints/gcc-13-3918 [...] new c7d9d7ddf3a0 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 79a56eb39532 197: onsuccess: #1856: 4: Success after binutils/gcc/linux [...] new 529101cddadb 198: onsuccess: #1878: 7: Success after binutils/gcc/linux [...] new 31d4175f8911 199: onsuccess: #1881: 7: Success after binutils/gcc/linux [...] new 8a0f67e07602 200: onsuccess: #1899: 7: Success after binutils/gcc/linux [...] new c893eed84a34 201: onsuccess: #1905: 7: Success after binutils/gcc/linux [...] new 7afceb1f9b5d 202: onsuccess: #1923: 7: Success after binutils/gcc/linux [...] new 9238edc7039a 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: [...] new 116d3ccad51f 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: [...] new f8d637578bf0 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: [...] new 600a7b66bb6c 206: onsuccess: #1927: 7: Success after binutils/gcc/linux [...] new ca121aa78560 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: [...] new 46fafbde09dc 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new fb4e32b6761e 209: onsuccess: #1931: 7: Success after binutils/gcc/linux [...] new c844cad8ee6c 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: [...] new 2b26d3378c48 211: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] new 44ababd32d54 212: onsuccess: #1934: 7: Success after gcc: 3 commits new 8c97e6c833a2 213: onsuccess: #1935: 7: Success after gcc: 2 commits new fe78bab4a901 214: onsuccess: #1937: 7: Success after binutils: 4 commits new c6b6676c250f 215: onsuccess: #1938: 7: Success after gcc: 4 commits new 646fe5f6b184 216: onsuccess: #1940: 7: Success after linux: 12 commits new 784c9b6ccff1 217: force: #1942: 5: Failure after gdb-12-branchpoint-294 [...] new 304aa9f6024e 218: onsuccess: #1943: 5: Success after gdb: 3 commits new 925e3d07077e 219: onsuccess: #1945: 5: Success after binutils: 8 commits new 1c655de78773 220: force: #1948: 5: Success after gcc: 4 commits new ab7727f0d909 221: force: #1949: 3: Failure after basepoints/gcc-13-4492 [...] new b47663732e86 222: onsuccess: #1950: 3: Success after basepoints/gcc-13- [...] new 671356379653 223: onsuccess: #1951: 3: Success after binutils/gcc/linux [...] new 8289c681dfaf 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/q [...] new 683d68d5ce5e 225: onsuccess: #1953: 7: Success after binutils/gcc/linux [...] new a0b249bdc3a6 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc [...] new c71ee95560e8 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new 7404f0f9a92c 228: onsuccess: #1956: 7: Success after gcc: 5 commits new 0efcdac31778 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc [...] new f7684c7913f7 230: onsuccess: #1958: 7: Success after binutils/gcc/linux [...] new 74a542e3b136 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc [...] new 3e2141fb88de 232: onsuccess: #1961: 7: Success after binutils/gcc/linux [...] new 848e54a2c480 233: onsuccess: #1962: 7: Success after gcc: 6 commits new 0ba34e26bd7f 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: [...] new 0900dd5a61f0 235: onsuccess: #1964: 7: Success after binutils/linux/gli [...] new 9cee29775a3b 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: [...] new 8a1d813d6f01 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits new dd96ea1eeae9 238: onsuccess: #1967: 7: Success after binutils/gcc/linux [...] new 02cb71e167f2 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: [...] new 397f6a06a003 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits new 1f1b96f8b9cb 241: onsuccess: #1970: 7: Success after binutils/gcc/linux [...] new f3f8ad7f1e1d 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc [...] new 27389a57e679 243: onsuccess: #1972: 7: Success after binutils/gcc/linux [...] new ec2b201c924c 244: onsuccess: #1973: 7: Success after binutils/gcc/linux [...] new f161a9d6d7ee 245: onsuccess: #1974: 7: Success after binutils/linux/gdb [...] new 125206c959d1 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: [...] new 8be8af7a76b2 247: onsuccess: #1976: 7: Success after binutils/gcc/linux [...] new 3208fef572a9 248: onsuccess: #1977: 7: Success after binutils/gcc/linux [...] new 091413969299 249: onsuccess: #1978: 7: Success after binutils/gcc/linux [...] new ce129a59601f 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: [...] new 3ff63b4d23ab 251: onsuccess: #1980: 7: Success after binutils/gcc/linux [...] new ce28f640e484 252: onsuccess: #1981: 7: Success after binutils/gcc/linux [...] new d10e559dd073 253: onsuccess: #1982: 7: Success after basepoints/gcc-13- [...] new 87ed6c9339a8 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/q [...] new 7fa5a5fb8815 255: onsuccess: #1984: 7: Success after binutils/gcc/linux [...] new 29060d3ee30b 256: onsuccess: #1985: 7: Success after binutils/gcc/linux [...] new 15de4e79b832 257: onsuccess: #1986: 7: Success after binutils/gcc/linux [...] new c9d51846995e 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/q [...] new e77fc970df4a 259: onsuccess: #1988: 7: Success after binutils/gcc/linux [...] new ba9c1f972666 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/q [...] new a07040b20f6d 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: [...] new 6eb66bf2fc41 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new 861858a433d5 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/q [...] new d292ae458867 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: [...] new 245804cbd109 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: [...] new 6f1fb7a3f374 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4a [...]

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 (7bbc0b863098) \ 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 1716 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2788 bytes 04-build_abe-binutils/console.log.xz | Bin 32128 -> 31956 bytes 05-build_abe-stage1/console.log.xz | Bin 91300 -> 92092 bytes 07-build_abe-linux/console.log.xz | Bin 8612 -> 8628 bytes 08-build_abe-glibc/console.log.xz | Bin 235964 -> 236804 bytes 09-build_abe-stage2/console.log.xz | Bin 225844 -> 226616 bytes 10-build_abe-gdb/console.log.xz | Bin 39332 -> 39684 bytes 11-build_abe-qemu/console.log.xz | Bin 31208 -> 31376 bytes 12-check_regression/console.log.xz | Bin 3500 -> 3196 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++------ 17 files changed, 51 insertions(+), 51 deletions(-)