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 689c09a1e6 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards e578650742 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 61811b3db9 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards a41687fddd 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 339dbad657 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 90e54ce055 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 560a94d92f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 84d336be4b 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards a252262c83 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards e077f9405c 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 1bcce449de 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 7eeac5432c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards b28c2de0f8 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 95a7ce1673 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 343ec42f94 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards fc6dda2b5a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 0e418815a5 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards d9fa3077ea 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards d0d8238e60 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 74d7bed634 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards f38b35e470 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards f51f99cd8e 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards c181afc983 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 38a453ad3c 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards fe7b50c7ad 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 6f64060a08 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 94bb29cfda 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards f50f67269f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 37661e68e8 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards bd682250ac 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 9632f23ffe 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c74a6ee741 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards b92273fbed 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 00d4a57690 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 636d94e0bb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 03f37de322 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 9ff876506a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 3d9cde6214 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 9e0841a9f1 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 38da561415 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 3cfc77c290 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 93d648441b 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards ad6c604268 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards ceae208f02 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards e5c432383b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 72d7450930 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 31fc15ff04 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 7a35833dd9 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 4735780cee 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 4aabf6a5f1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards f168ea5bbe 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards f3ac79a304 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 9589e26ea1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 89a5ee5945 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards f22b86bf04 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 82c95b5b07 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 0c0486e13f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards d543e5f93a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 4eabc0d07c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 29b5e30497 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 858d0417e5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 51c5243516 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 7ac523ab45 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 49ed296544 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 412ecdd15c 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 42f7d70b5b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 6dc605bce0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards e83833ab14 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 9e263e7891 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 682cadfd75 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards b9b5b1e83f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards e028cbfbb7 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 3e8af37cb3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards d062271954 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 3168a256eb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 709cea2b94 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 43c078976d 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e8466b10f7 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards e9237c8182 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b671f02d33 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards a190e8a0bd 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 83b26c7940 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ee62204c31 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards ef02335826 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards f55269aff1 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 145a42c9ac 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 88ad7b89c4 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 88fcc66b3a 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 83400720ed 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 59ec10231c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 00c89a963d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2b4894484d 74: onsuccess: 1: Successful build after linux: 44 commits discards 09e65853c9 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 3f8305d43d 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4ed787c3d4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 31fe049bcd 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 00c4fe41db 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 5ba7d61d48 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cfcf3b36fa 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8788292721 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards bbbcd697e1 65: onsuccess: 1: Successful build after gcc: 4 commits new 2717b4633f 65: onsuccess: 1: Successful build after gcc: 4 commits new 9a16cc7747 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new aa5c0aee1b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0dff50a3fd 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d3f4d1e8bf 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 261cedad8b 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 6631f1bff0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new ee1aa9e0a3 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b25d584ab1 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9bab07d02d 74: onsuccess: 1: Successful build after linux: 44 commits new f2821ee4dd 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7d52477d0c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 6a139f42e1 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 009625268d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ae7d53b30e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 829a80463c 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new a373d3b75f 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 01dbbe7efc 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 68f27e2f9a 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 1ae3b6a4c1 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 93d0a89516 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b6a4047e07 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new de0516942b 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3a8ce9934c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 92ebe8b9da 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 984cf2f8b6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 399be37ff0 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 788883814f 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new cfe89ab268 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 32ada85ef0 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new b03a014437 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new a41ebdc899 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 6cf07ea248 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 8ad1d94edf 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new d9166f8f51 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 98bb3a0914 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 118241b671 101: onsuccess: #1693: 1: Success after glibc: 14 commits new e1a85686c2 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new b566a2d0c1 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new f72148bb3d 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 759c46bf25 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 9d0384c14d 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 2a1da20a26 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new f158c4885a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 2a9748cf06 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 430a6322a9 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 3c4d88f987 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new fad13aa127 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new dfb5c98ab6 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 9c27b4e5f4 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 9b7c4cd222 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 68715915a1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 44ece94078 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 367fd0eeee 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new d96db56c7a 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 56e32c1610 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 271781e148 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new dd22498508 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 1fb3fdc641 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new e8b82b0c21 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new e762a02051 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 1935fc7ee7 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 139fc4b581 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 88c5e3ad61 128: onsuccess: #1723: 1: Success after linux: 12 commits new 2b30a9c5db 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 398e5e64c0 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 326c23386c 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 8664c732ad 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 125603ca2c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 95aa053084 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e11fa54b7c 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 46d82ab5d8 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 7ac989bebb 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 2a5aab2fe3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new d1041e069d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 363b685e67 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 39e6c26922 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new db1cb60a74 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 01aad2c8cc 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 6c1698dc06 144: onsuccess: #1743: 1: Success after glibc: 2 commits new e3a43b9603 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 52b94b74d7 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 7919af197e 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 5d4b319607 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new e855e47411 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new b880a843d7 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 370fb15cbb 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new fe7d1ca5a8 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 2908c65c77 153: onsuccess: #1754: 1: Success after gcc: 2 commits new fcec073ac2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 10547d6496 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 5e6032062b 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 320d2ca20e 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 19551dc10b 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new a464b5af18 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new bc4583dc76 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 15504ec05e 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 85b3a1c1d1 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 132e82d919 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new f833992dce 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 6d761db69a 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 72b9f77f94 166: onsuccess: #1767: 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 (689c09a1e6) \ 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30436 -> 29940 bytes 04-build_abe-stage1/console.log.xz | Bin 90960 -> 92468 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 11940 bytes 07-build_abe-glibc/console.log.xz | Bin 233264 -> 233872 bytes 08-build_abe-stage2/console.log.xz | Bin 224672 -> 225500 bytes 09-build_abe-gdb/console.log.xz | Bin 37660 -> 37236 bytes 10-build_abe-qemu/console.log.xz | Bin 31628 -> 31684 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2752 -> 4156 bytes 13-check_regression/console.log.xz | Bin 6840 -> 7356 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 | 21 +- 13-check_regression/results.compare2 | 219 ++- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 26 + sumfiles/g++.log.xz | Bin 2661780 -> 2685920 bytes sumfiles/g++.sum | 49 +- sumfiles/gcc.log.xz | Bin 2199188 -> 2209732 bytes sumfiles/gcc.sum | 2413 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 886428 -> 890404 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201408 -> 201628 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429724 -> 437736 bytes sumfiles/libstdc++.sum | 6 +- 44 files changed, 1689 insertions(+), 1272 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