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 3c249c1855e 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/ [...] discards 9398e990627 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] discards ed7d02dc4c1 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards b5c008558a5 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards bcc9764e571 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] discards 166e7c1c301 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] discards 9e9d29e1417 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] discards d7eed2fa1e3 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] discards d30249bbd3c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] discards 2735c5b98bf 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] discards 0eb8e751aa4 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] discards 2890e20ea79 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] discards 4fb25cfad90 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] discards 8c17777f1f2 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards fe8830cc86c 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] discards 161f7886b50 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] discards 74e3b68bbf1 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards ac25d691fd9 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards 911adb769df 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards e2e6c25bf31 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards 80b7e191d45 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards 974a722cd85 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards a8ed82903af 212: onsuccess: #2022: 1: Success after linux: 3 commits discards c556ab850d8 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0a6f36d204e 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 59116aa4a4f 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 054977e8f48 208: onsuccess: #2012: 1: Success after linux: 12 commits discards d8e1effbc5e 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 3018959e9b2 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards ee1238a847f 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards b204a2837ed 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards ed275d911ec 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 9d2c5261708 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 4f19531e8b5 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards c9209958329 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 677bfee048d 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards dfa6fe87194 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards a880a0724ff 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 025f6d748e0 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 87d29ca653a 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 7100d3c1d3b 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 255adfbe921 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 5e846d79ad0 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards df6538e93b5 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards b12d6e90365 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards c2b631be6da 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards fb5db6b4584 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards da0c9f60bc6 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards d6b84e97583 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards aca74c3bbe9 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 7635d06b3e6 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 7cd6e48b5bd 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 16be45d6993 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 4b49b13dae2 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 3ba10caa1fc 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards bbd49bd07c2 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 945d33c0d66 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards c66d5bf72ba 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards c88ee8ae1c5 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 815ecdfa1ac 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 088d1e9a34b 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards cd8d30806c1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards ce643d33025 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 97ffc6d1a2a 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 6e3fea96f9f 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 6218d12dd25 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 6ad1b2265f9 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 86ca7b153ee 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 69bf63c6e71 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 3e0f0ef6c05 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 75a93e400c4 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 407539b238d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards df06a0e7ceb 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 98b9312b317 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards bca582b147c 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 2dd70f59557 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards b9b5a927eb4 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 5d66015745c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards af303e1b53a 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 91532ee7cb2 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 760f6e79677 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 9e1687d6f84 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards beff4f2bb18 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 95eb841cca3 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards a32d43403cd 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 80738675b39 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards f7ccae6fed3 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 8e9baae7689 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 1211133727e 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards e8e98ac0302 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 1edeb667003 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards cfc4ae03fd6 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 0ca7d988a77 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards ab77b95704f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 212443d0476 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards fad121a32ff 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 102df47d0db 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 342bf71e857 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e287d95d47e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 8588af01518 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards b89dbc0890b 134: onsuccess: #1730: 1: Success after binutils: 2 commits new aa9a8c2bb4a 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e6e3f113647 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 6508e4398b0 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 86e1e922a04 137: onsuccess: #1736: 1: Success after gcc: 5 commits new b02c8ab6d05 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 615066049d2 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 4c7406bca8d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 4422d30b840 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 343b1fde56a 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new c5153a5fa63 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 35c5eb7f6ab 144: onsuccess: #1743: 1: Success after glibc: 2 commits new c5fa1b443e9 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 155dcf97fed 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 6bc0e6ef169 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 3a58e65f7b2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new b8c832fbb93 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 4b9aa724b9c 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 82dae94bd94 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 67a1b798775 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 597324c7f5d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new e6d6bc31234 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new fa0b6279948 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 8af9ed81cf6 156: onsuccess: #1757: 1: Success after gcc: 4 commits new ed5ee4b624e 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 9776eb86457 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new fb0202a008b 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new fa057e55e44 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 953cb8109e2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 72e80e8026d 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 813b609723e 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 4ab4502d393 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 5b1974b2123 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 83af553ecaa 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 45338047c0d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 7dca3db6c92 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 05894f925e0 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 298bfd3cddc 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 64c1ef820d7 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 75a2fead1e9 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 3d59c0b0e59 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 9853333728c 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new b39dc6fef14 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 4fe68343c93 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 5969eeb68f6 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 8589972a673 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 65d18c7c237 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 36dd5f9d2c8 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new bb17384f9d3 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new ffbdf21f72d 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 11b8ab2f5ca 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 7105cbeac15 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new ce710b38be2 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 6dceab75a80 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new c73c9524556 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 6c687263155 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 7d87255074c 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new ef9a5876f4e 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new b5093a7108e 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new fffb7277422 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 88390872f3f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 8811d68c277 194: onsuccess: #1995: 1: Success after linux: 517 commits new 3d20c0c2ad6 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new da652c59397 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 987c7da930a 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 96a3754cfaa 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 07f9733cbdd 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 77ba9cb7227 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 03c802ab843 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 1c2873b102f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new de67682951b 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 07ff71c688f 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 9584a7468cd 205: onsuccess: #2006: 1: Success after gcc: 3 commits new a7ec4b3d75e 206: onsuccess: #2007: 1: Success after gcc: 2 commits new a010b75456a 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 18f69e0fd65 208: onsuccess: #2012: 1: Success after linux: 12 commits new 5c53c32d6e8 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 2b2355b5b64 210: onsuccess: #2017: 1: Success after binutils: 6 commits new cd994f28ba6 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 290d1a5c90a 212: onsuccess: #2022: 1: Success after linux: 3 commits new dfc690fd791 213: onsuccess: #2024: 1: Success after binutils: 3 commits new fce37e3a134 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new f81407c0890 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new b302e1fcdbb 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new 8172dfc487c 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new 82ad0ebf157 218: onsuccess: #2030: 1: Success after gcc: 5 commits new aacd6ba54a9 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] new 0ae914cd80d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] new 72ffc40f210 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 1cc6decd770 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] new d7cb18a7012 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] new 688d7d46f66 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] new 251d37c43fb 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] new cf2a06ff650 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] new ca250aadce1 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] new 5f2985a3561 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] new d95861022f6 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] new c03dfbb848f 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] new b0c3c020061 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 9700de180e2 232: onsuccess: #2048: 1: Success after glibc: 2 commits new d0ec4b961c9 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] new 9743161198c 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/ [...] new 17385458f0b 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...]
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 (3c249c1855e) \ 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 1788 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31500 -> 31744 bytes 04-build_abe-stage1/console.log.xz | Bin 91216 -> 91436 bytes 06-build_abe-linux/console.log.xz | Bin 10544 -> 9412 bytes 07-build_abe-glibc/console.log.xz | Bin 235452 -> 235368 bytes 08-build_abe-stage2/console.log.xz | Bin 223912 -> 223964 bytes 09-build_abe-gdb/console.log.xz | Bin 38656 -> 38984 bytes 10-build_abe-qemu/console.log.xz | Bin 30240 -> 30256 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2480 -> 2484 bytes 13-check_regression/console.log.xz | Bin 6176 -> 5716 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 57 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- sumfiles/g++.log.xz | Bin 2682976 -> 2655376 bytes sumfiles/g++.sum | 20 +- sumfiles/gcc.log.xz | Bin 2235260 -> 2260612 bytes sumfiles/gcc.sum | 2168 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 887724 -> 894524 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213856 -> 213932 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426616 -> 429408 bytes sumfiles/libstdc++.sum | 8 +- 37 files changed, 1178 insertions(+), 1207 deletions(-)