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 8bc9f4b2a0 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 8d10f75a4b 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 698d4c14c1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards b7367844d9 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards c3596228bc 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 18448efd20 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 959755dc19 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 71c6ed8f63 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c7a59c9144 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 14824d42a9 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 5a04795456 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 09beba1368 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards d67752466c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 3a4cb24a70 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 7230689084 128: onsuccess: #1723: 1: Success after linux: 12 commits discards e748fdc42f 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4f70eba9e2 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 3c2254bae8 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 197cbb1036 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 26509ee736 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 3ecd6a7d90 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 43e56ed6f4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 49b212fa8a 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 0872ae4fe5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 1e2992e38d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 093869abaa 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 2e7d85f6c0 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards d56767c7ee 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 89113aec95 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards f0851fcc71 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 36130c6444 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards d380307723 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 810e77831f 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 5e4ab5b436 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards c08fdd475a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 7e6518c219 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 187a5753f0 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 0d56c0762b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 5270923923 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards e9560cf21c 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards af7cf1074a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 01f3f38dd8 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards ca46fbd813 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 5de9119f42 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 75aacdd156 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards a45677a7c4 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 7857103ee2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards cdd5f384ed 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 1feb64d7c5 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 4ea5c0f1f0 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 96240c3b6a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 00200af208 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards fcb32117c2 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d4259c7aec 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2e2a473757 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 790e37c952 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards d03121965c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9d9451fed4 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 6a5b8f9cfc 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ebcefb5e88 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 575e3f96f3 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 04f35fba41 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards b60159821a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 00aeef5344 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b3baf148d7 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7d81171c45 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 187336acd6 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards a7122fb4f4 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2a5849fd9e 74: onsuccess: 1: Successful build after linux: 44 commits discards a14c2ab260 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 8714afe615 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9da6ac3a06 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 2b9ef3a981 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards baea4d3d82 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 1c3c77ec31 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c46afbca4c 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4c6ccba72 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e010542225 65: onsuccess: 1: Successful build after gcc: 4 commits discards f9e8508788 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a20d93404a 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cb61a597cc 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 8160f0fafe 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b1ca9097af 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 953ca06727 59: onsuccess: 1: Successful build after glibc: 2 commits discards 5535a1356e 58: onsuccess: 1: Successful build after binutils: 2 commits discards 2b0209b138 57: onsuccess: 1: Successful build after gcc: 7 commits discards c74da04346 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d68343c55a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1604865fde 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 0f25c9255b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 64afe620f9 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards b84b3f987d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b456ff6aa9 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4e2b460e45 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f9fff1e098 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 6dde03fab9 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ab2d952eb4 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards bbd198732e 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 663aef4434 44: onsuccess: 1: Successful build after linux: 34 commits discards 567fb6ff7b 43: onsuccess: 1: Successful build after gcc: 2 commits discards fc50c36ae1 42: onsuccess: 1: Successful build after baseline build: no [...] new 30a09f3ab9 42: onsuccess: 1: Successful build after baseline build: no [...] new 874a1325c1 43: onsuccess: 1: Successful build after gcc: 2 commits new 31b783c80a 44: onsuccess: 1: Successful build after linux: 34 commits new b6e0c900cf 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 842a080e62 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new dd9f31d122 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a9e88f0e72 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 59c476ec46 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c4782dc76a 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d23c0b0746 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 97d780c50e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 64b0125917 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new b2d36feb04 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 356ca6c51a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eefba6ef73 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 785f320823 57: onsuccess: 1: Successful build after gcc: 7 commits new f36302c6df 58: onsuccess: 1: Successful build after binutils: 2 commits new 9ec2520582 59: onsuccess: 1: Successful build after glibc: 2 commits new 51bf2c82b6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c312dc9e78 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 756f49d247 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 26892c2857 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3a3f0847ad 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 433d8537f4 65: onsuccess: 1: Successful build after gcc: 4 commits new 53b58771d9 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3f5d34ea6f 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 718023b7fa 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e6ed8f72d 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 80006d5437 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new c1e2c17f91 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new ad937ef61f 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c69d9d4217 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 16966c8eb9 74: onsuccess: 1: Successful build after linux: 44 commits new bcc28740cc 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b08a957d18 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 03d2789538 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 54b24ebdd2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 024ca2c347 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 495d84916a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new e15cfe5826 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 947cac56d9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 249a195244 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new a46331671e 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 406e4fbbba 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new d007fadd65 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new f59d1ca4a9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 80fd37c361 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 837583a321 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8dd6e783ec 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new fdcd3375d6 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 587803dc31 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 1a0693d7c9 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new d9f51fe9e2 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new e00333a2fa 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 6ffc90b82b 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 808036a27c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 0522d50fde 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 9fa73e78d9 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 1e7abf4226 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 9446f87e4d 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0cb3043888 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new a17a27f051 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new bfb0cda74f 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 9c35157fe6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new b4faf1b0df 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new fa52745e8c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new b0f610cc28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 511613434d 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 46bff33771 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 115e6368ab 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new b4d07fc103 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 3f07325dd2 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 2b3ab2ccac 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new dfbe87c3fe 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 957f067ba5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b5fd8ce0dd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new a95961bea2 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new f89ae8bff3 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new ad0d2562dc 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 72a36a73d5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new b70e8c90ba 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 761cce069e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new a79f42a46e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new d2d027dfdf 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new d01de6b8ef 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 8ee903730c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 72ca984f87 128: onsuccess: #1723: 1: Success after linux: 12 commits new cce3957603 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 3f808193c3 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 5fa1ad7db8 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 4ede5ad5bb 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 735cf761b8 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 55cd045042 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 90326e0df3 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 6384e614e1 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 5e8355e07a 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 86be48dfd6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 1fff1edcca 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 0ef74d37f1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 8e9f122d9f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new d84842ffb2 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 1155375e33 143: onsuccess: #1742: 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 (8bc9f4b2a0) \ 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 1708 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30144 -> 29876 bytes 04-build_abe-stage1/console.log.xz | Bin 91152 -> 90612 bytes 06-build_abe-linux/console.log.xz | Bin 9256 -> 8760 bytes 07-build_abe-glibc/console.log.xz | Bin 234364 -> 234572 bytes 08-build_abe-stage2/console.log.xz | Bin 223344 -> 222608 bytes 09-build_abe-gdb/console.log.xz | Bin 37556 -> 37240 bytes 10-build_abe-qemu/console.log.xz | Bin 31096 -> 30776 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2744 -> 2432 bytes 13-check_regression/console.log.xz | Bin 6036 -> 6944 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 | 66 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 70 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 26 + sumfiles/g++.log.xz | Bin 2667716 -> 2651552 bytes sumfiles/g++.sum | 40 +- sumfiles/gcc.log.xz | Bin 2226364 -> 2219996 bytes sumfiles/gcc.sum | 1970 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 881588 -> 882784 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201100 -> 201320 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422680 -> 423668 bytes sumfiles/libstdc++.sum | 30 +- 44 files changed, 1288 insertions(+), 1096 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