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 e6385fc37a2 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/ [...] discards 0527156e9b4 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 1 [...] discards 7a88be66bed 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 5e0b6be9e0c 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/ [...] discards 3634c8b1071 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] discards cffc3f5867e 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 843fa1e6714 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards a9c2e8a5e90 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] discards 671aa659b58 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] discards 464cb93aaf4 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] discards 040246724dc 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] discards 11265adb51f 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] discards cd6c3058e43 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] discards e7021ceb033 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] discards 54570d4fc92 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] discards 72614e6ba15 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] discards 63b9a216f9a 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 1a2d122840e 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] discards dded171d6f1 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] discards 1eecf42e5ef 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 3f6c8d18fdd 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards f70d350cff1 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards 11d6572d7d8 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards 2c35e3f97c6 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards 47ffa116300 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 16d19886d3a 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 7b78cf6ed0d 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 51299533f2f 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 7f530cc7cf5 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 0a6789c08e2 208: onsuccess: #2012: 1: Success after linux: 12 commits discards e36c9e80ae0 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards fac3f2b6352 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards b380c858fa7 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards b91e6f1ae78 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards f4130a7fefc 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 527d91c58f4 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 65a76a3f002 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 51ae73f8632 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards ba74afe507d 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 52fc6ef6581 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards ed02ee76b3c 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards bbd7ac255a1 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 5c355126293 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 1f4ac7ff475 194: onsuccess: #1995: 1: Success after linux: 517 commits discards bd919994629 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 2e798033ecb 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 82c1e27d142 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 9567533ff91 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 931f0c4e1e9 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards ed045b47c3b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 514f74f5c54 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards b7fc25acd6c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards df0e898f712 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 8fda19a4d9f 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 5bceb5adaf9 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 96b3af6d4a8 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 4f67337fe43 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 274169f1896 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards d65e5ee74ec 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 35f7c63fd2e 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 10ef097e373 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 0fe1bc08162 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards dbfe11ac638 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 5dd5954b75d 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards e2549bfe92a 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 08a251fcb75 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 30df7091fff 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards c2db7416c8e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards c997e20e619 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards d98e60f4cb7 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards d78da0b9357 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 0c246e50a05 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 09365e7797e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 49b94b418dd 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards efec416c1b3 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 9d9da670416 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards b4803aa95ef 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 249b2d6df30 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards a70cded9dfb 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards f6806a18fdb 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards d7e1823b693 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 879583b5b73 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 8d746f66b2c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 863c0292ab6 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards b94cabd2d16 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards e581f208c93 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards c39ee07208e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards f7b7a41e3aa 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards d82d3bd35b7 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 7fb39e1f801 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 9a3bf5ca36a 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 00d7aaf9171 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 8c515b6951b 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards b5337252287 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 9a810371ad8 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards f0310793aca 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 5ba51de262e 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 234956fff04 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards ffe04b63d0d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 67654b39ebc 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 8677347b951 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 20c124ddd70 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a26ddaa90b8 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new a507581e501 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 949d555ce52 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 091c0026c28 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 8ae78026c7f 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 48a4001fdc1 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 85cc36d8879 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 88eb07ce9a7 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new d1a1d0baaa5 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new d40c693b50a 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new aa82c85ce70 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 24ba9470c23 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 59de924d20a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new b642dfc544e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 8d015214f40 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new d3ca902c137 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 6bccba23fd3 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new c024e237f34 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 1e8d1649b9a 156: onsuccess: #1757: 1: Success after gcc: 4 commits new fe049f1043f 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new dee72123745 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 519215b47ae 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new eba855803ad 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 031fb321071 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 55c75f19523 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new c496f6bc49e 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new d317781fa08 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new e3124b28a9f 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 4e88a5075c2 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new b976ab45c77 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 36293e2a9fe 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new ab9d597f36f 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 0c3bdfe62a7 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 8c4958bec67 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 092aeac7504 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 68954086afb 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new ba0ebca596b 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 3f21b6814c4 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new b9828a595dd 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 6f15c70d827 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 2812e785e78 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 119269de0c7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 32918a72804 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 309c07b89c4 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new c7dccfbbf1c 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new da83104bd9b 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new fbb55c054b0 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new f5b530a7fda 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 9621f14d867 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 34f9360699c 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new e942345b53e 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 61e69189ca4 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 46366ced6d8 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new eed046b3f83 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new f92e9085b40 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 520e0caa84c 193: onsuccess: #1992: 1: Success after binutils: 151 commits new afdaf70353c 194: onsuccess: #1995: 1: Success after linux: 517 commits new f26d66ff0aa 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 42a2329e6aa 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new cff418dd938 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 1e6d6fb100f 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 7a70a37c991 199: onsuccess: #2000: 1: Success after gcc: 5 commits new e748b0b1a39 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 18823586b47 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 3ab0d3177ea 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 7ff6e50d4f6 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 120bb881b7f 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 3c0b2ac4ee6 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 80d7572dfd4 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 529f55e3f2c 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 5b5f0f2a79b 208: onsuccess: #2012: 1: Success after linux: 12 commits new 25a527c32c4 209: onsuccess: #2014: 1: Success after binutils: 12 commits new da178a9ec17 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 63e3abbf16f 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 0ea450c8e5f 212: onsuccess: #2022: 1: Success after linux: 3 commits new fa6427ca9b9 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 80ba5465893 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new e4aa28e35f8 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new cac0ac659a6 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new 0f00fe34b93 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new ceab5882371 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 0cd52f8f1b2 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] new 2368a0e9952 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] new b43b914998e 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new f176b49a2de 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] new add0107d65b 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] new 41fccbf36d9 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] new d4f6b25637a 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] new 4bd5129621a 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] new afe45c29b45 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] new 4f527e3b4ac 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] new ddeb696f042 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] new ab3e6d5d80a 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] new 6df1684fb3f 231: onsuccess: #2047: 1: Success after gcc: 4 commits new b20c8a2356d 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 5a83ad1e388 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] new 7ce24eca2aa 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/ [...] new b35fdf325ed 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new feb8347eade 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 1 [...] new 68c54ebd321 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/ [...] new c3972017ab2 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/ [...]

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 (e6385fc37a2) \ 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 1800 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32592 -> 31436 bytes 04-build_abe-stage1/console.log.xz | Bin 91780 -> 91244 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9932 -> 11952 bytes 07-build_abe-glibc/console.log.xz | Bin 236916 -> 235032 bytes 08-build_abe-stage2/console.log.xz | Bin 225476 -> 225228 bytes 09-build_abe-gdb/console.log.xz | Bin 40012 -> 38612 bytes 10-build_abe-qemu/console.log.xz | Bin 30652 -> 30600 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2668 -> 2508 bytes 13-check_regression/console.log.xz | Bin 6760 -> 7152 bytes 13-check_regression/results.compare | 22 +- 13-check_regression/results.compare2 | 93 +- 14-update_baseline/console.log | 70 +- 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 +- sumfiles/g++.log.xz | Bin 2661524 -> 2656748 bytes sumfiles/g++.sum | 118 +- sumfiles/gcc.log.xz | Bin 2233296 -> 2268012 bytes sumfiles/gcc.sum | 2565 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892256 -> 896988 bytes sumfiles/gfortran.sum | 49 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213860 -> 213992 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 434428 -> 431692 bytes sumfiles/libstdc++.sum | 16 +- 41 files changed, 1528 insertions(+), 1497 deletions(-)