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 97fafd46d0 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 98407df66c 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 46173d5654 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 30fdea8bdd 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards ce13b6d34e 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards bcc2ec2e73 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 8bd2630851 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 440e4f9979 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 7bc56c54d2 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards c722414de5 92: onsuccess: #575: 1: Success after linux: 34 commits discards a2b7a5bc00 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 9c3ddff8c3 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 9d55b54e72 89: onsuccess: #570: 1: Success after linux: 11 commits discards 529c81f680 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 3d597d29d2 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 8e515ccbba 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards b9258ec1d6 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards e4c96ade00 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 82c8d3d791 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 3ef175961c 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards acb96e0627 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 8d2aa2b4d4 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 4883ca2015 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 721c02d4d3 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 5c1d696bf0 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards d5ab3a135f 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards c269c3f3c3 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards e9efae994d 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards c3aadec5a9 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 7abaf86e67 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards fb5b589734 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards c0fe61a434 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 5857f4fa8b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards e37da163a0 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards f4c3047c4c 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 23469f23b9 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 7fea4d7855 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards b47fa2a0fc 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 112d4fe7ac 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 013606d91b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 2eed7f786d 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 76345ffd31 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 5df46e4987 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 453bf1cbd1 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 67fa027eab 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards c115b957ac 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 0584eb64d5 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards a5433ec1ce 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 467aa77fb4 53: onsuccess: #531: 1: Success after binutils: 12 commits discards d92c4332ec 52: onsuccess: #528: 1: Success after binutils: 8 commits discards cd75f4def2 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 25c9117b17 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 1810403c61 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards e3385f3c7e 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards d87adb624c 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards b8c6677c71 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 44bd81d775 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 9d7b6be83a 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 2ebbc85eca 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 0379932895 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 2f4a6dd0ff 41: onsuccess: #514: 1: Success after linux: 64 commits discards de0b8b1902 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards cd74de4663 39: onsuccess: #511: 1: Success after binutils: 8 commits discards c0b19948b6 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 3812928a50 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards b6c8a1207c 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 90c2e09b92 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 120b99a782 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards b83c4ad274 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards d31320a133 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 4ba6a0883c 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 9072faf783 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards f7f3be6ccd 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 8897d09b6f 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 463e1b4fe3 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 7ded707bc6 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 08733b556a 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 2aceaad260 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 07f2dbf929 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 6075e2a076 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards cb180409ef 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5544569e33 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6cdd27cdc8 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6d6eee01de 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9a5fe15fe4 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cfc0e63618 16: onsuccess: 1: Successful build after binutils: 4 commits discards 7acc57325d 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bb48271164 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6d7a12879f 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7e7f94c8ee 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b6555526a0 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 78a54d0e43 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b79daa7586 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 473dbf0f8d 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b84c531afd 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b80f639e5e 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards de08445c3f 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 42ec1d3e9c 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c4fcd58e0d 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards cb36dc221b 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 775f7b1838 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4c4684f449 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 9b468b370f 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 325bdd921d 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 67fead7216 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6cd4219601 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b249c0d928 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 02caff124a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new bb1540f29d 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8aaf497d02 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 44ad42a9d6 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 833a3f20b2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1bb29d14b1 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new de6db8edda 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 69c52d13f3 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 66bf64be33 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 49a2a34381 16: onsuccess: 1: Successful build after binutils: 4 commits new 4a81e2ff52 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ba36d44043 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1cae20c698 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 293c708f23 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new de132c7d30 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5ef775b982 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 71db94a3b3 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new fd89a3bff7 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 5f6b280e68 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 2a4a918a32 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 9c9709faf5 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new ee11b67775 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new 1ada5a016f 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new cd22262da9 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 8e96d0cd2f 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new d8eba7c748 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 036e8e9c88 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 730224df7c 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 1c0ec38bd1 35: onsuccess: #503: 1: Success after binutils: 11 commits new 9a302bdd3b 36: onsuccess: #505: 1: Success after glibc: 3 commits new ec9b4ddc49 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 7b44c2cc86 38: onsuccess: #508: 1: Success after binutils: 3 commits new 9ea3143a72 39: onsuccess: #511: 1: Success after binutils: 8 commits new b661f07e55 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 2b4e071503 41: onsuccess: #514: 1: Success after linux: 64 commits new dd5d7a5632 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 09bf6d7ef8 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 65a0d501d3 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new ef56cdae19 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new a5915a9113 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 4b9e6fbc00 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 55500d9fa7 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 1a6fdfc345 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new fa281447a3 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new c9a3882ac6 51: onsuccess: #525: 1: Success after binutils: 8 commits new 0ef7c3b99b 52: onsuccess: #528: 1: Success after binutils: 8 commits new 5ad45a211d 53: onsuccess: #531: 1: Success after binutils: 12 commits new 6dd6bf1a65 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 6fc4a5d96f 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 9086d30fa5 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new fbe0833b2a 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 8a0a675a73 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new b960b2c8ab 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new ff6aad206a 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 5a801df7c6 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new f83fad5fbc 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new db56cbb471 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new b9b7ea103d 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new a7d609c798 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 51f3020415 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new f91bcdbf9e 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new e24ac084be 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new a70c433b41 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new a1c1591c67 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 3c3af9ec25 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new e4987ce7a5 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 4dc9e21a33 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new f3b8e0219c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new d868045494 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new b3178073bc 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new acd0a03ca1 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 60bf11f100 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new bd23e9674c 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new a82fa790e8 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 5f99b3395c 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new e3f3edebf0 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 906941c24a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 410d9cb3f8 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 2d6ccd5c32 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new f2864054c9 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 998606a1c1 87: onsuccess: #567: 1: Success after binutils: 8 commits new c3144e9a70 88: onsuccess: #569: 1: Success after glibc: 10 commits new 8e7763c027 89: onsuccess: #570: 1: Success after linux: 11 commits new 200f2212fc 90: onsuccess: #572: 1: Success after binutils: 15 commits new 822e55c593 91: onsuccess: #574: 1: Success after glibc: 3 commits new 42e29379a0 92: onsuccess: #575: 1: Success after linux: 34 commits new 27af64ebc5 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 7ba70eb298 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new f2f4c6e0ef 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 0d59a4f067 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 9db3ce08d3 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new b9493736e2 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new c3016e4063 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 591aa75c1c 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new dfad8b443a 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 81847c2309 102: onsuccess: #586: 1: Success after binutils: 5 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 (97fafd46d0) \ 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 1688 -> 1640 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52180 -> 52804 bytes 04-build_abe-gcc/console.log.xz | Bin 233684 -> 235168 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9720 -> 9852 bytes 07-build_abe-glibc/console.log.xz | Bin 236732 -> 237668 bytes 08-build_abe-gdb/console.log.xz | Bin 49440 -> 50668 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2236 -> 2156 bytes 11-check_regression/console.log.xz | Bin 14352 -> 17712 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 39 +- 11-check_regression/mail-body.txt | 168 +- 11-check_regression/results.compare | 88 +- 11-check_regression/results.compare2 | 3099 ++++++++- 11-check_regression/results.regressions | 88 +- 12-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 170 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 88 +- sumfiles/gdb.log.xz | Bin 1702088 -> 1737332 bytes sumfiles/gdb.sum | 10817 ++++++++++++++++-------------- 27 files changed, 8816 insertions(+), 5843 deletions(-)