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 72b9f77f94 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 6d761db69a 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards f833992dce 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 132e82d919 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 85b3a1c1d1 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 15504ec05e 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards bc4583dc76 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards a464b5af18 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 19551dc10b 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 320d2ca20e 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 5e6032062b 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 10547d6496 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards fcec073ac2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 2908c65c77 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards fe7d1ca5a8 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 370fb15cbb 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards b880a843d7 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards e855e47411 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 5d4b319607 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 7919af197e 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 52b94b74d7 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards e3a43b9603 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 6c1698dc06 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 01aad2c8cc 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards db1cb60a74 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 39e6c26922 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 363b685e67 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards d1041e069d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 2a5aab2fe3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 7ac989bebb 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 46d82ab5d8 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards e11fa54b7c 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 95aa053084 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 125603ca2c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 8664c732ad 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 326c23386c 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 398e5e64c0 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 2b30a9c5db 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 88c5e3ad61 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 139fc4b581 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 1935fc7ee7 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards e762a02051 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards e8b82b0c21 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 1fb3fdc641 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards dd22498508 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 271781e148 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 56e32c1610 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards d96db56c7a 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 367fd0eeee 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 44ece94078 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 68715915a1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 9b7c4cd222 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 9c27b4e5f4 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards dfb5c98ab6 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards fad13aa127 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 3c4d88f987 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 430a6322a9 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 2a9748cf06 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards f158c4885a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 2a1da20a26 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9d0384c14d 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 759c46bf25 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards f72148bb3d 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards b566a2d0c1 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards e1a85686c2 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 118241b671 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 98bb3a0914 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards d9166f8f51 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 8ad1d94edf 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 6cf07ea248 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards a41ebdc899 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards b03a014437 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 32ada85ef0 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards cfe89ab268 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 788883814f 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 399be37ff0 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 984cf2f8b6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 92ebe8b9da 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3a8ce9934c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards de0516942b 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b6a4047e07 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 93d0a89516 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 1ae3b6a4c1 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 68f27e2f9a 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 01dbbe7efc 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a373d3b75f 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 829a80463c 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards ae7d53b30e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 009625268d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6a139f42e1 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7d52477d0c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards f2821ee4dd 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9bab07d02d 74: onsuccess: 1: Successful build after linux: 44 commits discards b25d584ab1 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ee1aa9e0a3 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6631f1bff0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 261cedad8b 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards d3f4d1e8bf 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 0dff50a3fd 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aa5c0aee1b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9a16cc7747 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 77cfadf7f4 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c1b3e37821 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 13b9ee3e25 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 852f55fba0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new aae3b359ee 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 32e92ffa4b 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 18369a782b 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f3b0087afd 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 8e24818106 74: onsuccess: 1: Successful build after linux: 44 commits new 969ad0da50 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 00acc8a57d 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new d080e6e310 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21fb8da077 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f281cc40d9 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 83acb77a7a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 643752f92b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 51016fb805 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new f46a6f7bde 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new e8fd7ea586 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 19ee20e994 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 127902f37e 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d0bb18dabc 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new ef2dbebf80 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 471375cb0e 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f1c1b83443 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d05de101c2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d247cf7b48 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 2638d4b7b5 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 6783fcd29a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new f373e91a1a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 4e986d7f77 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new f4a37a89bc 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 169e2bd70e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 9a3daa57b1 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 4b27f7bc0a 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 8d265c9f74 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 43d35ca68e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 4c278c77ce 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new dbabe2d8cd 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 8e586365b7 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 799d990329 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 4ad3d3767b 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 545b31feab 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new d84d9d0c43 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 84ecdcee09 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 5767797586 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 4ebbd15e14 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 06e2e877ef 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 562ea50b34 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new c3b5732ec7 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 6adecf326c 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new ba7ac75ff5 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 25ae4ff82d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 0f4af1e1b5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 9bbf77acd6 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new e33067638b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 6966619d1b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 71a7cdc1bf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 2d5968394e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 64f9a4e432 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 3946da0da6 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 1995eeb847 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6c33fed267 128: onsuccess: #1723: 1: Success after linux: 12 commits new 5a441da2ee 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 42b880f719 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 9cd4ed14a1 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 29721daccc 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new fb2d17db2a 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 78f30129ea 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 43084b8988 135: onsuccess: #1733: 1: Success after binutils: 5 commits new bd50cf6e65 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 757b8f4392 137: onsuccess: #1736: 1: Success after gcc: 5 commits new c987b09b29 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 7dd6122038 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 96c6ac5c97 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new eb0dddf205 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 2458c82971 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 529cba50dd 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 0c4eaad674 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b744a7325f 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new d45067a79a 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 88dc0749d6 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 045069684a 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new e64f5e9b5d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new d4be44b4a8 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 6675a8e3c8 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 8acc24fe9a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new dfcee24519 153: onsuccess: #1754: 1: Success after gcc: 2 commits new eee01fe123 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new bce8957fe0 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new acf8c92424 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 46605b9dc7 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 93054d0354 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new e19f98666e 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new b3d37c8014 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new d6b813a972 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new ca312e370f 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 1f78fb35e0 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 339a232989 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new d32676c30e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new d134ef5d8b 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new c688b3bc81 167: onsuccess: #1768: 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 (72b9f77f94) \ 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 1696 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29940 -> 30312 bytes 04-build_abe-stage1/console.log.xz | Bin 92468 -> 91132 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 11940 -> 9228 bytes 07-build_abe-glibc/console.log.xz | Bin 233872 -> 234008 bytes 08-build_abe-stage2/console.log.xz | Bin 225500 -> 223988 bytes 09-build_abe-gdb/console.log.xz | Bin 37236 -> 37248 bytes 10-build_abe-qemu/console.log.xz | Bin 31684 -> 31960 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 4156 -> 2676 bytes 13-check_regression/console.log.xz | Bin 7356 -> 5712 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 | 209 +-- 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/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 2685920 -> 2688840 bytes sumfiles/g++.sum | 132 +- sumfiles/gcc.log.xz | Bin 2209732 -> 2208868 bytes sumfiles/gcc.sum | 2470 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 890404 -> 888504 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201628 -> 201328 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 437736 -> 423876 bytes sumfiles/libstdc++.sum | 10 +- 44 files changed, 1464 insertions(+), 1719 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