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 3bcf08b941 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 956bd0abc7 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards aa9b87786b 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 9096407d01 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards a78f085e3e 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 4153e7c1e2 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 26a8faad09 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 0b185b74ec 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards fe616fc4d6 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 92b938fbad 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 26e8f7a01f 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards dff54f254b 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 07f017b4de 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 04def5cca4 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 568c132a6d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards a974c58d9d 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 3828bcde5d 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards d0d606652b 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 67fbf88174 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards fd1fec5684 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 52ae68418c 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 49fd5a0d4b 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards c41fa10c6f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 834b114d6a 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards dd60201f2a 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 1df48b6443 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 78d6185291 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 1e480a88dd 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 5d9de47824 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards eeb90086dc 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 9a29f22b33 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 3e66679316 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards d314b5c443 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards d923a67155 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards bf5c1ef0c2 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 7bcb7ee385 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 109addbe45 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 00a5bb3322 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards db608ec552 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 1a5140b013 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards caa0478c96 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards beed967c94 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 56813e5f60 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 280dd0fdca 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 6e6735ec95 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 2130cf21f9 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 99683c515f 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 09b05a2abd 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 5f33e08f46 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 8a8d586443 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards c3a1532caf 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 3ac7c26044 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards b414d74fbc 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards ae9ec28fb8 128: onsuccess: #1723: 1: Success after linux: 12 commits discards f61abff177 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4219e274c9 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards a9c836250c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards c18c343e70 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 64864be451 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 24fcb7ad32 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 6231805228 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 52e8d0a011 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 4a14dc3121 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 21671c29bc 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b63740a51c 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 87b279ca9d 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards b07115ec56 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 2265a2787e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 3fedace879 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards a2314cb6e5 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 4b3bce3f1b 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 1bb1d2c2a9 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 3701b1c0ad 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 9de088ce92 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 2625c9c057 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards e7f6b661b9 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 566572e4c5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards da5e5fc78c 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards f89577ac12 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards f84c132732 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 7667b61051 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 1ea43e443f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 2649341f41 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards c6212c770f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 0a841cf206 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 0bbd2d4f11 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 5c017e2571 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 3031849972 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards e0e4b8c977 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b18757c2dd 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards e0fd3f4af2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards c7a0229301 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9dd62fcb3b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards fca91ce39f 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards f8ebe40b73 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 87b33c5ce9 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 13e3dc4c07 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards acc082d4ae 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 28a7668e68 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 47960c1fe5 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8b211ed1db 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 6826e464f6 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 56aa6080c7 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 07cc51a722 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 1c6178896c 84: onsuccess: 1: Success after gcc/glibc: 9 commits new a036470a5c 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 9eabfc4869 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 161e800fb5 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 169ed2fa84 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 81afeb6237 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 57d6edc4a2 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new cb21440ee3 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new da4e94e333 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 99ddfdf19a 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 6bc3fc4257 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 3d4099767d 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new e0746d9d21 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 8af9c376b5 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new c73b9c27d1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new f8244cd400 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 45aaa5ab68 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 45e1e01af2 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 76958964df 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 88636d97f5 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new c3000a3385 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 7df48fc9d2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 9ac4c686ae 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 9091061803 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 89d1ebebf5 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 75ac4a4d77 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new a06ad33106 110: onsuccess: #1703: 1: Success after gcc: 6 commits new d3e11bbfef 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 6b75269e24 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 3981e405bf 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 2f7ec5dc44 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new e1cf60d7e2 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 60f31406af 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 2c923f3c10 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 42126365cf 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 541f0bcec8 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 2981567c98 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 4acd4c0512 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 54ec9aeada 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new f95d8e53c4 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 2fd5ce8199 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new bd58463b6e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 7a8832d9c2 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new cef759c9a5 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 877ad8f515 128: onsuccess: #1723: 1: Success after linux: 12 commits new a733d44600 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 04b8f66958 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new c07f066221 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 754bb530fe 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b03dca0fab 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new c61f53e993 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 88e0da437a 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 4c5afab622 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 1da9d0cc23 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 311e2fd07c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new b93c9d81f2 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 306f69e941 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new fb627a3e37 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new f602a02af6 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 04920cb7b1 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new fb1b616b8a 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 40f7e44e5d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 4b0bd273c6 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 29f0b28473 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new b1a18a8677 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new a31be1066c 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new bf29ca8837 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 99da15cc31 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new daea07c200 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 5618c26f95 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 1055baf283 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 76c70f4b63 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 2c50d16b90 156: onsuccess: #1757: 1: Success after gcc: 4 commits new fc07d3bb4b 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new fa204c4e87 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 1708ae9b31 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 2ac481002b 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 02603e4019 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 213c6235d3 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 102512eec4 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new ebc993b6cf 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 567ecc3ad8 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new c2b9517298 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 18d52ea155 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new a378ef1921 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 34806a0f27 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new f01f21258a 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new d1546afdb9 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 91c44b5723 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new b3a65d8a9e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 9d1af8a991 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 936154bf96 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 3eb2397652 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 12d1e573b0 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 100478a8a6 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 6b5c95e00f 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new d7cb64f800 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new de23f543a5 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new fe7c6d45bd 182: onsuccess: #1860: 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 (3bcf08b941) \ 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 1704 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30564 -> 30260 bytes 04-build_abe-stage1/console.log.xz | Bin 91224 -> 91524 bytes 06-build_abe-linux/console.log.xz | Bin 8504 -> 8708 bytes 07-build_abe-glibc/console.log.xz | Bin 234296 -> 233996 bytes 08-build_abe-stage2/console.log.xz | Bin 226312 -> 224676 bytes 09-build_abe-gdb/console.log.xz | Bin 37524 -> 37516 bytes 10-build_abe-qemu/console.log.xz | Bin 31416 -> 31360 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3016 -> 2624 bytes 13-check_regression/console.log.xz | Bin 13712 -> 6612 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 12 - 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 190 +-- 13-check_regression/results.compare2 | 1142 +-------------- 13-check_regression/results.regressions | 101 -- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 101 -- sumfiles/g++.log.xz | Bin 2706284 -> 2699748 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 2218828 -> 2223304 bytes sumfiles/gcc.sum | 2348 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 883288 -> 885392 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 203340 -> 203456 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425192 -> 423576 bytes sumfiles/libstdc++.sum | 8 +- 44 files changed, 1315 insertions(+), 3022 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions