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 97ab9bce02 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards c3fe9d0799 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards f05e628d94 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards dee0a9c2fb 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 10c0ec32ca 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 00b8dc1a11 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 1fe78b409f 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 7a0e848e09 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 3c2bb93d74 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 5ab1eb4efe 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 7ae67bd551 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 6923aa66ac 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 9f9f8f329c 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards a2ea5e4fba 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards ef10100313 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards fde3f2cd83 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards d0a3d82e4f 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards fa1825d43f 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 170829a0a8 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 56932c306e 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 2bdbe5bc40 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 42d78fde31 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 2c6c764fbc 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 3b330c517d 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 0eb51f67f9 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 1a5f7d46fa 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 807911f141 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards b231a2dc61 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards e02987729c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards f23c8286bf 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 091ac2879d 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 26cd83a286 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 053a731492 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards cf7cad01c3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards ff4cebac88 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 66300ce8f8 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 528c581f40 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards f33452129c 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 0dd83fec66 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 0c0f8a51e7 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 04fcc78a47 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards b49cbd5a23 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 7d0d3598f6 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards c641063bd1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 329fd816f7 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards e30569182e 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards e916478d1c 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards cad5fa92ff 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards ec76aa340a 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 506d5e8308 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 34f4f43fd3 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards a24aee8014 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 8ba9464b95 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards e148dbe106 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 6c1a78b072 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 7386b9cc34 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 16becabc7c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 297c3e7dbc 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards fd749a1c87 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 92266848e3 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards af57c4d647 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 1db4421c0f 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 7e934638e7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards b6bbc85cf8 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards cfacef26c0 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 5d7086e8ec 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards f514115359 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards b4be81e9ce 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 04acb3d9f9 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards f7f0488e11 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards f0f7b350ed 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards b6e9e6f449 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 93d3c60281 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards fd2dfd280b 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards d4e933d5b6 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 48b05941d2 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 7c9d1cfde7 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 1a5dfccc52 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 95aab173eb 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 9a1bf2caa0 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 05bbd70fdd 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b0e0d02424 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards cc5dc0097b 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 2bc8e0662e 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards cd37938e22 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 1861b0f757 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards f920c8c864 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards d7f2e5bc01 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 7998b9566c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 7988ef76bd 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 3b41afcbac 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards bebee7fb2a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards ba223ea38c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 24974b4a3c 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ab28d27f60 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 637421a803 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 7e24b95199 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards df90d3d5fa 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 369d9a36aa 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards e463f67c40 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 6dec740b56 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new f10f903550 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 3fb7d1b5b9 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 5bfea0a10f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new ff20b7cfe9 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new abd95a9790 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 2b173f7040 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new f598b476d3 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new cf5578e0f4 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 335a93a12e 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 8eeb7f0bd2 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 342341147b 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 0bf0117629 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 56e8f34002 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new f55a9d3925 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 3145a2bfce 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 797cf2f60a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 911f9f7d7c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 33db991f46 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 462ff3571e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new d068fc9154 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new a0d415bc28 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 6891631c86 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 3471580f43 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 26c26ec8f1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 4e54a79003 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new ec1bdb6c2b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new e41690cb25 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 275b3b1e3a 110: onsuccess: #1703: 1: Success after gcc: 6 commits new b1d21c9d3e 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 9afc4d5608 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new d975d0f797 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new fb6abcf04b 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 19713af704 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 0601044586 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new ba21b87add 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 8cd642d5d7 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new ed342cf2ed 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new c1fbe97e9b 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 044adaa118 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 2cc55d43b1 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 071ca01990 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new fba26b82ca 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new a05fe4fda7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new cf1ffd9eec 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 7b2d1cb23c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 9e647949fc 128: onsuccess: #1723: 1: Success after linux: 12 commits new 1e735279f1 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 25b5cf051f 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 8024d2c98f 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new b412df9fc2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b06eb6b632 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 21e4bae774 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 786ecad909 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 059cfedb92 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new f243a84296 137: onsuccess: #1736: 1: Success after gcc: 5 commits new c2daa70328 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 667175f5a6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 1a771217e1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 5aa47fe80f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 44ae529cbe 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 5613919015 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 8d07ee173e 144: onsuccess: #1743: 1: Success after glibc: 2 commits new e3c2534258 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 4905574105 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 3136dc715a 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 73a86557a0 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 1eb9b3ef56 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 6361e1efb0 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new ca546a9331 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new a51a8bff34 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 2da17f2ea4 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 84dddab114 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 7f6ff8d367 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 71aabb924c 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 774d68df29 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new f11e2829c4 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 3f7c2b2144 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 5ae9a23ca0 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new b4755d8eff 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new bc0a01db37 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 446eaa9df4 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 8bf2d462a1 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 65106759d0 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 8cb45f43fa 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new f693047cae 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 7b3dafc870 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 0267ca6c93 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new f721bb3dac 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 583f7152b0 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new e040fcdeee 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new e459805fa8 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 09393572b1 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 3c47223f4a 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new e99c5a11b4 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 1cf76b9326 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 034ac6579a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 600bb45fd4 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 4b46c225cf 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new a3151a516e 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 3df650c9eb 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 045ec2db5c 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 19a925090f 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...]
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 (97ab9bce02) \ 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 1708 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30080 -> 30244 bytes 04-build_abe-stage1/console.log.xz | Bin 91020 -> 91360 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 235328 -> 235968 bytes 08-build_abe-stage2/console.log.xz | Bin 223236 -> 223692 bytes 09-build_abe-gdb/console.log.xz | Bin 37236 -> 37664 bytes 10-build_abe-qemu/console.log.xz | Bin 30920 -> 30740 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2816 -> 2532 bytes 13-check_regression/console.log.xz | Bin 13344 -> 6204 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 14 +- 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 42 +- 13-check_regression/results.compare2 | 1242 +-------------- 13-check_regression/results.regressions | 42 +- 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 42 +- sumfiles/g++.log.xz | Bin 2685100 -> 2686596 bytes sumfiles/g++.sum | 155 +- sumfiles/gcc.log.xz | Bin 2209384 -> 2244384 bytes sumfiles/gcc.sum | 2648 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 891624 -> 884104 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212980 -> 213044 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432752 -> 425908 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 1700 insertions(+), 2819 deletions(-)