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_check_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards 5eae4103a0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards b6861b9abc 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards bce1995d5d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards ef9f46305b 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 3041ac44c2 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 42fb8c9d9f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 987f091a7d 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards b066a6c610 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards b271084065 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards d5a169cf67 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 9697ee6d1b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 19aec5b83b 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards b1c0453f90 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 7fe87a1553 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1993ca6ee8 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards e3b246da3f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 8d59c72768 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 29812a6dfb 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 45e652d1cd 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards ab4f89dde1 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards c8476ffac6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards c4699f5db3 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards a5125b35f2 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 21188444dc 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 4394524f60 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards a7bfe53ef6 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 8fd6af54a5 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 65d9cf18b2 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards f20d3fc8da 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 645960fcbb 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards fd164db13a 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 8e5c63bae8 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 71d6fcc008 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 0c7d3f26b9 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 8fbe29e6db 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards a06f5dac78 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 5a7e5ef8ef 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 0d326c7aef 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 76fb649e7c 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 1f61d79c43 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 5d82540f4d 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards eef9ea3336 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 36dccb4050 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 981e052a45 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 43d375796d 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 1b9d1fcb52 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 681cab2a1b 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 7628ded430 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 29c433efef 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards b0c203944e 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 92b4598564 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 1cfb7b7a82 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 5459a88c85 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards b126c50e70 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards aebe272560 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 1d5b531ae5 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 87bba84669 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 6a90ede485 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards bccf42f0c3 208: onsuccess: #2012: 1: Success after linux: 12 commits discards bb15c7b57e 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards e1aaeeb0ce 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 00c2ea882a 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards a714d63d63 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards 712d514ba5 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 9ee1ed6dc3 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards a09407afbf 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 95548b4c59 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards b6085b42ff 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards eb538d287f 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards bce5ea0e7e 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 257ec69396 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards 381aadc47c 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards a7c6cf9602 194: onsuccess: #1995: 1: Success after linux: 517 commits discards f5221e4320 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 731ef4e228 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 48cbb8842d 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 83fd09f069 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 114dfbda43 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards fc3b6243da 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards c4369707dc 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards bc9fac029f 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards a2c5ac1f9f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 45d13beeb5 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards fea85f8cfd 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 766ca8f66f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards cc6eb15f02 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 057bf08a43 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 8ec1bc5596 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards d249e39ff7 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 5745b6e8a7 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 363ea4d666 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 9e01891abe 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 84b1854e7e 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 15ba1f6698 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 45c2ad4217 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 9638a67fc6 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 116c3883a0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 2743250bfc 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards a397bd64f4 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 1cc29c4037 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 8dadbe0efd 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 13e9257048 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new a9516559fe 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new e5902245e6 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new b87a9848ee 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new bc345c449c 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new be81b18790 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new d8b13a68fb 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 9765cce09f 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new b8b5a3a5d7 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new ff33ca1cb1 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new c60474b68f 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 30ca5daf4e 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 41ee8bee4c 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 7977406581 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new f9676d8520 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 31e0e6e932 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new f6cbf06549 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new c507fe7e8b 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 97f9fe93b4 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 03e7f88a25 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new 1b17c323f6 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new bef82e5995 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 4be36f4567 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 66a7e7cb86 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 4cc9bce3ff 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new 045ea8b830 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new b3f81c1f56 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 953e20fb8f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new a9d6c8993e 194: onsuccess: #1995: 1: Success after linux: 517 commits new f7714d9c64 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new fac2bd3b62 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new e1b7212bd9 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new ad493b071a 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 336f042f10 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 37e23f833d 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 269036e19f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new b968ccddf3 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new 3a56240856 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new c060b57c08 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new f0f253f447 205: onsuccess: #2006: 1: Success after gcc: 3 commits new de9898d406 206: onsuccess: #2007: 1: Success after gcc: 2 commits new b9997285c1 207: onsuccess: #2010: 1: Success after gcc: 4 commits new e6a9cc15ba 208: onsuccess: #2012: 1: Success after linux: 12 commits new eee1f8b23d 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 80fa7b4d6f 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 6511e4f295 211: onsuccess: #2020: 1: Success after binutils: 10 commits new df87ccf30f 212: onsuccess: #2022: 1: Success after linux: 3 commits new 4d2981d246 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 5e0a5436b1 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 75933781c2 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 81d7c71e25 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 2b1add5b74 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 2d4a3ac586 218: onsuccess: #2030: 1: Success after gcc: 5 commits new d005b87781 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 060b63fa7b 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 4546b94780 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new cb9e599446 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 4ceb3eb46f 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new fd046fc6b3 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 67e0764675 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 2b3505f8d8 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 971edcef76 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 5466af668a 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 3d5061f1b8 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new c56edf6417 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 9182f61408 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 05f105f3c5 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 7afdc88a96 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new ad3c0ac206 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 9107be7028 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new e938e69e85 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new ea9d753c47 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new e0d4a587d5 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new bcbfdc6623 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 63275c61e0 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new e819fa7e8a 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 703b6cf0ed 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new f777f21c4f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new b9feec0a34 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 42dca08beb 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 066afe3807 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 826effc9de 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 7f6f40ac04 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new d479617187 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 5e55b1ad1a 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 14abef313a 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new f50c674c6d 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 16cfbc018f 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 87d9b685d1 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 4d9acd5922 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 0c5ea63496 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 8bf8bbb8c5 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 7de1e4a17c 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new f9b025fd5f 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 7c117f1bd2 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new d29af94752 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 798ca2b1d9 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 4fe9fa8472 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new f3117d9dfc 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 356c0d6893 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new ebfd0b941f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 29d0a92f44 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...]
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 (5eae4103a0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1772 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 32152 -> 32884 bytes 04-build_abe-stage1/console.log.xz | Bin 92208 -> 92876 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 236940 -> 237052 bytes 08-build_abe-stage2/console.log.xz | Bin 225984 -> 224952 bytes 09-build_abe-gdb/console.log.xz | Bin 40048 -> 39208 bytes 10-build_abe-qemu/console.log.xz | Bin 31092 -> 31524 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2532 -> 2608 bytes 13-check_regression/console.log.xz | Bin 5988 -> 6148 bytes 13-check_regression/results.compare2 | 73 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2651156 -> 2659920 bytes sumfiles/g++.sum | 27 +- sumfiles/gcc.log.xz | Bin 2253172 -> 2273828 bytes sumfiles/gcc.sum | 2286 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 914704 -> 896768 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213896 -> 214032 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428848 -> 442660 bytes sumfiles/libstdc++.sum | 2 +- 36 files changed, 1283 insertions(+), 1279 deletions(-)