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 afb7f6f254 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards d91177fa53 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 9405bc67f9 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards d0505f6236 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 7e3aec2b21 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 837ab0ab9d 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards dda1399c7e 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 45947666dc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards fe796bbbee 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 2fc1439a40 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards d25bd64fc2 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 754b98ab5b 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards aad7977295 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 34aa551492 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 8c068b5f09 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards e2f9a3ec3c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 4ec8ea61d8 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 3e268b3f97 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards f793f34367 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards deac3b8cbf 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 09d01fdc7f 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 68be7a05b1 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards cc9a776d3f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 91b88500cd 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 2d0e3a0f51 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 69f8dc2b40 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 32a05a500a 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 2da2bedc07 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 270c0f53f4 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 53f3b25745 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 1b0fbc656b 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards fb1c355d7f 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 90b235c904 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 47a85dc888 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards a2a3058327 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 4fe03acc0e 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 496e982184 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 59ad04d915 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 0cd2d329de 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 787eea4c60 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards fb0d671ad3 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards e4edf976a6 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 7f3fca22c8 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 8ede979455 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 7f1698c806 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards f8001fdf47 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards d3aea42fd4 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 516495b73e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards e3f8ed8b30 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 51ff909c2d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 8d589dee80 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 48c92326ca 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards caa6aad7ef 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 7202f15589 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards a7d58f2332 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 0eba20908c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 6bb093d54e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards d29ed8ef52 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards adab2221b5 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 8f94d8ac9c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3f7ed7cbcb 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 53e7028c2d 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 857df69a61 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 69cf712136 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards ed10149d64 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards fd6a4b9e71 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards b8ad3673e1 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 09e373775a 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 565fa77325 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards d1bd46388e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 9d6a0775a6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards c2d31752a9 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 642cdb1e23 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 2f95420a7a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards acdec19ff5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 92f15a6442 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 538291e92f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 958bb21c1d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 2c414ad820 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards a16ec1f9f5 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 3225db095a 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 453ffc7f31 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7c802303b8 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 4f3837b9ec 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 70df3f47c5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards a94c072b28 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 607d534205 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 9dd2fd7ac4 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards e88aeddad6 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a2810c343e 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 036d47bb85 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 74a6082763 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7bdb4d47b0 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 729fa7e6f7 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2ff239a90b 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 5176d55e26 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5c2d629dda 74: onsuccess: 1: Successful build after linux: 44 commits discards 742716f8f8 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards df03267033 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6dd9925856 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards ee7eee072a 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new e3a90f482e 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new d4ae3d5a3c 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 9de5675f59 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e0e17609bc 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new c808c4eb66 74: onsuccess: 1: Successful build after linux: 44 commits new e32d18410d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new da19b0b948 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new a33a5008f0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1f6ce6bf4b 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5edaac9cdb 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c1aaea2fce 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new b2f666229d 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 6e40892754 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new cd7a761d12 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 8394b49bad 84: onsuccess: 1: Success after gcc/glibc: 9 commits new f70d77183f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e67806d6e4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 80c00ed14f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new be819ac234 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new a52d07285f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 4505ab15ae 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 2ee4c4dcfd 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 49bd6a6256 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 522d937f34 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new fe28954f33 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new a9f1328d1c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 10e1680338 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 96b865a512 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new d2fec2a821 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new b49b8171bc 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new fc3d09712f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 9bf262bb48 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 394b08b8fb 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new d9f71c6b9d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new ee25ffd9e7 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 7e387d6bdb 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new db401f5b84 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 226e3fdf6a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new c0275b8502 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new c47406c82b 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new b357028f30 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 5f76aadbef 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 7b82f23c87 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new b12f127d23 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 69259366cc 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new d09b0c1d6b 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 73e75ea61b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 7e77f1b450 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new e88e11cee3 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 61d6289ab5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new a74900192d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 882928dbd3 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 8cb55418ea 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 17d1f82d53 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 232d89a013 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 162e4dd003 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 3fbbae5eb7 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 26c0c4e55e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 704cddd6d9 128: onsuccess: #1723: 1: Success after linux: 12 commits new de57e9ba27 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new c0e69d0ea2 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new f985cd03bf 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 8f2bc8edd4 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 8f8800e513 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new a8eb45bd2a 134: onsuccess: #1730: 1: Success after binutils: 2 commits new ef633100d1 135: onsuccess: #1733: 1: Success after binutils: 5 commits new b5e9be92af 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 6da4c1851e 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 06ddc47b9b 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 33f2925b4a 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 63f0ab9f11 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 8692727d3d 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 0ec92cb08e 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 8c1b4b1a8f 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new ecac5b22d0 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b311d81b01 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new b7862920f9 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new b5a38af060 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 7563337186 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new e534e27ca1 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 8332454e2d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new ace86a1247 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 07e70bc1d0 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new a65292c832 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 40f701b4c3 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 15285733c3 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 530b9bb587 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 5c915e6c89 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new b1c0a72ab0 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 9f49a62715 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new d897da5652 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 547519d3be 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new efc9f482f8 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 4299b67c7c 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new b49008b0c1 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 1124ac2331 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 304c568fdf 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 2d9b423cc5 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 468c97b593 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 3cec071693 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new a15770e86c 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 971a8df6cb 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...]

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 (afb7f6f254) \ 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 1740 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29992 -> 30236 bytes 04-build_abe-stage1/console.log.xz | Bin 90804 -> 91156 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9464 -> 9464 bytes 07-build_abe-glibc/console.log.xz | Bin 233872 -> 234104 bytes 08-build_abe-stage2/console.log.xz | Bin 223668 -> 224724 bytes 09-build_abe-gdb/console.log.xz | Bin 37312 -> 37392 bytes 10-build_abe-qemu/console.log.xz | Bin 30900 -> 30816 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2776 bytes 13-check_regression/console.log.xz | Bin 6508 -> 5728 bytes 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 22 +- 14-update_baseline/console.log | 40 +- 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 2656676 -> 2692600 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2235312 -> 2203752 bytes sumfiles/gcc.sum | 2514 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 891028 -> 885244 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201504 -> 201296 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 425220 -> 422832 bytes sumfiles/libstdc++.sum | 16 +- 38 files changed, 1424 insertions(+), 1432 deletions(-)