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 60bb53297c 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards de44ba03b7 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards e52b9522b7 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 32d29656cf 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards b1cf0198f2 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 8a2c469e5c 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 6fc48a9271 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 89773d8d73 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards aa058b623e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 8d4e848842 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 04ead036d2 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 72fdf01650 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards ad7c3da900 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 215a8aa88f 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 6df3cc4b70 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 31cba41788 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards ffa0d1cb90 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 2ad13493cb 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 7502319321 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 0f320480b6 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards ff5d8d7f01 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 6aec4775d6 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards d0b7acf47c 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 4d0b870d2e 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards cbd6eff422 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 876855a664 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 8d52b570ee 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 04f3a445d1 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 5ff6d44404 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 479417addc 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 635316cf36 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 5ebf02e2ab 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 8911f5cd4d 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 7acc4af76c 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 268b732cda 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards d2f4fd649d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 3c49fad6f0 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 86901b8d37 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards a1953f437d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 3631f89dbc 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 2838063836 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 7faa148b7a 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards b500f06997 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards fce18e2a49 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards b38f7d4025 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 7ff092c8d1 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards cc6d4826a4 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 497db27e0b 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 0bc345ff68 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards a7a7abeed5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6b9c1f0a1a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards ba97b0dea7 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4874542264 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 0cd4d1b486 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 8e884bc840 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 33d9d9ba45 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards c9cbf3d96e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards e0c3957668 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 4223a104c4 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 0175052d88 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards b8baaf0c01 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards c77c1ae611 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 53728e1d3b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards b0d5615bb2 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 9374387a16 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards b6267c741e 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 15b2d2684a 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards d108af3d3c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 7a735311e3 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards db433af896 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 74b04c903e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 5eb9ee3951 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 521113f81d 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 1c83a70708 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards c4495eee32 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 2f190c0a4a 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards be5c60caa1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards ad7f012cca 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 11f06694eb 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 3f2d6bf411 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 4516601746 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards e08382dc80 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards b8ee2709e6 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards f3325145b3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 15d46d53ee 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 091700eb10 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 2222ee41f0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards f431785e9b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 60d4501322 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 06a0a751ee 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2ad20b8440 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 283c6df767 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards a55f226f61 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 2da3c33f3a 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 492427026b 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards d66d729704 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 15517619fb 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 5eacbfdc0a 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c25357848d 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards ccb5b0737f 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7e18a4e224 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cf19a82a0b 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1dc742794b 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a9ac07227e 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new ab3a8d843c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new fb1d51f724 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 266616b437 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new c6f351ae8b 84: onsuccess: 1: Success after gcc/glibc: 9 commits new ba1853cf08 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 5bf3b001db 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d7497479cf 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e5eae1e9b7 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 80b8307de5 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 2f6c0bc4c0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 7b788e1993 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new be3927a0d1 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new c69e65d0d2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 2f207bfee7 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 9b002fa40b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new e215c62130 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new de9a57b3fe 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 17f4482224 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new afcff97666 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 1e6f944321 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 487c65b540 101: onsuccess: #1693: 1: Success after glibc: 14 commits new bedd0c112a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 86a786f84a 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 506e0e2f5c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 716c894abd 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new ae0a7cd1c2 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 7688c9947b 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 08a8c3a9b8 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new a90f533bb5 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new aba760ea8c 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 7b807d5d1d 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 4814b6f987 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 45900769ad 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new df18c66b21 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 03e97373e1 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 7f62ad7e71 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 91d1cf6f45 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new b0a110161e 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 367138abd2 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 00d364b421 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new b892cdd61c 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 5b1628c84d 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 9412441ddb 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 536e09595b 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 1fc4208681 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 0518ff2f6e 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new b576085546 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 38585af7bd 128: onsuccess: #1723: 1: Success after linux: 12 commits new 473124ec45 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new f5222bcd32 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 36e9ac2370 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new a6d5630d2b 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 2cbdd923fd 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 7e6d34c3c5 134: onsuccess: #1730: 1: Success after binutils: 2 commits new be679fb503 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 5b738589d2 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new b57d879aa7 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 7ef9a89c94 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new e745429419 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new f4b979e274 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new cde3f7591e 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new d3bf501483 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 67f3653c48 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new a1ee480bed 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 887f9d89e6 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new d22f12feaa 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new e2c1007269 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new bc5e8dce75 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new b2371ccb9e 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 0c96a4348e 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 90afc0143c 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new dfc2e1363a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 5de06749f4 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 81fc052de7 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new fe561b6cf3 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 0977ca9c8f 156: onsuccess: #1757: 1: Success after gcc: 4 commits new f3f7d82e65 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 692d7d93b4 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new eec4b8f019 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 887b883eaf 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 2a1151f729 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new c6b3139496 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new d758e27687 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 2c06e9cacc 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 2040edf1bd 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new fa38abd9de 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 7405ec0464 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new f95bcefea2 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new b880501263 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 3f9c1f170a 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 78ab86ee29 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new bd36ba6cc4 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 9575fe5d09 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new ca1d080f41 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 40cc5fff14 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 328d13c5d2 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 1c41797dca 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new f70169803a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 8406279ffe 179: onsuccess: #1810: 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 (60bb53297c) \ 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 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30588 -> 30144 bytes 04-build_abe-stage1/console.log.xz | Bin 90688 -> 91136 bytes 06-build_abe-linux/console.log.xz | Bin 8804 -> 8804 bytes 07-build_abe-glibc/console.log.xz | Bin 233248 -> 233464 bytes 08-build_abe-stage2/console.log.xz | Bin 224592 -> 223928 bytes 09-build_abe-gdb/console.log.xz | Bin 37800 -> 37260 bytes 10-build_abe-qemu/console.log.xz | Bin 31472 -> 31704 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2860 bytes 13-check_regression/console.log.xz | Bin 8320 -> 8876 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 27 + 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 370 +++-- 13-check_regression/results.regressions | 27 + 14-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 4 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 27 + sumfiles/g++.log.xz | Bin 2694764 -> 2699728 bytes sumfiles/g++.sum | 57 +- sumfiles/gcc.log.xz | Bin 2208168 -> 2221976 bytes sumfiles/gcc.sum | 2364 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 883700 -> 890068 bytes sumfiles/gfortran.sum | 91 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201916 -> 202984 bytes sumfiles/libgomp.sum | 88 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434536 -> 434428 bytes sumfiles/libstdc++.sum | 13 +- 45 files changed, 1862 insertions(+), 1395 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