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 36e6249b2d 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards fda657209f 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards b4b1df9e9d 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 30d819b243 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 340e75ec45 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 6bb7f056a8 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards 0413a6ccd9 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 75dc5da15e 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 8e1165bcc7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards e6a8ce4fee 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 00dcf90b31 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards f15562d1ad 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards f3f181d85e 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards d56a646123 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards ebc16cb24b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 99b3b0a589 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards e208f19f46 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards cbe7b7ecc4 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 6bc3473cab 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards a4b5168c08 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 90b9b5d14b 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards aa17949e42 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 732fdf6a6e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 6a4d8d4442 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards b4b93e8abb 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 488070ab21 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 561fc5cfb1 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards f26a2f7ca6 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 6efbbd6137 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 44fbe0e01c 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards ddd6801d0b 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 332b7d61a1 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards be6ab438fe 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards ac52d2959f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards eecb54ae41 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 93100ecb7f 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards f12c9754af 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards ff0e1871c0 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards cd2597dd6e 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 02f73d183a 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 4c92249006 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 065c10358b 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 57106d76ef 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 697dacdf75 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 8bb1b7cca7 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 85d95f1c11 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 03d2f3fcd7 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 2207ed02aa 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards bc7ec49323 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 5a73fcf87d 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 781713ea85 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e459357635 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards a5934a33a5 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c3120f4c1d 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 16b40a4100 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 533d99d93e 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 2407e69ccf 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards ad2bb1e7fe 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 9590874ca8 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 801d366941 128: onsuccess: #1723: 1: Success after linux: 12 commits discards f2d096e0e9 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 3b16ec2059 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards a1ea377a90 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 85434af9dd 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 1f0295995f 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 95bd507c31 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards c0628e5c62 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards f4eb5fbf23 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 5f3202e499 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 40cdb26619 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 510b489766 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 021e8a6668 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 9c6b9e62fc 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards f1f9a2acac 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards e1bdbf9934 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 5141d5f5c4 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards a7049a2236 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 971e0bf560 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 3745d06f97 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 700ebc4c32 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 92231f7225 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 7d70cf049e 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 101ec23ae2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards ad7b11748f 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 1314833421 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 385450af47 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 811fe0a660 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 679d337125 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 6c17fc009e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 9f2f579802 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards dbff8141b1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 50b454fcee 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 1161d8e826 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards ed273ec620 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 548493e65c 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 068bae8daa 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 194f8e41f8 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 547ea3a930 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c80c091f78 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3514b29ec5 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards f9b1c3e21d 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3ce2af6467 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 829659ef8a 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 5d7ad9a045 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0ca28d3efe 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9d7e51e829 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d48c795616 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 29455cbcfb 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 4df7d03bea 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 9817ae1ffd 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 6dd47f1520 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 54cb43d058 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new be5f8512c8 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 5cfc0e3707 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 9051e59697 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 71be664758 101: onsuccess: #1693: 1: Success after glibc: 14 commits new e564ead378 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 08cb373c0d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new d6bffacf7d 104: onsuccess: #1697: 1: Success after gcc: 4 commits new c19fb26787 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 55994884b5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 99da4b70e5 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new dad3c12218 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 6b48cec774 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 88fe12dbfa 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 573c80b771 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 428029eeb1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 0009a295d9 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new dbe815ef03 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 2665bd040e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new d372021e7a 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 08e12cf109 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 52cebbc1d6 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new a00dc4431e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 673655b6b8 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 713bc55b4d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 3b25390c9a 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 1dc7d8a467 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 04cbfc22fe 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new f92b1997fa 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new cf2aa68b93 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 52c94f263c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new e773c5ef3a 128: onsuccess: #1723: 1: Success after linux: 12 commits new 83820057b7 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new eaf1bcead9 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 6113bd20bc 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 63a8fb4a5e 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 72548ce875 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new fda6183593 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 9aaa621a47 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 464bd70178 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 66880a4261 137: onsuccess: #1736: 1: Success after gcc: 5 commits new d4987b1dc2 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 2787f756c9 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 8a70c7813b 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new abc91caa29 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 2a2afc3b95 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 688c443736 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new daf5487172 144: onsuccess: #1743: 1: Success after glibc: 2 commits new c75d5f4986 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 06a48a9848 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new bf4034db31 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 0802beeb49 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 3b9e6613db 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new f4d071053a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 1b9255f57d 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 96ef75f037 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 11a6ac9057 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f22ad5525f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 940baa97fb 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new a4bd53d501 156: onsuccess: #1757: 1: Success after gcc: 4 commits new f2f7bd17bc 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 385dae9722 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 72c1cc1a50 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new bbf09fed91 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 75d8bb0243 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 83dbeaf609 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 23ba8ebf54 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new ac0ca93f8f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 8881e1998e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 73da7ee904 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new c7684a5782 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 5fe997ac41 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 01a5c229e0 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 4812dd51ad 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new adeffc9bbe 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new ff0484fdbd 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 00811a435d 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 9c42fc1a9b 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new e47746ccf1 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 57ea25f469 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 0cfe68e88b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 29e41a862a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 2fc9efe792 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 99e30bec03 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 057f739c03 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new c9cb1f1c1a 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 347e530c56 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 381c1291f6 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 33c7b5aa6c 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new f2eafc6162 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 87a139f239 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new f67e315f61 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 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 (36e6249b2d) \ 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 1700 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30104 -> 30112 bytes 04-build_abe-stage1/console.log.xz | Bin 91256 -> 90304 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8860 -> 8864 bytes 07-build_abe-glibc/console.log.xz | Bin 236172 -> 236800 bytes 08-build_abe-stage2/console.log.xz | Bin 223784 -> 223168 bytes 09-build_abe-gdb/console.log.xz | Bin 37708 -> 37536 bytes 10-build_abe-qemu/console.log.xz | Bin 31200 -> 31112 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3980 -> 2432 bytes 13-check_regression/console.log.xz | Bin 6908 -> 5140 bytes 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 93 +- 14-update_baseline/console.log | 64 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2672344 -> 2679060 bytes sumfiles/g++.sum | 112 +- sumfiles/gcc.log.xz | Bin 2249848 -> 2249772 bytes sumfiles/gcc.sum | 2424 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 889940 -> 891804 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212896 -> 212888 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427112 -> 435596 bytes sumfiles/libstdc++.sum | 10 +- 38 files changed, 1382 insertions(+), 1461 deletions(-)