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 c688b3bc81 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards d134ef5d8b 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards d32676c30e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 339a232989 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 1f78fb35e0 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards ca312e370f 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards d6b813a972 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards b3d37c8014 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards e19f98666e 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 93054d0354 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 46605b9dc7 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards acf8c92424 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards bce8957fe0 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards eee01fe123 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards dfcee24519 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 8acc24fe9a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 6675a8e3c8 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards d4be44b4a8 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards e64f5e9b5d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 045069684a 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 88dc0749d6 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards d45067a79a 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards b744a7325f 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 0c4eaad674 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 529cba50dd 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 2458c82971 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards eb0dddf205 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 96c6ac5c97 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 7dd6122038 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards c987b09b29 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 757b8f4392 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards bd50cf6e65 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 43084b8988 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 78f30129ea 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards fb2d17db2a 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 29721daccc 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 9cd4ed14a1 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 42b880f719 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 5a441da2ee 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6c33fed267 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 1995eeb847 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 3946da0da6 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 64f9a4e432 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 2d5968394e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 71a7cdc1bf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 6966619d1b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards e33067638b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 9bbf77acd6 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 0f4af1e1b5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 25ae4ff82d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards ba7ac75ff5 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 6adecf326c 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards c3b5732ec7 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 562ea50b34 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 06e2e877ef 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 4ebbd15e14 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 5767797586 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 84ecdcee09 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards d84d9d0c43 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 545b31feab 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 4ad3d3767b 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 799d990329 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 8e586365b7 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards dbabe2d8cd 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 4c278c77ce 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 43d35ca68e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 8d265c9f74 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 4b27f7bc0a 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 9a3daa57b1 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 169e2bd70e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards f4a37a89bc 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 4e986d7f77 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards f373e91a1a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 6783fcd29a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 2638d4b7b5 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards d247cf7b48 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards d05de101c2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards f1c1b83443 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 471375cb0e 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ef2dbebf80 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d0bb18dabc 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 127902f37e 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 19ee20e994 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards e8fd7ea586 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards f46a6f7bde 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 51016fb805 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 643752f92b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 83acb77a7a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards f281cc40d9 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 21fb8da077 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d080e6e310 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 00acc8a57d 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 969ad0da50 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8e24818106 74: onsuccess: 1: Successful build after linux: 44 commits discards f3b0087afd 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 18369a782b 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32e92ffa4b 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards aae3b359ee 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 852f55fba0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 13b9ee3e25 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c1b3e37821 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b4a3cc10d6 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3cd1b3e2f2 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 847f31bc1c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 3f12b5c868 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 620b3c7dd4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 95c8c1a05b 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7efa02070d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 8e09962181 74: onsuccess: 1: Successful build after linux: 44 commits new f1fecdc82c 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7638158aa9 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new d44db31ec0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3d8b77d93c 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5ebabebf4a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 83ef584739 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new d851f49e91 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new bd81ec54cd 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new f12e213cea 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new fc104b385c 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 673ed7ad92 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 811d2edc08 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new bbc162d8c9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 726d7c0cb3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new e88d8c94a2 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new dae62d4631 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new bf97f54910 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b0276ce48d 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 00c00fd235 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 8389e05281 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new e17d052d3e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 003fa009a9 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 96f2293d4b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 44df292c6d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 4aa228b7fa 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 23e6b7440a 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 03e813ff84 101: onsuccess: #1693: 1: Success after glibc: 14 commits new f76acfb056 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 7120362758 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new fb5a79770b 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 7ca840ac26 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new d90f305097 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 5c8425f91c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 41c6c45a45 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new b6ebdde214 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 26b10c4261 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 36518a189a 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 970a2d8947 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new c21290bd0d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new acfa8198a5 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new c658de7896 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 7dee60fd43 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 6304904fe2 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 3013bd4509 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 5ee53b7306 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 8ba2bf94ff 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 589d9a7c41 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 323d6c822c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 60af47e9d4 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 606ec12a99 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 328d44f3b4 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 01a76881a0 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new f550384470 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 00c2ef9248 128: onsuccess: #1723: 1: Success after linux: 12 commits new 6b4fec3351 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 530d92c7f0 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 89be0c056f 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 1425bddd37 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 43d56961a4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new f10531b478 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 918a4ce90e 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 61219f13cd 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 4153d41270 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 59c17d77ec 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 4fe4e4d2d7 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 2b49940e41 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new e3400e8073 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 46813c5e6a 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new cef517b0ea 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 75941aa3aa 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 31312ef800 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 3832255bc5 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 02a95786e9 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new ff44af5c0e 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new c1066374be 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new f6dd69eac6 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new cdef878324 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new f04490db57 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new fd7bb33a72 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 32370bfd43 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 2b7d3d1077 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 180ac82d23 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 9ec0c5b3d1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 468928b8cf 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 6e4c308981 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 5166f4700f 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new b7944b999b 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new b0ab4efcba 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new f92139b518 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new b49d09f696 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new e753c5c40a 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 0f3a801581 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 5b93d4df1b 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 65b0d37231 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...]
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 (c688b3bc81) \ 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 2732 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30312 -> 30560 bytes 04-build_abe-stage1/console.log.xz | Bin 91132 -> 91224 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9228 -> 9244 bytes 07-build_abe-glibc/console.log.xz | Bin 234008 -> 234736 bytes 08-build_abe-stage2/console.log.xz | Bin 223988 -> 225416 bytes 09-build_abe-gdb/console.log.xz | Bin 37248 -> 37580 bytes 10-build_abe-qemu/console.log.xz | Bin 31960 -> 32596 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2676 -> 2520 bytes 13-check_regression/console.log.xz | Bin 5712 -> 6036 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 32 +- 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 2688840 -> 2691556 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2208868 -> 2210884 bytes sumfiles/gcc.sum | 2746 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 888504 -> 886056 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201328 -> 201448 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423876 -> 424948 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 1573 insertions(+), 1593 deletions(-)