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 971a8df6cb 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards a15770e86c 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 3cec071693 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 468c97b593 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 2d9b423cc5 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 304c568fdf 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 1124ac2331 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards b49008b0c1 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 4299b67c7c 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards efc9f482f8 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 547519d3be 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards d897da5652 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 9f49a62715 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards b1c0a72ab0 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 5c915e6c89 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 530b9bb587 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 15285733c3 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 40f701b4c3 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards a65292c832 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 07e70bc1d0 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards ace86a1247 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 8332454e2d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards e534e27ca1 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 7563337186 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards b5a38af060 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards b7862920f9 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards b311d81b01 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards ecac5b22d0 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 8c1b4b1a8f 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 0ec92cb08e 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 8692727d3d 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 63f0ab9f11 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 33f2925b4a 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 06ddc47b9b 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 6da4c1851e 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards b5e9be92af 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards ef633100d1 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards a8eb45bd2a 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 8f8800e513 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 8f2bc8edd4 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards f985cd03bf 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards c0e69d0ea2 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards de57e9ba27 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 704cddd6d9 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 26c0c4e55e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 3fbbae5eb7 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 162e4dd003 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 232d89a013 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 17d1f82d53 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 8cb55418ea 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 882928dbd3 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards a74900192d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 61d6289ab5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards e88e11cee3 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 7e77f1b450 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 73e75ea61b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards d09b0c1d6b 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 69259366cc 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards b12f127d23 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 7b82f23c87 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 5f76aadbef 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards b357028f30 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards c47406c82b 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards c0275b8502 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 226e3fdf6a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards db401f5b84 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 7e387d6bdb 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards ee25ffd9e7 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards d9f71c6b9d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 394b08b8fb 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 9bf262bb48 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards fc3d09712f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards b49b8171bc 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards d2fec2a821 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 96b865a512 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 10e1680338 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards a9f1328d1c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards fe28954f33 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 522d937f34 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 49bd6a6256 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 2ee4c4dcfd 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 4505ab15ae 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a52d07285f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards be819ac234 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 80c00ed14f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards e67806d6e4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards f70d77183f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 8394b49bad 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards cd7a761d12 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 6e40892754 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards b2f666229d 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c1aaea2fce 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 5edaac9cdb 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 1f6ce6bf4b 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a33a5008f0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards da19b0b948 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards e32d18410d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c808c4eb66 74: onsuccess: 1: Successful build after linux: 44 commits discards e0e17609bc 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9de5675f59 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d4ae3d5a3c 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 23f564f690 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new ac998cb3ff 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0abd94658b 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new fdcfd7d7f0 74: onsuccess: 1: Successful build after linux: 44 commits new 15746d6869 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0f0ce945e9 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 2432c9bf5f 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d259411371 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0a695e31c9 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6f7ecb8019 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new a2e04e48f6 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2b283e188d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 9b5990f395 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 3be4b8d5d9 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 7c8a434250 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 5209b8da0b 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 9fe079e26f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 5e6edae645 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new c1c7197160 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 7cacd3ef22 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 814aa6c3af 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 4c6d2f6660 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new f04cf4394e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new bef782b656 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 18625e4fec 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 73519a5fe4 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new fd60c062b1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 36487a817b 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 66af9ae51d 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 4d850b6201 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 204003676e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 129469d85c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 064821cb51 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 973eec6838 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 6deb58e69d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 9f6dd11420 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 59791593f9 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 5a165b843a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 7fb155379a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 7d46d13ecf 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 370a311299 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2544ccc6e9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new dcf51224da 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new c6f0e47314 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new bc0aec3745 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new fc70b09a3e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 9aba36c783 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 34e663f9f0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new f35633d262 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 5eeba42a86 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 4a06ca72f9 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 9187619251 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 0a970ccd6c 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new b291b8b7c7 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new c3c53fda03 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new cd625e3d08 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 1e521b0b0e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 7d671ce2f4 128: onsuccess: #1723: 1: Success after linux: 12 commits new 9b219152be 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new a5ddc0fb5a 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 774d371867 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 665c21433d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 207cc19a6d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 63d6aadb8c 134: onsuccess: #1730: 1: Success after binutils: 2 commits new c5b8a314c6 135: onsuccess: #1733: 1: Success after binutils: 5 commits new ffc403db87 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 51825e84ab 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 60880d0b21 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 27f6b4365e 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 3955b47926 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 2e82751533 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 9e74300ada 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 24f79c535e 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 94c8e7f952 144: onsuccess: #1743: 1: Success after glibc: 2 commits new f7be42cc30 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new efa80937d1 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new d3489672b2 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 8a2ee44193 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 7df1352501 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new e034ed783d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 97a6d3cd24 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 5a2199ccb6 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new dfdd89c495 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 4a8e77cc9b 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new f7b925e507 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 8c0da347d6 156: onsuccess: #1757: 1: Success after gcc: 4 commits new cfe24469d0 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 67a4413114 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new e301833d56 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 1ae324dd9a 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 077f6a15fe 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 78f7d6762b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 79a80871cc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 010dd149bb 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 3c3e229378 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 3d24db96aa 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 738683ae5d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new f6988d40fc 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new e8254976f4 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 7a03a7b081 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new a4afa66982 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new aa54959c50 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/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 (971a8df6cb) \ 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 1692 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30236 -> 30180 bytes 04-build_abe-stage1/console.log.xz | Bin 91156 -> 90880 bytes 06-build_abe-linux/console.log.xz | Bin 9464 -> 9472 bytes 07-build_abe-glibc/console.log.xz | Bin 234104 -> 234260 bytes 08-build_abe-stage2/console.log.xz | Bin 224724 -> 223284 bytes 09-build_abe-gdb/console.log.xz | Bin 37392 -> 37536 bytes 10-build_abe-qemu/console.log.xz | Bin 30816 -> 30864 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2776 -> 2700 bytes 13-check_regression/console.log.xz | Bin 5728 -> 7764 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 40 + 13-check_regression/results.compare | 39 +- 13-check_regression/results.compare2 | 347 ++++- 13-check_regression/results.regressions | 40 + 14-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 40 + sumfiles/g++.log.xz | Bin 2692600 -> 2662128 bytes sumfiles/g++.sum | 233 +++- sumfiles/gcc.log.xz | Bin 2203752 -> 2207760 bytes sumfiles/gcc.sum | 2206 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 885244 -> 887296 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201296 -> 201372 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422832 -> 426976 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 1945 insertions(+), 1155 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions