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 ac14e18db5 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 249c597adc 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 60cad9eed0 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 0e9d9d70d4 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 3c2a36702d 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 4a6819712d 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 91d4e45360 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 1c1da7e3de 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 342db4f102 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards d51cd3200d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards a67e2e7a12 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 2d867408f0 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards ce0e68c7b3 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards aee684273e 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 19e831186c 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 221503eab6 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 529bdc7614 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards b6c1d615a8 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 04ac027cc2 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards ef49cd564a 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 3b6634a5f9 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards b28a1e0b54 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards eff6018b87 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 43f98fdfa5 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 5335a22fa6 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards db01a8601c 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards c49a11adb0 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards b8f7789f52 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 3f0b62a9b5 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 6ab0372dfe 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards ea04f1a1d9 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 4956f6f280 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards bf367934a3 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards e696279c89 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 6faee11809 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 57497ce101 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 11fd1bfe9e 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 37ca2a3fc6 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 9e7dad1e91 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 9cf7a1c7ee 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 894f5765c1 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 0a89f1c076 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards a042574242 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards f39f183e81 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards f8dc512c2d 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 9068a3c982 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards ca25eaf5e3 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards bef4eb681d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 2667698408 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 04c7df7a3f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 0a83fafd33 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards c5e934abf8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards c0c24f2462 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards bea0af0b59 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 0b859d18c7 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards d62ff3cc4d 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 68a9042ee2 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards f72de1942c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 41766ca2a7 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 2388e467d0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 21596b08e7 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 2b41f6978e 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 2fd33dac0a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 3a86509a5f 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards d92d852b79 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards b042025dc6 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 36d34d3c99 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 101eed8e66 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards bd19dbc8f8 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards d696f5684d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards c7e61a22c3 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 8b9bfe5808 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 743b331f01 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards dbf8a68c10 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards d0d9c1e5e4 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards c4b5fb397f 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards f9df49bc55 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 3dd521420b 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards c4165286ae 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards f4b5753260 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 133d5fabc4 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards d96e151cc2 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards c2e33e0da6 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 6d6965416e 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 679907f102 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 167a485a91 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 4e759e8794 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards baa1cfcebc 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards e0e0215866 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards fb13d8c4b7 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 267c58f2fa 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards d1a0a47cf1 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards dab40b6048 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 4d94286332 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 5b6efdb536 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 3c08a565c1 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 619ae4cfc3 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards d3efa12af1 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards f666a97355 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 2d06279bcb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 20fdfa7ff5 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 034046718c 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 94d72315be 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 2ccd815974 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 158114600b 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new e4ca8d5e56 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new cae44eb8d5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new b310221c48 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new f690099c8f 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 8edabf2364 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new a73bc8d300 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new b816d2a42b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 206f841a70 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 997d2737e1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new a63284837a 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 43639b80c4 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 552baa5526 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 5f007222ef 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new bc49e6a2db 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new e207591d27 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 60eab3e388 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 32480913aa 110: onsuccess: #1703: 1: Success after gcc: 6 commits new eb7bf6a38e 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 8e6953c4c5 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new e38700f069 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 834f14b43e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 20577d286e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 9b62bc9312 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new f3d5c3deb3 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 734729d142 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new dc0f5adfdf 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 7da61e5106 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 83c800c0df 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 2cf1acb1f4 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new e0250b14fc 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new c1836cd156 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 84998a1b08 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 41a55fa77a 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new edadea3b9e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 193685dc9a 128: onsuccess: #1723: 1: Success after linux: 12 commits new 372a1cbbc1 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new c2609353fd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 285d271eef 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 3583acd053 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 104072b49b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 9738a23e14 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 3951d2ac48 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 59ad0c3f2e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 90855f3e28 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 9e9131230b 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 86e1327b29 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 9f7454cf10 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new b72dab2471 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 60d6918c05 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 6ae67afe89 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 86ec6e1bbf 144: onsuccess: #1743: 1: Success after glibc: 2 commits new d6192107db 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 2e4946c0a1 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 52d6bac7ef 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 6f9200c98f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 1fafeeeeee 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new b68788792d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 27a0a53621 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new b00b7abb5d 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 6a4d2525b6 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 723501952a 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 20a9b29712 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 79e0d88a57 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 2078e9211d 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 3d65902793 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new eee4aa65e5 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new e52a2c7884 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 5f77029b95 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 43e3105a69 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new a0567f40ce 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 7fb81fe1a3 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new a781d8650b 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 4070817de6 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 99541155e9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 36c82fb5d1 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new a01f85cdb1 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 73ad0ff75d 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 0137a89778 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 76e095d108 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new e8a64da153 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 78d8cfd187 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new cd17256433 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 9f95b6087d 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 04ca72da2c 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 91b4b4cc98 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 5c07e711ee 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new db092e2cf7 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 3fdd23b606 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new f7b3ba45df 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 4411912446 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new c231750a19 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 5c3fe2235c 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new 7bf6147eb2 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 85561786a6 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new f6b4e1e36b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 222465a5ad 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new ee51ebcd66 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new b4137c326c 191: onsuccess: #1949: 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 (ac14e18db5) \ 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 1688 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 30172 -> 31320 bytes 04-build_abe-stage1/console.log.xz | Bin 90008 -> 91248 bytes 06-build_abe-linux/console.log.xz | Bin 8724 -> 8620 bytes 07-build_abe-glibc/console.log.xz | Bin 236556 -> 234896 bytes 08-build_abe-stage2/console.log.xz | Bin 222940 -> 224852 bytes 09-build_abe-gdb/console.log.xz | Bin 37560 -> 38668 bytes 10-build_abe-qemu/console.log.xz | Bin 31028 -> 31032 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2440 -> 2612 bytes 13-check_regression/console.log.xz | Bin 7472 -> 16456 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 19 +- 13-check_regression/mail-body.txt | 83 +- 13-check_regression/results.compare | 45 +- 13-check_regression/results.compare2 | 1943 +++++++++++++++++-- 13-check_regression/results.regressions | 45 +- 14-update_baseline/console.log | 66 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 85 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 45 +- sumfiles/g++.log.xz | Bin 2705192 -> 2733584 bytes sumfiles/g++.sum | 976 ++++++++-- sumfiles/gcc.log.xz | Bin 2227044 -> 2243772 bytes sumfiles/gcc.sum | 3086 +++++++++++++++++++------------ sumfiles/gfortran.log.xz | Bin 888296 -> 892252 bytes sumfiles/gfortran.sum | 53 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 212916 -> 212884 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430300 -> 433372 bytes sumfiles/libstdc++.sum | 36 +- 45 files changed, 4907 insertions(+), 1649 deletions(-)