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 e983bf3e9c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards d9df8af538 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 20a59418bf 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 7ee5182049 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards d8f0723963 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 9dad1db68e 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards bd764c03b5 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 5dce5766a3 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 4dd8f075bc 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards b8fcb121ff 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 26b7b9040b 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 2dfbc043e5 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 49c1b608d8 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards ed3c943398 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 07530500c9 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards d982bc4ffc 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 485a62a95d 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards fa886ceab0 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 9cbeb95bc2 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 8c7c1e6a95 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 3b6b94d805 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 3ba26c6a09 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards a99f3a8bb3 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 790ab8fe09 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards a5ba3cd9d1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d761ce5e29 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 9310bfa850 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 32c5636dc5 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 0235de1faf 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards e3693f1d49 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards f73aec0706 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards bc0d1b5253 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 0b05186668 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 0df8f7472c 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 7097a4cae0 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 18aae24cec 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards c0a3db4c85 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards ce3d5ca4ec 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 4a97e580f7 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 0257429e1e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards ad21ac19a6 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards cd9cfc7051 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards a0ab6a3ad0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 1b5152c93e 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 62d2a3628a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 5048094191 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards ae312d931c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards b078445d22 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards a345543f24 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 731d4d2da1 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 7940fea132 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 78d8007739 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 5b0356bcfe 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 572b4166a4 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e294f9b8db 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 855e449b99 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards f18d52e2db 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards db9a4126df 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards e5eb880b3a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 5c6b895a28 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 86cebe779f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 96bf0c9a77 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 417841b2f0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 9a50fc47c4 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 20006fb903 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ae85b4b02f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a89e17ebba 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d7f40d2ffe 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 698b16abd6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 22c8849d64 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 7240ad26ad 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards acfcfccd6b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards ef667b98c9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7ed49d5088 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6bde732342 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 869e43cf97 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ac4902beca 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7d906ec025 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a2b05392fc 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards f8115df2ff 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 152d9d9c66 74: onsuccess: 1: Successful build after linux: 44 commits discards d18e092599 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 21091188d3 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 24ea50fb85 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards b171334fb3 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 547233f33a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 992f51b0ba 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a465020cbc 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 877d0960b6 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 553521013b 65: onsuccess: 1: Successful build after gcc: 4 commits discards d789aa4f6b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 46f21e916f 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 419b3979cb 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 18a606131e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards ccd590fb0b 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5120701f95 59: onsuccess: 1: Successful build after glibc: 2 commits discards 0874c56cb1 58: onsuccess: 1: Successful build after binutils: 2 commits discards ad3a9801b1 57: onsuccess: 1: Successful build after gcc: 7 commits discards 37c3ea4edb 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8fcf491a1c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a45dedba1c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new b1c23570c0 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 9ad8167a90 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0d704ec40b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bff3df3c20 57: onsuccess: 1: Successful build after gcc: 7 commits new 1414b5a3c0 58: onsuccess: 1: Successful build after binutils: 2 commits new b2df515570 59: onsuccess: 1: Successful build after glibc: 2 commits new dca794fe44 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 74d589a6bd 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b1d8f12ace 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 6831f0f2f5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 012eba71a6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a6f24dc039 65: onsuccess: 1: Successful build after gcc: 4 commits new 8130da6213 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 97ed350313 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6c60ef15f4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4228b0f2ad 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 0ac8b36af8 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 8b7ec4ded4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 6cd38c226a 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 838f3dd98c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 28d897959c 74: onsuccess: 1: Successful build after linux: 44 commits new bb4fa8c424 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6cabba42c2 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 65103ae17b 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 54a8a93d22 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7602705a5f 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new e6eb2bad3f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new cbadbad84c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new bb05826da9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 10e1a05c19 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 3f47e8f14f 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 64a1de7507 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 23eb873116 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new a38245a177 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new c3a3910b30 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ee46a68547 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8b88393473 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 947a4bac27 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b92e83bec0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 21573f47ed 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 8345610ea1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new bb560e45ee 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 16cceaa7df 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 71f73b2969 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 95cb27af6f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new a8b01858c0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 0eb707729d 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 81c8d77316 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0cd5cf68c6 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 14eb40d58d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 8f83c67218 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 8179d129b5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 8c443b42c5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 21451aa70a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 7bafa89633 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 194297f8f1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new dfbc9deb0c 110: onsuccess: #1703: 1: Success after gcc: 6 commits new f65076c256 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new a01c16fa57 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 197421cef5 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 6d3e12e92a 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new f798298e80 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 7d86e378b8 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 87af198a63 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new d16de88b59 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 13c677f027 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new ffe21f6a10 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 7fc8b849c7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new d407d27e55 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 02b0833778 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 6d5b202f22 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 347215527d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 4714590f5f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new b8633c3f9c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 2678572c4e 128: onsuccess: #1723: 1: Success after linux: 12 commits new 7018865cf1 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new a7fb194afd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new b37149d27c 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 788b158f1d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 61d96312cc 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new d4fa75bfde 134: onsuccess: #1730: 1: Success after binutils: 2 commits new cc52c1ea0a 135: onsuccess: #1733: 1: Success after binutils: 5 commits new e6c48e643c 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 4034d8c2b8 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 927ec93fa3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 1539a087b8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 4145032150 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 459268cc21 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 9b0c62a331 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 7b59f5e7a2 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 277c2578d2 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 0ab8704a96 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 5df45acfa4 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new a58df84cdb 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new a83196d85b 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new d9ce77a6e4 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new b25bc19c66 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 835809e8e2 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new b8e71afc96 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 439bf6db34 153: onsuccess: #1754: 1: Success after gcc: 2 commits new fc4734cff9 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 782c15e279 155: onsuccess: #1756: 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 (e983bf3e9c) \ 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 1724 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30000 -> 30112 bytes 04-build_abe-stage1/console.log.xz | Bin 90828 -> 90876 bytes 06-build_abe-linux/console.log.xz | Bin 8920 -> 8928 bytes 07-build_abe-glibc/console.log.xz | Bin 234904 -> 234276 bytes 08-build_abe-stage2/console.log.xz | Bin 224020 -> 223936 bytes 09-build_abe-gdb/console.log.xz | Bin 37184 -> 37120 bytes 10-build_abe-qemu/console.log.xz | Bin 31400 -> 31540 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2736 -> 2432 bytes 13-check_regression/console.log.xz | Bin 5916 -> 5700 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 | 25 +- 13-check_regression/results.compare2 | 64 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 46 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 + sumfiles/g++.log.xz | Bin 2650704 -> 2664664 bytes sumfiles/g++.sum | 40 +- sumfiles/gcc.log.xz | Bin 2201416 -> 2232560 bytes sumfiles/gcc.sum | 2014 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893568 -> 886828 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201520 -> 201752 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427764 -> 423444 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1225 insertions(+), 1151 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