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 65b0d37231 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 5b93d4df1b 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 0f3a801581 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards e753c5c40a 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards b49d09f696 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards f92139b518 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards b0ab4efcba 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards b7944b999b 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 5166f4700f 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 6e4c308981 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 468928b8cf 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 9ec0c5b3d1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 180ac82d23 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 2b7d3d1077 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 32370bfd43 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards fd7bb33a72 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards f04490db57 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards cdef878324 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards f6dd69eac6 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards c1066374be 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards ff44af5c0e 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 02a95786e9 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 3832255bc5 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 31312ef800 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 75941aa3aa 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards cef517b0ea 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 46813c5e6a 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards e3400e8073 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 2b49940e41 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 4fe4e4d2d7 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 59c17d77ec 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 4153d41270 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 61219f13cd 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 918a4ce90e 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards f10531b478 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 43d56961a4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 1425bddd37 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 89be0c056f 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 530d92c7f0 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 6b4fec3351 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 00c2ef9248 128: onsuccess: #1723: 1: Success after linux: 12 commits discards f550384470 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 01a76881a0 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 328d44f3b4 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 606ec12a99 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 60af47e9d4 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 323d6c822c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 589d9a7c41 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 8ba2bf94ff 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 5ee53b7306 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 3013bd4509 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 6304904fe2 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 7dee60fd43 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards c658de7896 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards acfa8198a5 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards c21290bd0d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 970a2d8947 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 36518a189a 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 26b10c4261 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards b6ebdde214 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 41c6c45a45 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 5c8425f91c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards d90f305097 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 7ca840ac26 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards fb5a79770b 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 7120362758 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards f76acfb056 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 03e813ff84 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 23e6b7440a 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 4aa228b7fa 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 44df292c6d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 96f2293d4b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 003fa009a9 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards e17d052d3e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 8389e05281 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 00c00fd235 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b0276ce48d 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards bf97f54910 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards dae62d4631 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e88d8c94a2 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 726d7c0cb3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards bbc162d8c9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 811d2edc08 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 673ed7ad92 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards fc104b385c 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards f12e213cea 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards bd81ec54cd 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards d851f49e91 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 83ef584739 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 5ebabebf4a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 3d8b77d93c 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d44db31ec0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7638158aa9 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards f1fecdc82c 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8e09962181 74: onsuccess: 1: Successful build after linux: 44 commits discards 7efa02070d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 95c8c1a05b 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 620b3c7dd4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 3f12b5c868 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 847f31bc1c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 3cd1b3e2f2 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b23624c6d1 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 226d3676b6 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new ecfd1ac11e 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 2dce08d5d6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new f097abeebe 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 46464c489d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 80249ac8b2 74: onsuccess: 1: Successful build after linux: 44 commits new b65780ff29 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0133d9adbf 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 0342d908bd 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7a97d4847f 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 20e6017871 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 58312ac168 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 669d35aab3 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 03284eb26a 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ab892e2449 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 9a8a491692 84: onsuccess: 1: Success after gcc/glibc: 9 commits new c357521399 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 25972003ba 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 4db0776e68 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new fe29b25800 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new bfd306470d 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b3b8d483d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 01e5e38865 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 92d8959c04 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 050a821d23 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 0fb7e85f93 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 85e6e0a0d6 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 1f83c51b82 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 0e3d8b7ca1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 5099f3c8fc 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 32359849cc 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new c021adfef1 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 727a7e317e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new a5be2b251f 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new c715e4aaee 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 376834c8ed 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 9b7b4c3365 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 13878c2740 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 6bccb3ae0f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new afe8279768 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 43ca4f163a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new e857659642 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 24a3f85f02 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 53585de4f5 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 6b28f24b5a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 842fdecb1e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 31f1b4f15f 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 8242806ab1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 2be41df45a 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 8abe7f1161 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new bcb6fcad40 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 7c6e10c67c 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 5065b8bbcc 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 4bd248615d 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new c188093154 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 35a702499c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new af538db943 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 071a777f2f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 4572c6524e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6432dde9f9 128: onsuccess: #1723: 1: Success after linux: 12 commits new 1c5867f07c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 898ab7d27c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 2aeb5c7de4 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new dcb65185ca 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 2ca5e50566 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new ca848a71eb 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 0e9916d340 135: onsuccess: #1733: 1: Success after binutils: 5 commits new b6194a10b3 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 329bd39db3 137: onsuccess: #1736: 1: Success after gcc: 5 commits new bfaea73764 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new b8de0db5d5 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new e7c7f098d4 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 5dc8e6ef37 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 8190c9a461 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new f384185dfc 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new e0c7bc2ea7 144: onsuccess: #1743: 1: Success after glibc: 2 commits new c1e4fc8010 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 8332d34a21 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new cd439b3897 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new bd3bc27ee2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new bead610f8d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new f58cba90cb 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new e075de8774 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 8de14d13ff 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 7fdb73e3ab 153: onsuccess: #1754: 1: Success after gcc: 2 commits new b369ed77ae 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 5e5eec0567 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 7a996415c3 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 460d175bcc 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 785c74633b 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 647ee7e200 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 37ba7fed54 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new a2a9864319 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new de3103bf83 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new b0f4a3d321 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new c0def47d20 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 76532c662e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 9a7b823c1a 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 631b24b5dc 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new ae9812ca57 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 8137b6f327 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...]

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 (65b0d37231) \ 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 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30560 -> 30456 bytes 04-build_abe-stage1/console.log.xz | Bin 91224 -> 91028 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9244 -> 11260 bytes 07-build_abe-glibc/console.log.xz | Bin 234736 -> 233956 bytes 08-build_abe-stage2/console.log.xz | Bin 225416 -> 225252 bytes 09-build_abe-gdb/console.log.xz | Bin 37580 -> 37660 bytes 10-build_abe-qemu/console.log.xz | Bin 32596 -> 30888 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2520 -> 2760 bytes 13-check_regression/console.log.xz | Bin 6036 -> 7268 bytes 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 288 +++- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2691556 -> 2691960 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2210884 -> 2202304 bytes sumfiles/gcc.sum | 2574 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 886056 -> 885164 bytes sumfiles/gfortran.sum | 63 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201448 -> 201472 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424948 -> 427180 bytes sumfiles/libstdc++.sum | 16 +- 39 files changed, 1759 insertions(+), 1504 deletions(-)