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 bac3ecc833 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 16c20c9893 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards f88c41496f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 1d62d15eab 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards fd9385284a 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 6dc6379251 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 8280ce39bb 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards df357442bb 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 1706738f87 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 4b2c6b68a8 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 4787bb76d0 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards e78036bc7b 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 5cbd9990e4 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 3509ac10a6 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 5ee8950416 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 6da79e5ad1 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards de06f4b5c7 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 9f194eb3e1 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 7bbd8f5498 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 6ff2e06009 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 4d2d504348 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 5c3c94037c 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 125a67a7c9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards f35f348fb0 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 3b62323578 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 30901f8a26 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards b195ed5b53 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards a91177956d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards ff4560863d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 548cac9ea1 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards b278c114ab 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 3309020e2f 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards c8bf449a40 128: onsuccess: #1723: 1: Success after linux: 12 commits discards a6cb1341b7 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4f9059cfc8 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 873b5de494 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 986e99704f 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 872f557821 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 650867adcc 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 53bda11cf4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 1229adbf27 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards cb511c15d4 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards b11f1f78b0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b70c2c72d1 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 8dc63b28bc 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 3bcd9fad37 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards baa7267c27 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards e2ca038a33 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 5ff4a75687 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 59c2b5d0fb 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 021b2bea38 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 101c33ab87 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 1528c82e77 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 2cd0cd2899 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 3453a1696e 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards b7c2502e5c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 3f870aad5c 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards cdc5163928 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 878d8fedd5 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 312e3968d6 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards c8d93ca052 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 2d20ca1fde 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 1d4a1c7e4a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 8c6ae34bec 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards bd29c1181f 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 746744679b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 54f9f65967 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 91ff526115 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 1f5978c8d0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 125ebec8d9 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 3c9471bcad 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 12e132d669 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f17048f00d 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 060ba822e0 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 42dbdc6cf5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 411621375b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards d151fe9f55 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards b6b31e20de 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards af4cee2959 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 95baebb721 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 1c46af5c13 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards d2c6d5850d 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 38f36f18db 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5bbfe683b6 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0e6f2197f1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 85a351f78b 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0161135430 74: onsuccess: 1: Successful build after linux: 44 commits discards 8cb962ac78 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f8d173e1b7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f01fd66fb1 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards f479f18cdd 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 00b4cf67eb 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards afbbe6c245 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d5a276f912 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d4f8f8e6db 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fcab108342 65: onsuccess: 1: Successful build after gcc: 4 commits discards da9f305b4e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e673c99e73 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d3f2310af7 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards ceb0b3f005 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 56d2b9a0a7 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new fda25b27f6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e0eca13098 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b8e2af1961 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 11272b5b98 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 31e00f93a6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6afa6e50c9 65: onsuccess: 1: Successful build after gcc: 4 commits new 42d5634fe9 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d0a797552a 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 303f7166a2 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 87e8698cb3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 3ca985185c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 1214b9d367 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new e0a932e7fa 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 89cdf6873c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 808ac298bd 74: onsuccess: 1: Successful build after linux: 44 commits new ab25b8b203 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 93e80a4ab0 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new d9a118a6d3 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cac6a60aee 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new af4d0eb2bd 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new e7946da9e2 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 3d32430997 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 3f3bd064a6 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new e13b0bc9d1 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new f7f3babd34 84: onsuccess: 1: Success after gcc/glibc: 9 commits new d2d3b61c3c 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 0205102131 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d00ca8749d 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 781775bb08 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new d8a7d91e8e 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 1b84f1b6d8 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 89b28dc0b5 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 66585fda8a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 30a3645964 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 09d171965e 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new c06cf3f0f4 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 3f9a9c82dd 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 437fbd4bd7 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new eae63ebe79 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 7f4e24d03f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 33d6e9da2e 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new b7f6298f47 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 99b7f4773c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new fd37af66b0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 776f90f8ea 104: onsuccess: #1697: 1: Success after gcc: 4 commits new e0316cbff3 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 987407ff20 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 61b51e626f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new c318e95af2 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 23fb3f1198 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new c043aaf878 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 53f68b4759 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 4a99a5b9fd 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 9046782d58 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 7409c63875 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new a523e7c38f 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 4687c5e839 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 44aed818e3 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new c1588f9fe8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new aaa719dbc9 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 60f94800d6 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 0c715d9d96 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 011079a9b3 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 2059f1cea0 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 53ad23e560 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 451bba2ee4 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 84b082ba09 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new c79e2cf4ba 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 01d34e72d1 128: onsuccess: #1723: 1: Success after linux: 12 commits new 9260f645f6 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 395690f200 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 79b683ff66 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new ebd3206a5a 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new bae3f1ce43 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new be6d05cc2b 134: onsuccess: #1730: 1: Success after binutils: 2 commits new a05ba5fea3 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 4b9c64e437 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new c1d671b4df 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 38ab38b6a6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new c38fc7a118 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 6650631b84 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new a51a711798 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new b981416474 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new e59420cfec 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 0ce2d22729 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 740364c92e 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new e5ad7a917b 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new d6dd8a4f12 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new e493704e45 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new b93cfc7a2e 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 14ebd4dea9 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 612c7de967 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 242c1b21a4 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new a239c2a75b 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 5b721136b2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 4c297dba4e 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 124d728b87 156: onsuccess: #1757: 1: Success after gcc: 4 commits new ab5e303caf 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 87011e1392 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 27ef7952c9 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 82895fac56 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new b74d393922 161: onsuccess: #1762: 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 (bac3ecc833) \ 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 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29972 -> 30700 bytes 04-build_abe-stage1/console.log.xz | Bin 90448 -> 91184 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8316 -> 9188 bytes 07-build_abe-glibc/console.log.xz | Bin 234220 -> 235876 bytes 08-build_abe-stage2/console.log.xz | Bin 223088 -> 225680 bytes 09-build_abe-gdb/console.log.xz | Bin 37132 -> 37648 bytes 10-build_abe-qemu/console.log.xz | Bin 31824 -> 31604 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2792 -> 2704 bytes 13-check_regression/console.log.xz | Bin 6012 -> 8316 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 291 +++- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 64 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 26 - sumfiles/g++.log.xz | Bin 2687800 -> 2652712 bytes sumfiles/g++.sum | 173 ++- sumfiles/gcc.log.xz | Bin 2196196 -> 2228744 bytes sumfiles/gcc.sum | 2224 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 884808 -> 886832 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201460 -> 201464 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432928 -> 424796 bytes sumfiles/libstdc++.sum | 188 +-- 45 files changed, 1749 insertions(+), 1493 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