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 0f6dbe2c21e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] discards eefaf339d06 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 55f93e3ee75 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 77a06c231bc 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] discards 9f06a338ca6 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] discards 4c546b8f43b 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] discards 1c3b9cfa75f 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] discards 3230c03e418 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] discards a719945bf0f 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] discards 0a5296ec95b 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] discards 71617c30966 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] discards 4df18b7942e 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] discards 2eded9e1f45 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 72f302c662d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] discards d5ebc7acae4 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] discards 9672a3ad74a 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 0cbd052828e 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards 2d3cdaefe0f 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards f359baccd6f 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards 86d457bf751 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards 5bad395c985 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 49b6467ee08 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 9f938ce2376 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards c063ce430c1 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 4278f90ca78 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 97a3910b8fe 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 9d66b05e00c 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards b412a0b894b 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 963f3ffebde 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards ff1cb8cf1af 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 0daa4686882 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 680e4cb7035 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 7a87f91dd84 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 31c0047df38 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 72ec1a3ac98 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 42c1bcf0e2a 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 7a682ad0e2a 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 73e2b9fd7f6 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 6412c94d042 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 6dcf58dcc53 194: onsuccess: #1995: 1: Success after linux: 517 commits discards b3ae3158a2f 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 900eb06a991 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards d8872d05b20 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 4868e2efc5c 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards e9e4a49c49e 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards c440373384a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 3d8a8ba7678 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards ec248e05edd 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 8b5261ba870 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 11177f017aa 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards a21ff3818fb 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards edb8d1d14c7 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 25dc5fa4e7d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 134e1ef8723 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards f161bf55588 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards fe735edcefd 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 636ca7c37f2 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 1187235e143 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards db0a796e2a2 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards e793e777683 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards d4d399c3ac4 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards e29a436bd89 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 2c8949a1851 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 558359c3a52 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 92130bcaccb 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards e31a443fe4b 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 932c1a92e0c 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards fd9b4687874 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 0d45034ce0f 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards cd8f72f3dc6 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 57acf1ecb02 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards ec40ce0f199 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards f11e0653447 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards ad8d6353cc6 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 88d412923b8 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards e57736c061f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards efcaa3e58d5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 6a08b0d1af4 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 5b6b0c0b38d 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 80e895d2b57 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 8c9d22d08df 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards c18248d44c6 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 06000736387 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 1b708a38e96 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 05e858ff6c2 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 8df310b5ea7 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 1fc4347929e 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 8841424a7b6 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 42b270a64cc 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards f2ef28859f9 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 371b058f5df 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 0ca708ae574 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 19d0f873793 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 46e80cd0d14 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 650384baa02 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 19127a80d95 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards e617b4dc8a3 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 5b3d4a836fe 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards e7591c4539e 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 2528dedf649 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 37838700b01 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 910eebf9a05 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new b89dbc0890b 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 8588af01518 135: onsuccess: #1733: 1: Success after binutils: 5 commits new e287d95d47e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 342bf71e857 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 102df47d0db 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new fad121a32ff 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 212443d0476 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new ab77b95704f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 0ca7d988a77 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new cfc4ae03fd6 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 1edeb667003 144: onsuccess: #1743: 1: Success after glibc: 2 commits new e8e98ac0302 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 1211133727e 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 8e9baae7689 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new f7ccae6fed3 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 80738675b39 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new a32d43403cd 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 95eb841cca3 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new beff4f2bb18 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 9e1687d6f84 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 760f6e79677 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 91532ee7cb2 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new af303e1b53a 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 5d66015745c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new b9b5a927eb4 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 2dd70f59557 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new bca582b147c 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 98b9312b317 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new df06a0e7ceb 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 407539b238d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 75a93e400c4 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 3e0f0ef6c05 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 69bf63c6e71 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 86ca7b153ee 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 6ad1b2265f9 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 6218d12dd25 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 6e3fea96f9f 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 97ffc6d1a2a 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new ce643d33025 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new cd8d30806c1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 088d1e9a34b 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 815ecdfa1ac 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new c88ee8ae1c5 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new c66d5bf72ba 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 945d33c0d66 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new bbd49bd07c2 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 3ba10caa1fc 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 4b49b13dae2 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 16be45d6993 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 7cd6e48b5bd 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 7635d06b3e6 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new aca74c3bbe9 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new d6b84e97583 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new da0c9f60bc6 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new fb5db6b4584 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new c2b631be6da 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new b12d6e90365 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new df6538e93b5 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new 5e846d79ad0 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 255adfbe921 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 7100d3c1d3b 194: onsuccess: #1995: 1: Success after linux: 517 commits new 87d29ca653a 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 025f6d748e0 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new a880a0724ff 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new dfa6fe87194 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 677bfee048d 199: onsuccess: #2000: 1: Success after gcc: 5 commits new c9209958329 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 4f19531e8b5 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 9d2c5261708 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new ed275d911ec 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new b204a2837ed 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new ee1238a847f 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 3018959e9b2 206: onsuccess: #2007: 1: Success after gcc: 2 commits new d8e1effbc5e 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 054977e8f48 208: onsuccess: #2012: 1: Success after linux: 12 commits new 59116aa4a4f 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 0a6f36d204e 210: onsuccess: #2017: 1: Success after binutils: 6 commits new c556ab850d8 211: onsuccess: #2020: 1: Success after binutils: 10 commits new a8ed82903af 212: onsuccess: #2022: 1: Success after linux: 3 commits new 974a722cd85 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 80b7e191d45 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new e2e6c25bf31 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new 911adb769df 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new ac25d691fd9 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new 74e3b68bbf1 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 161f7886b50 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] new fe8830cc86c 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] new 8c17777f1f2 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 4fb25cfad90 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] new 2890e20ea79 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] new 0eb8e751aa4 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] new 2735c5b98bf 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] new d30249bbd3c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] new d7eed2fa1e3 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] new 9e9d29e1417 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] new 166e7c1c301 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] new bcc9764e571 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] new b5c008558a5 231: onsuccess: #2047: 1: Success after gcc: 4 commits new ed7d02dc4c1 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 9398e990627 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] new 3c249c1855e 234: onsuccess: #2050: 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 (0f6dbe2c21e) \ 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 1776 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31584 -> 31500 bytes 04-build_abe-stage1/console.log.xz | Bin 91488 -> 91216 bytes 06-build_abe-linux/console.log.xz | Bin 10260 -> 10544 bytes 07-build_abe-glibc/console.log.xz | Bin 235208 -> 235452 bytes 08-build_abe-stage2/console.log.xz | Bin 224904 -> 223912 bytes 09-build_abe-gdb/console.log.xz | Bin 38860 -> 38656 bytes 10-build_abe-qemu/console.log.xz | Bin 30188 -> 30240 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2840 -> 2480 bytes 13-check_regression/console.log.xz | Bin 6224 -> 6176 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 54 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2682784 -> 2682976 bytes sumfiles/g++.sum | 31 +- sumfiles/gcc.log.xz | Bin 2232904 -> 2235260 bytes sumfiles/gcc.sum | 1688 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 892932 -> 887724 bytes sumfiles/gfortran.sum | 16 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214080 -> 213856 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427868 -> 426616 bytes sumfiles/libstdc++.sum | 8 +- 39 files changed, 979 insertions(+), 1008 deletions(-)