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 fb8ee3cd6e 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 65abd90eba 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 03d7932552 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 3645552889 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 8ac1a35fa4 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 4e1dc80deb 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 867a08dbdf 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 03e7601094 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards fb020efdab 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 203ffe4b8a 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards cdbee36d94 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 888d122b4d 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards f0a20159b4 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 1600bf4677 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards d5180928c4 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 8dca16cf8f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 796258692b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 513fdaf733 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 49b4cd156b 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards d1668e3f23 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 41e67680e1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards c0c0b4dafe 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards f86bc94396 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 93bba83d69 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards b036fa53e8 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 07bb7a128b 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 1982af377d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 8f4e0ef711 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards dc7d633b17 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 5ac43c1af0 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 309833f0a3 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards c7372346f0 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards fca4846aca 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 18adc32340 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 6bfef6a2dc 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 586ac36e64 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards c9500be00c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 81a794b40f 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 815aedfbb6 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 9b70e3caa2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards e80adcbcf8 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards bbc4445662 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 9b995f7438 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards a7742f2cb3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 705406c299 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards e926b292a1 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 2f1872aa9e 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 3bcaa22014 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards e14a15cb9f 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards fdc92b7cb3 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 7bb436dd48 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 529d91a678 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards b70a94e821 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 5d25d57ce0 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 03988eaeb7 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 3826b1e1dc 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards ae600e2b67 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards d9fcd4ae76 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 2baa2d7d19 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards d76a487ab9 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 5c8022b71b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 827c622205 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards ba288063d0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 9386355952 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d928f81a43 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6931e590e9 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 284b5f01e8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards f84b8b3564 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 38e7365e62 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 32a4fc914d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards cd3eee61cf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards ffc9388cef 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 397eb9d276 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards dbda9ac7a3 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 9fb355060a 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards c04851cc0f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards fa3ff10c94 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 1b82de7aa4 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 4e056c8424 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 24702c0528 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards ce7ef20de2 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards f8aef3600f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 9705fbedb1 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3557348a9d 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 66c51d02b6 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards cac2512e3e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards f802b58fb1 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 7c05b0934a 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 9339f88882 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards b1b1363c50 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 4909c8cb2d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 6254037997 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 4be93ca602 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 8d86c7acfb 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 0adfc5d46f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards fc1a56dbf6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards b874839314 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 4348b5da99 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 636bb65fe6 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards a155a24870 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards fe1a75b0ee 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new a4f8ad6e56 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 9d16ef23e9 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new badf0b5424 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 4689092985 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 0be8549fc2 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new c964fd6074 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 814f6b5864 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new abde9cc64b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new aa3916e1d9 101: onsuccess: #1693: 1: Success after glibc: 14 commits new ccabbbe42b 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 95fdfb53b6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 6a09cdd925 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 1c0341c009 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 22fcfe23fc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new f325bbd5ad 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 28c35691ae 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new d68f12d969 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new f234be03a1 110: onsuccess: #1703: 1: Success after gcc: 6 commits new bb874be24c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 06b3e86e67 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new afaa88f230 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new f2e2b272c3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new ad29fd42a3 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 5178a92bd5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 245a012446 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 89a2ef1eb3 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new ac8059e3da 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new fad3ed9a38 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new a478c26c9c 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new d7a5a9a240 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new e143e67b60 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 81962520ca 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 435f5fa1dc 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new b5b7b2f4f1 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 1747782b09 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 58a6e3e9db 128: onsuccess: #1723: 1: Success after linux: 12 commits new 0f5e0f887d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 4754c5ecd1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new da209a0391 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 2091fdf66c 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 98b060d810 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 9f502bd5a1 134: onsuccess: #1730: 1: Success after binutils: 2 commits new f9764bd14f 135: onsuccess: #1733: 1: Success after binutils: 5 commits new ce5c1c5600 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 6dfb4b41bb 137: onsuccess: #1736: 1: Success after gcc: 5 commits new b6f4fb2a69 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new a9bb9023ec 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 76d30e8b5c 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 8c1d6bc354 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 29cee821ea 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new b2ab9124b7 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 28cc853636 144: onsuccess: #1743: 1: Success after glibc: 2 commits new c80282ac5d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 46e7c2a102 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new d2e5a7d5d4 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 5a82ce0a50 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new d1a54422f3 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 56bcacd8d8 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 5f3d750681 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 56641e4fd7 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new a89d04040c 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f90e181169 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 3c07880487 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 0c616d29a8 156: onsuccess: #1757: 1: Success after gcc: 4 commits new a697590cd1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 088fbd4e5d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 608f1e5a32 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new a68dae9c68 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 4aec9ac006 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 6194c3da65 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new ad37bfd3b6 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 2b5e317785 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 9ea462abb9 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 0c5942ece5 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new f46fdea95f 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new fd92c2b0fa 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 45db8c14ee 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 91d7f56fc0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new e713b2a13b 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new ad2fa287e6 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 4c91e5708e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 9cdab326cf 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new ff668282c9 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new db8980b0e7 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 2c341d9410 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 6bc30fdc78 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 23f11ac8a7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new f9a6a40243 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 8d96128ad4 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 006a46e5ac 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new df3da11e87 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 8c05567879 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new b6be351d37 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new ceb35c2437 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 2a881d7ebc 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 608b491186 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 1471c254ff 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 00852a5302 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new ae37227739 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 4f567c9c65 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new c7c2122a32 193: onsuccess: #1992: 1: Success after binutils: 151 commits new bbba426276 194: onsuccess: #1995: 1: Success after linux: 517 commits

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 (fb8ee3cd6e) \ 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 1736 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 31096 -> 31376 bytes 04-build_abe-stage1/console.log.xz | Bin 91880 -> 91692 bytes 06-build_abe-linux/console.log.xz | Bin 8804 -> 8568 bytes 07-build_abe-glibc/console.log.xz | Bin 235780 -> 235336 bytes 08-build_abe-stage2/console.log.xz | Bin 225128 -> 224236 bytes 09-build_abe-gdb/console.log.xz | Bin 39216 -> 39012 bytes 10-build_abe-qemu/console.log.xz | Bin 30888 -> 31328 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3152 -> 3168 bytes 13-check_regression/console.log.xz | Bin 5328 -> 5348 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 | 34 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 26 + sumfiles/g++.log.xz | Bin 2705292 -> 2723764 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2238396 -> 2270540 bytes sumfiles/gcc.sum | 2410 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892756 -> 891784 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 212868 -> 212812 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432932 -> 428940 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1393 insertions(+), 1289 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