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 8f47374776 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 95d741e1ac 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 5057f64310 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 43ab69790d 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 2b60423303 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 4ab18f443b 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards e6fabc3067 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards d496596cc2 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 20dcdbe54e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 47d637db6d 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 70e35f7f85 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards d3ef3c5b3b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards b799c9b4da 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 28d16c9e31 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards c09cdea6ff 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 471828a42f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 92cfd9a51b 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards af4338db9f 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 53616cf308 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 79de365429 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards ec7a39df4a 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 5ddd5ff7f7 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards ff01c89276 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 0702afbf32 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 56fe00bc18 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 9a3a44403d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 473f6c2f6b 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards f06db59e9d 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 6ce2722f7a 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 361c2a6443 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards be3d9fb610 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards a8e93ce1ce 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards bdd0d4f99c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 6271cf63ab 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 2dd6adb399 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 416e2d3933 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 4bf906431c 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 654ba430e6 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 55e4507f34 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 9b7a340d40 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards f29ef3409c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards b8fc0b9242 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 3b58d2724e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 426a19aa36 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards fbcda176a2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 4aaafa698f 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 417d9b509c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards d73908cf0f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 3f1ed7ed4a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards c35c91d011 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 37232e3cf0 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 77712d26ba 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 17d207d5ec 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 46e0d9afb9 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards cc08949c29 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards f37fc69b86 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9feda5690b 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards c228af9534 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 0b9f6379b9 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 125e645395 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards c206c735b5 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards c577800867 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 235f3a30d1 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 6a8956e0bd 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards cc9bf2afa2 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 34925e3465 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards a83d319651 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9a5422d0d7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards fbfa870a58 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 9e8e5bba79 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 21e4bd8ac9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards fcd46dcc7d 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 0142f23f5b 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards ae42f7d416 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards da686c3630 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 29334242c4 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 9008315e7e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 43b2c8a657 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 5265167497 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards f406df92ed 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 3778614c02 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards d854255f14 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 1b0bbb8ebc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards ffe4387016 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1e3b2e760f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d2199eeb9a 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards e51ed00750 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b5324e6c79 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9b47a14354 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 73633dd06c 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 291541faea 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 65286e789d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 579b063342 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards ab0173e022 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards a9a999bbbc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b4a6b0a5f9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 76aa1cf865 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ea2bbadf7 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 1cbda5a426 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb26223940 74: onsuccess: 1: Successful build after linux: 44 commits discards da77442f1d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 977144eb97 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 97e7b8074f 74: onsuccess: 1: Successful build after linux: 44 commits new 573d2b46fa 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 63916ec43e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 0c23e26d6c 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 56f09a1bf4 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 900c18f71d 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 886f5d14f2 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 68cc75c977 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new d1594c5f9f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 52d0e0e468 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 4817adad1a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new dfe161ce9f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b6e58d22d6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 460ac12fd9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 30f74f3fce 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 48b2c1b2d6 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e0b3bbb227 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c7319e6b58 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b588a1229f 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new c389d1a58f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 8511cc1e25 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 4fa59f29b0 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 57d41791a3 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new d76a75de48 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 5971142123 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new f5e528f9ae 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 0cacf6c55d 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new ad8be835d2 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 15cf3c3a80 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 7275e5ec37 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new c5fc2bca54 104: onsuccess: #1697: 1: Success after gcc: 4 commits new e4e3ec1268 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 8d8d02f84e 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 9aec2fb9af 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 16e406ea44 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 4fda817db4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new e1641919fd 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 2e871697ef 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2c15e251b1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 37e4d5c427 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 56cc21dad1 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 3fb7eb2bc4 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new da8b5bc6f0 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 653eb54d51 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 922dd93460 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 914d5921bc 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 32d493a9cc 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 7ed25814b0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 5f413b9275 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new c555e34276 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new dedd557498 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 3e596ceaa2 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 5db474567c 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new befd3bd75a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new bc8cb33f8c 128: onsuccess: #1723: 1: Success after linux: 12 commits new 633106ddfe 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 4d81bebeb5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new e8ba8971e7 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new cca68c0192 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b7e7c2c7b2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new e17b009aa2 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e3f81eae0a 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 45cea36b25 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 4e54dc4c6c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 8782632382 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 27f84ae717 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new aef3c811e8 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 603ea273ef 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 4f5210f735 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new a2a6d8fdad 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 07b7d46c8c 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 52bd9b33e7 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 259a028b77 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 6b1dcd29f3 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 75afc10d26 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new fa2c401405 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 879c4176fc 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new b0150ca119 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 63859ce7b5 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new f57fb97a9d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f92ecdee0f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 3bbcdc52c5 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 0ea851af38 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 2891848af1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 208dc0de72 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 1f747dea02 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 73c2be95a5 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new c4f14e6b68 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 27f993db34 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 2a41917b16 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 3284ef3a61 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 31da5a1cee 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new a7ed720694 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 232cedcf27 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 196dcecc16 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 14efe4f21b 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 63e3d5c6cd 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 7ff5666b6e 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new bcbe73e3b4 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 3463f08d46 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new dd0d23501f 174: onsuccess: #1775: 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 (8f47374776) \ 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 1692 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 31380 -> 30028 bytes 04-build_abe-stage1/console.log.xz | Bin 92284 -> 90924 bytes 06-build_abe-linux/console.log.xz | Bin 9528 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 236300 -> 236272 bytes 08-build_abe-stage2/console.log.xz | Bin 227408 -> 224160 bytes 09-build_abe-gdb/console.log.xz | Bin 38700 -> 37512 bytes 10-build_abe-qemu/console.log.xz | Bin 31724 -> 32468 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2460 bytes 13-check_regression/console.log.xz | Bin 7584 -> 6592 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 10 +- 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 42 +- 13-check_regression/results.compare2 | 123 +- 13-check_regression/results.regressions | 42 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 42 +- sumfiles/g++.log.xz | Bin 2675008 -> 2655948 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2233560 -> 2238232 bytes sumfiles/gcc.sum | 2200 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 889516 -> 883248 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201268 -> 201488 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439148 -> 426080 bytes sumfiles/libstdc++.sum | 2 +- 43 files changed, 1327 insertions(+), 1440 deletions(-)