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 aa54959c50 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards a4afa66982 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 7a03a7b081 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards e8254976f4 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards f6988d40fc 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 738683ae5d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 3d24db96aa 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 3c3e229378 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 010dd149bb 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 79a80871cc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 78f7d6762b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 077f6a15fe 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 1ae324dd9a 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards e301833d56 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 67a4413114 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards cfe24469d0 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 8c0da347d6 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards f7b925e507 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 4a8e77cc9b 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards dfdd89c495 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 5a2199ccb6 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 97a6d3cd24 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards e034ed783d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 7df1352501 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 8a2ee44193 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards d3489672b2 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards efa80937d1 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards f7be42cc30 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 94c8e7f952 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 24f79c535e 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 9e74300ada 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 2e82751533 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 3955b47926 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 27f6b4365e 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 60880d0b21 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 51825e84ab 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards ffc403db87 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards c5b8a314c6 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 63d6aadb8c 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 207cc19a6d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 665c21433d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 774d371867 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards a5ddc0fb5a 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 9b219152be 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 7d671ce2f4 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 1e521b0b0e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards cd625e3d08 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards c3c53fda03 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards b291b8b7c7 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 0a970ccd6c 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 9187619251 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 4a06ca72f9 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 5eeba42a86 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards f35633d262 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 34e663f9f0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9aba36c783 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards fc70b09a3e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards bc0aec3745 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards c6f0e47314 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards dcf51224da 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 2544ccc6e9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 370a311299 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 7d46d13ecf 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 7fb155379a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 5a165b843a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 59791593f9 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9f6dd11420 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 6deb58e69d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 973eec6838 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 064821cb51 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 129469d85c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 204003676e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 4d850b6201 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 66af9ae51d 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 36487a817b 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards fd60c062b1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 73519a5fe4 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 18625e4fec 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards bef782b656 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards f04cf4394e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 4c6d2f6660 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 814aa6c3af 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 7cacd3ef22 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c1c7197160 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5e6edae645 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 9fe079e26f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 5209b8da0b 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 7c8a434250 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 3be4b8d5d9 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 9b5990f395 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2b283e188d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a2e04e48f6 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6f7ecb8019 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 0a695e31c9 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards d259411371 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2432c9bf5f 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0f0ce945e9 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 15746d6869 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fdcfd7d7f0 74: onsuccess: 1: Successful build after linux: 44 commits discards 0abd94658b 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ac998cb3ff 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c2d51e4599 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new da77442f1d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new eb26223940 74: onsuccess: 1: Successful build after linux: 44 commits new 1cbda5a426 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7ea2bbadf7 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 76aa1cf865 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b4a6b0a5f9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a9a999bbbc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ab0173e022 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 579b063342 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 65286e789d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 291541faea 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 73633dd06c 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 9b47a14354 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b5324e6c79 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new e51ed00750 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new d2199eeb9a 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 1e3b2e760f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ffe4387016 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 1b0bbb8ebc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d854255f14 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 3778614c02 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new f406df92ed 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 5265167497 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 43b2c8a657 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 9008315e7e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 29334242c4 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new da686c3630 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new ae42f7d416 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 0142f23f5b 101: onsuccess: #1693: 1: Success after glibc: 14 commits new fcd46dcc7d 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 21e4bd8ac9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 9e8e5bba79 104: onsuccess: #1697: 1: Success after gcc: 4 commits new fbfa870a58 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 9a5422d0d7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new a83d319651 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 34925e3465 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new cc9bf2afa2 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 6a8956e0bd 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 235f3a30d1 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new c577800867 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new c206c735b5 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 125e645395 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 0b9f6379b9 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new c228af9534 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 9feda5690b 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new f37fc69b86 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new cc08949c29 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 46e0d9afb9 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 17d207d5ec 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 77712d26ba 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 37232e3cf0 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new c35c91d011 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 3f1ed7ed4a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new d73908cf0f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 417d9b509c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 4aaafa698f 128: onsuccess: #1723: 1: Success after linux: 12 commits new fbcda176a2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 426a19aa36 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 3b58d2724e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new b8fc0b9242 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new f29ef3409c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 9b7a340d40 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 55e4507f34 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 654ba430e6 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 4bf906431c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 416e2d3933 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 2dd6adb399 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 6271cf63ab 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new bdd0d4f99c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new a8e93ce1ce 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new be3d9fb610 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 361c2a6443 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 6ce2722f7a 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new f06db59e9d 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 473f6c2f6b 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 9a3a44403d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 56fe00bc18 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 0702afbf32 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new ff01c89276 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 5ddd5ff7f7 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new ec7a39df4a 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 79de365429 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 53616cf308 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new af4338db9f 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 92cfd9a51b 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 471828a42f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new c09cdea6ff 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 28d16c9e31 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new b799c9b4da 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new d3ef3c5b3b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 70e35f7f85 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 47d637db6d 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 20dcdbe54e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new d496596cc2 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new e6fabc3067 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 4ab18f443b 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 2b60423303 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 43ab69790d 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 5057f64310 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 95d741e1ac 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 8f47374776 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/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 (aa54959c50) \ 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 1728 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30180 -> 31380 bytes 04-build_abe-stage1/console.log.xz | Bin 90880 -> 92284 bytes 06-build_abe-linux/console.log.xz | Bin 9472 -> 9528 bytes 07-build_abe-glibc/console.log.xz | Bin 234260 -> 236300 bytes 08-build_abe-stage2/console.log.xz | Bin 223284 -> 227408 bytes 09-build_abe-gdb/console.log.xz | Bin 37536 -> 38700 bytes 10-build_abe-qemu/console.log.xz | Bin 30864 -> 31724 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2700 -> 2644 bytes 13-check_regression/console.log.xz | Bin 7764 -> 7584 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 399 ++---- 13-check_regression/results.regressions | 20 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 20 +- sumfiles/g++.log.xz | Bin 2662128 -> 2675008 bytes sumfiles/g++.sum | 27 +- sumfiles/gcc.log.xz | Bin 2207760 -> 2233560 bytes sumfiles/gcc.sum | 2246 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 887296 -> 889516 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201372 -> 201268 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426976 -> 439148 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 1460 insertions(+), 1548 deletions(-)