This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts.

discards 81847c2309 102: onsuccess: #586: 1: Success after binutils: 5 commits discards dfad8b443a 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 591aa75c1c 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards c3016e4063 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards b9493736e2 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 9db3ce08d3 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 0d59a4f067 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards f2f4c6e0ef 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 7ba70eb298 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 27af64ebc5 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 42e29379a0 92: onsuccess: #575: 1: Success after linux: 34 commits discards 822e55c593 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 200f2212fc 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 8e7763c027 89: onsuccess: #570: 1: Success after linux: 11 commits discards c3144e9a70 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 998606a1c1 87: onsuccess: #567: 1: Success after binutils: 8 commits discards f2864054c9 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 2d6ccd5c32 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 410d9cb3f8 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 906941c24a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards e3f3edebf0 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 5f99b3395c 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards a82fa790e8 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards bd23e9674c 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 60bf11f100 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards acd0a03ca1 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards b3178073bc 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards d868045494 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards f3b8e0219c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 4dc9e21a33 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards e4987ce7a5 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 3c3af9ec25 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards a1c1591c67 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards a70c433b41 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards e24ac084be 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards f91bcdbf9e 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 51f3020415 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards a7d609c798 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards b9b7ea103d 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards db56cbb471 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards f83fad5fbc 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 5a801df7c6 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards ff6aad206a 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards b960b2c8ab 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 8a0a675a73 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards fbe0833b2a 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 9086d30fa5 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 6fc4a5d96f 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 6dd6bf1a65 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 5ad45a211d 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 0ef7c3b99b 52: onsuccess: #528: 1: Success after binutils: 8 commits discards c9a3882ac6 51: onsuccess: #525: 1: Success after binutils: 8 commits discards fa281447a3 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 1a6fdfc345 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 55500d9fa7 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 4b9e6fbc00 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards a5915a9113 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards ef56cdae19 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 65a0d501d3 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 09bf6d7ef8 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards dd5d7a5632 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 2b4e071503 41: onsuccess: #514: 1: Success after linux: 64 commits discards b661f07e55 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 9ea3143a72 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 7b44c2cc86 38: onsuccess: #508: 1: Success after binutils: 3 commits discards ec9b4ddc49 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 9a302bdd3b 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 1c0ec38bd1 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 730224df7c 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 036e8e9c88 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards d8eba7c748 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 8e96d0cd2f 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards cd22262da9 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 1ada5a016f 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards ee11b67775 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 9c9709faf5 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 2a4a918a32 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 5f6b280e68 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards fd89a3bff7 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 71db94a3b3 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 5ef775b982 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards de132c7d30 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 293c708f23 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1cae20c698 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ba36d44043 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4a81e2ff52 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 49a2a34381 16: onsuccess: 1: Successful build after binutils: 4 commits discards 66bf64be33 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 69c52d13f3 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards de6db8edda 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1bb29d14b1 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 833a3f20b2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 44ad42a9d6 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8aaf497d02 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards bb1540f29d 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 02caff124a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b249c0d928 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 6cd4219601 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 67fead7216 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 325bdd921d 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 9b468b370f 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 0b066c4f72 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 86f3bedb5e 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 3afa4046f5 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 64f646a133 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 9d729254de 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 2770dab20d 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new f36918e6a3 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9b8b9c18d2 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c44bbf010b 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a67155cbf4 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3fb7bc87c 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eadfc219ba 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8875336f86 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 20e8e4bf8e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bb1347481f 16: onsuccess: 1: Successful build after binutils: 4 commits new b7f6343089 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9ffdfc0824 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b00512b223 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2b69891f94 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8939f9401a 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 235a2b15ec 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new ea2d0ea96f 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new ca94d3fa2e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 153e7c7569 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 5be94254c8 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 592fa6a1e4 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 18d7b0df13 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new fdf541b5c6 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new ec029be529 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 88c4773878 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 6260ce2203 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 8c4f9beb5f 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new d606e5cd3d 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 786d598a24 35: onsuccess: #503: 1: Success after binutils: 11 commits new 20183da040 36: onsuccess: #505: 1: Success after glibc: 3 commits new 70be96c04c 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 2eb403e426 38: onsuccess: #508: 1: Success after binutils: 3 commits new 71c98a8848 39: onsuccess: #511: 1: Success after binutils: 8 commits new 171efa628f 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 6d25f19c2f 41: onsuccess: #514: 1: Success after linux: 64 commits new fbf28e8330 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 401cfa1536 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new fd7d686275 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 1314968e9b 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new b82a0add07 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 7b918ea38c 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new c5718c82a2 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 99ba940abf 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 5d9a76ec1d 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 3d866e317f 51: onsuccess: #525: 1: Success after binutils: 8 commits new a5f9d3d024 52: onsuccess: #528: 1: Success after binutils: 8 commits new d796bd8cb4 53: onsuccess: #531: 1: Success after binutils: 12 commits new e32b32b4bc 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 814d1e9de8 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 8651e83c28 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new fc9fb2b54a 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 1bfcf4e1c1 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new dcf6f93459 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new f33e73aa0a 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new b3ed8748be 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 77230cf2cd 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 5808fd3fac 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 4d1edb1cd3 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 32e844c906 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 2d24ce296f 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 5bbbf6c618 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 970eaaa6ac 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 25b13899ca 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 3f51f233f9 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 1d2233edc3 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 0782122008 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 0b2c704327 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new a45c516885 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new b91547b23b 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new fe7124d21f 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new eccd1a8d4f 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 7839f3a0b8 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new be952cb436 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 49782a9b24 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new f2ff801e7e 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new ed6a39ec14 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new d79dcae7bd 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 1439f1b0cd 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 2a29c3fbbf 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new f52ae9014c 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new f701c582c6 87: onsuccess: #567: 1: Success after binutils: 8 commits new 72ffd7b403 88: onsuccess: #569: 1: Success after glibc: 10 commits new ee1144f7d7 89: onsuccess: #570: 1: Success after linux: 11 commits new 72d30c4c77 90: onsuccess: #572: 1: Success after binutils: 15 commits new 1ee8957fd1 91: onsuccess: #574: 1: Success after glibc: 3 commits new fbb80485ce 92: onsuccess: #575: 1: Success after linux: 34 commits new 17783f3031 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 00ab6e7e6f 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 7735259e98 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 6e2198426c 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new aea6f13c38 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 610e4aff7a 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 88c1eaa4b1 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 9ca8a88286 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 22c28babbc 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 8177687fa9 102: onsuccess: #586: 1: Success after binutils: 5 commits new bca5eb3048 103: onsuccess: #589: 1: Success after binutils: 3 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 (81847c2309) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...]

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 1640 -> 1624 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52804 -> 51576 bytes 04-build_abe-gcc/console.log.xz | Bin 235168 -> 233664 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9852 -> 9800 bytes 07-build_abe-glibc/console.log.xz | Bin 237668 -> 235104 bytes 08-build_abe-gdb/console.log.xz | Bin 50668 -> 50784 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2156 -> 2236 bytes 11-check_regression/console.log.xz | Bin 17712 -> 7860 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 51 +- 11-check_regression/mail-body.txt | 178 +- 11-check_regression/results.compare | 90 +- 11-check_regression/results.compare2 | 6434 +++---------------------------- 11-check_regression/results.regressions | 90 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 180 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 90 +- sumfiles/gdb.log.xz | Bin 1737332 -> 1786044 bytes sumfiles/gdb.sum | 5346 ++++++++++++------------- 27 files changed, 3412 insertions(+), 9141 deletions(-)