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 bfe144f0c6 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 113ed7fe8c 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards f5c918b29d 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 684c9a55b2 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 0f15fc6de5 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 9768689e22 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 1e190d4c37 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 1410ac4484 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 38bce71973 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 7f228098aa 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards ed7f877692 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 96a274df2f 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards d88d20ddfc 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards ed826ebd1a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards ae623de739 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 39e4b2b0b7 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 386ce8f059 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 7071746389 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 99f6ae0ee0 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards c666824d74 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 32862c6842 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 4f89e702af 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards e9ff06ba93 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards a9a3197f93 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 5c30d6b0b2 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 038641f4d4 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 0d7e09e6ff 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 4cf961313d 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards b3077e3cb1 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 66b7c7aa1f 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards b93952db2a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 1b15406610 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards f00424cfe9 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards ba656c67c8 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 1f8299d025 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 61e3e78d45 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards e13742903f 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards e9d0c86c1a 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 659ad97401 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 7ebca8d818 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 608bb7955b 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards a41a9a82a6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards f0a5373de7 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 8054099f97 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards eabb989b09 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 31111be268 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 521ec5f719 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 448fe64883 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 9e05822e5f 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 60f25db50f 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 9d8a276883 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards dd6777f0f4 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 8c81d19190 128: onsuccess: #1723: 1: Success after linux: 12 commits discards f8b775068d 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 2fccd7e967 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 02d9158c24 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 784fea2b05 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 165e0cab50 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 5c0133e4da 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards b67de20a7d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards dac93b6244 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards fed4e9e9e3 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards d25b4b2259 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 890769fe3a 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 40da94eede 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards e6b83fbefe 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 385c6f7a83 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 3ebff6b5ad 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 6c0709cfcc 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 003b61b56b 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3c28a9009f 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 4cfba03e98 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards bae93d18d9 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 1977ed936a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards d41af3fa3b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards e3670404f6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 309ebfa802 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 199b457ffb 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 77e3be79df 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 0b484e5d45 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 7e90e903d2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 40f933d29c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards f9bee7b467 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 2653fe930d 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 153929645a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards cd02eb1499 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 7b4a3c5d37 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 30118c886f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 84a12dd923 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards bc122e8a2b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 737d42f2e0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 06c00f5f68 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 818349cd5e 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 525af3e504 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 6dcffb80aa 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards b9b920f551 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 6b9269b5c1 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards a060d4f0a3 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards ebf22ede50 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 45b41e02c3 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards a31776a641 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 4067209260 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 8b211ed1db 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 47960c1fe5 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 28a7668e68 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new acc082d4ae 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 13e3dc4c07 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 87b33c5ce9 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new f8ebe40b73 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new fca91ce39f 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 9dd62fcb3b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c7a0229301 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e0fd3f4af2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b18757c2dd 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new e0e4b8c977 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 3031849972 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 5c017e2571 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 0bbd2d4f11 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 0a841cf206 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new c6212c770f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 2649341f41 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 1ea43e443f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 7667b61051 101: onsuccess: #1693: 1: Success after glibc: 14 commits new f84c132732 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new f89577ac12 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new da5e5fc78c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 566572e4c5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new e7f6b661b9 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 2625c9c057 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 9de088ce92 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 3701b1c0ad 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 1bb1d2c2a9 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 4b3bce3f1b 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new a2314cb6e5 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 3fedace879 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 2265a2787e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new b07115ec56 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 87b279ca9d 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b63740a51c 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 21671c29bc 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 4a14dc3121 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 52e8d0a011 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 6231805228 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 24fcb7ad32 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 64864be451 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new c18c343e70 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new a9c836250c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 4219e274c9 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new f61abff177 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new ae9ec28fb8 128: onsuccess: #1723: 1: Success after linux: 12 commits new b414d74fbc 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 3ac7c26044 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new c3a1532caf 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 8a8d586443 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 5f33e08f46 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 09b05a2abd 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 99683c515f 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 2130cf21f9 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 6e6735ec95 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 280dd0fdca 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 56813e5f60 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new beed967c94 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new caa0478c96 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 1a5140b013 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new db608ec552 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 00a5bb3322 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 109addbe45 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 7bcb7ee385 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new bf5c1ef0c2 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new d923a67155 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new d314b5c443 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 3e66679316 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 9a29f22b33 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new eeb90086dc 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 5d9de47824 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 1e480a88dd 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 78d6185291 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 1df48b6443 156: onsuccess: #1757: 1: Success after gcc: 4 commits new dd60201f2a 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 834b114d6a 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new c41fa10c6f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 49fd5a0d4b 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 52ae68418c 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new fd1fec5684 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 67fbf88174 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new d0d606652b 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 3828bcde5d 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new a974c58d9d 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 568c132a6d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 04def5cca4 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 07f017b4de 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new dff54f254b 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 26e8f7a01f 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 92b938fbad 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new fe616fc4d6 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 0b185b74ec 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 26a8faad09 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 4153e7c1e2 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new a78f085e3e 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 9096407d01 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new aa9b87786b 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 956bd0abc7 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 3bcf08b941 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...]
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 (bfe144f0c6) \ 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 1712 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30248 -> 30564 bytes 04-build_abe-stage1/console.log.xz | Bin 90772 -> 91224 bytes 06-build_abe-linux/console.log.xz | Bin 8780 -> 8504 bytes 07-build_abe-glibc/console.log.xz | Bin 233732 -> 234296 bytes 08-build_abe-stage2/console.log.xz | Bin 224764 -> 226312 bytes 09-build_abe-gdb/console.log.xz | Bin 37396 -> 37524 bytes 10-build_abe-qemu/console.log.xz | Bin 31768 -> 31416 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2444 -> 3016 bytes 13-check_regression/console.log.xz | Bin 15008 -> 13712 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 178 +- 13-check_regression/mail-body.txt | 150 +- 13-check_regression/results.compare | 67 +- 13-check_regression/results.compare2 | 2416 ++++++++++-------------- 13-check_regression/results.regressions | 52 +- 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 | 152 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 52 +- sumfiles/g++.log.xz | Bin 2674904 -> 2706284 bytes sumfiles/g++.sum | 417 ++++- sumfiles/gcc.log.xz | Bin 2249308 -> 2218828 bytes sumfiles/gcc.sum | 3053 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 889516 -> 883288 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 203400 -> 203340 bytes sumfiles/libgomp.sum | 214 +-- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433720 -> 425192 bytes sumfiles/libstdc++.sum | 14 +- 45 files changed, 3439 insertions(+), 3478 deletions(-)