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 5561dc107c 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 1d79899b66 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 2e792b60f5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 155e291c7e 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 7428eca236 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 782c79aa42 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 9039197c8d 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards eae6c43256 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 514e56f611 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards a97fccb798 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 280078f9e1 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 99d3d2bf2d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 714500a00f 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards cb8ce74e84 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards c900e456e9 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards a706b24f99 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 889baf0cc0 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 72cd0010d8 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards cc02d95ab9 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards a92b7e36cc 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 116a01a3ec 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards befcf4ccf3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards c9a5979380 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 68c18d080e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 3c65758f80 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 43d315af10 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 9beb51d3a8 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards a1d9e01b9f 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards cbe5af6c39 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 19499d893d 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d43d8954b9 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards e2ea50de6a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 206e10aebd 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards d777dd5035 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 4742e7e4b9 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 0f78343226 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 9eb56a1e38 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards bdaa81022a 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 96a8c734fc 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 529c5b1075 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards b4be7a77bf 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 2f2abbe83b 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b51f649b13 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 910405a806 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 6a83afe4e1 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 69c036eb9d 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 4feedf520a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 82d67016e9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 5114f12ccf 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards fed6e0763d 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 177575c95e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 7e16e613bc 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards e3aeba8184 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards a7e1c1fd5b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards d31dcb32f7 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 709351081b 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards dd044e7a36 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards c4d790673c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards fb3f7ad00a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards b1ed3b0b61 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 31b427d2dc 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards d38a5af1c6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards ce1114733a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 29f865ff7a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 92289b5f5f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 14c5960623 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 49a7c55995 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b4db25a8b3 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards c3f7ef0c0d 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 991f6ec6ff 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards fe4090ac83 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 16e9b61638 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 107df4093b 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b2b14ef501 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 5877ab06ae 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 0fdc820a1e 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 0f34f0c64e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 488cd429b2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 59a33b3ac2 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 06469062ff 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 9c86f60d07 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 5071cd1da2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4633a41a03 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 65f7838c73 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards e5e97be36d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7034cd1fd4 74: onsuccess: 1: Successful build after linux: 44 commits discards 610b36eab7 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 32d8906bde 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f7dceff80 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 2452a1aea4 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 169d0eb5ef 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 8e8d0d088e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4cc05c2a6e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f1195d6b66 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 90993edc03 65: onsuccess: 1: Successful build after gcc: 4 commits discards 22081ddc61 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9e37a679a 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a9641cb4a6 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards b0b3e05670 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards c6b3e4d39a 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 70a9c09306 59: onsuccess: 1: Successful build after glibc: 2 commits new dd724187e0 59: onsuccess: 1: Successful build after glibc: 2 commits new 56d2b9a0a7 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ceb0b3f005 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new d3f2310af7 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new e673c99e73 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new da9f305b4e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fcab108342 65: onsuccess: 1: Successful build after gcc: 4 commits new d4f8f8e6db 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d5a276f912 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new afbbe6c245 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 00b4cf67eb 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new f479f18cdd 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new f01fd66fb1 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new f8d173e1b7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8cb962ac78 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 0161135430 74: onsuccess: 1: Successful build after linux: 44 commits new 85a351f78b 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0e6f2197f1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 5bbfe683b6 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 38f36f18db 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d2c6d5850d 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 1c46af5c13 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 95baebb721 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new af4cee2959 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new b6b31e20de 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new d151fe9f55 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 411621375b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 42dbdc6cf5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 060ba822e0 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f17048f00d 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 12e132d669 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3c9471bcad 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 125ebec8d9 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 1f5978c8d0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 91ff526115 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 54f9f65967 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 746744679b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new bd29c1181f 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 8c6ae34bec 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 1d4a1c7e4a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 2d20ca1fde 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new c8d93ca052 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 312e3968d6 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 878d8fedd5 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new cdc5163928 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 3f870aad5c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new b7c2502e5c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 3453a1696e 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 2cd0cd2899 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 1528c82e77 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 101c33ab87 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 021b2bea38 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 59c2b5d0fb 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 5ff4a75687 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new e2ca038a33 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new baa7267c27 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 3bcd9fad37 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 8dc63b28bc 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b70c2c72d1 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new b11f1f78b0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new cb511c15d4 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 1229adbf27 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 53bda11cf4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 650867adcc 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 872f557821 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 986e99704f 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 873b5de494 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 4f9059cfc8 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new a6cb1341b7 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new c8bf449a40 128: onsuccess: #1723: 1: Success after linux: 12 commits new 3309020e2f 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new b278c114ab 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 548cac9ea1 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new ff4560863d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new a91177956d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new b195ed5b53 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 30901f8a26 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 3b62323578 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new f35f348fb0 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 125a67a7c9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 5c3c94037c 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 4d2d504348 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 6ff2e06009 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 7bbd8f5498 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 9f194eb3e1 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new de06f4b5c7 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 6da79e5ad1 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 5ee8950416 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 3509ac10a6 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 5cbd9990e4 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new e78036bc7b 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 4787bb76d0 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 4b2c6b68a8 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 1706738f87 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new df357442bb 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 8280ce39bb 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 6dc6379251 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new fd9385284a 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 1d62d15eab 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new f88c41496f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 16c20c9893 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new bac3ecc833 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...]

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 (5561dc107c) \ 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 1732 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30328 -> 29972 bytes 04-build_abe-stage1/console.log.xz | Bin 91120 -> 90448 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8316 bytes 07-build_abe-glibc/console.log.xz | Bin 233868 -> 234220 bytes 08-build_abe-stage2/console.log.xz | Bin 224956 -> 223088 bytes 09-build_abe-gdb/console.log.xz | Bin 37380 -> 37132 bytes 10-build_abe-qemu/console.log.xz | Bin 31256 -> 31824 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2996 -> 2792 bytes 13-check_regression/console.log.xz | Bin 5296 -> 6012 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 22 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 54 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 26 + sumfiles/g++.log.xz | Bin 2692488 -> 2687800 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2203488 -> 2196196 bytes sumfiles/gcc.sum | 2288 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 883916 -> 884808 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201460 -> 201460 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425872 -> 432928 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 1351 insertions(+), 1225 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