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 45104503a2 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 8e29e620b1 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 183c4028e8 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 46f3a62436 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards c09df70df7 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 6ea0250ff8 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards c101850e52 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards c0068609d8 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards bf598087fd 92: onsuccess: #575: 1: Success after linux: 34 commits discards 7f2fdb2e9d 91: onsuccess: #574: 1: Success after glibc: 3 commits discards fea224a407 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 79bced8b84 89: onsuccess: #570: 1: Success after linux: 11 commits discards 02040b7131 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 9788cac25e 87: onsuccess: #567: 1: Success after binutils: 8 commits discards cce3eeb570 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 2b559f6673 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 842d4eff56 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 326198556b 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 71d21b8c26 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards dba99002e3 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 28aceb37d3 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 4d6749e22f 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 6168fd1685 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards c510ba0caa 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 253461e9af 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 24b7d4644b 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards ea88059ad3 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 5c86eb3c05 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards ef6309b277 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 9f06734ac7 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 172e87deb7 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 0e7fde6527 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 8660a9762a 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards d4c15d6985 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 1958459f3c 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 44cfe0cb19 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards a710bf23fb 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards a715603601 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 0fbd687dce 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards e1c87a13c4 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 678df301ec 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 55e2d2e646 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards ed8befc126 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 16ab3383f6 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards dd4dd8e5b9 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards e9f1a9fc7c 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 824f8a1a2a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards e0418ac59c 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 4e88a10c93 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 0e02f62c0e 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 6fcff0e2c4 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 67fdf9162b 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 7a49bbebfc 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 47b9af097c 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards b3ec7b7e9e 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards d821023b24 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 1e9ef8c363 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 179075b283 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 43929ef823 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 91bc5e8af6 41: onsuccess: #514: 1: Success after linux: 64 commits discards 0311f7072c 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 1a3645778a 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 2c35935024 38: onsuccess: #508: 1: Success after binutils: 3 commits discards d99c2077a5 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 35e9e86032 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 5f6499281a 35: onsuccess: #503: 1: Success after binutils: 11 commits discards c5988c8282 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 711d9e14f5 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 0603518471 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 880f2a19d1 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 25ff4f4afe 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 2b9c9ef1e4 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 7f3e14366d 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards bab044226b 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 974e4211ab 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 340e636cb7 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards de83fd40f8 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 553eb53b70 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 49a24a2fef 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards e613c29632 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f3c537707e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2feef5eb27 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 03362364cb 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6211cf3f6a 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6be9365899 16: onsuccess: 1: Successful build after binutils: 4 commits discards 3e623ba088 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 35e151e58f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7161e83e98 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4b20e56fa3 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 215581aa4c 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e1d66a93d4 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 63a9800ae4 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1d851eb8e2 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 457968b525 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 6e36086f4d 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards e8015b9582 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b1b30ef2af 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards d4bf233e6b 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 6bf56cf761 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b5b2a9320c 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 9180f28afc 0: update: binutils-gcc-linux-glibc-gdb: 1 new 77dbab4592 0: update: binutils-gcc-linux-glibc-gdb: 1 new 775f7b1838 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cb36dc221b 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c4fcd58e0d 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 42ec1d3e9c 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new de08445c3f 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b80f639e5e 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b84c531afd 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 473dbf0f8d 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b79daa7586 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 78a54d0e43 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b6555526a0 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7e7f94c8ee 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6d7a12879f 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bb48271164 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7acc57325d 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cfc0e63618 16: onsuccess: 1: Successful build after binutils: 4 commits new 9a5fe15fe4 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6d6eee01de 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6cdd27cdc8 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5544569e33 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cb180409ef 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6075e2a076 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 07f2dbf929 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 2aceaad260 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 08733b556a 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 7ded707bc6 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 463e1b4fe3 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 8897d09b6f 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new f7f3be6ccd 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 9072faf783 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 4ba6a0883c 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new d31320a133 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new b83c4ad274 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 120b99a782 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 90c2e09b92 35: onsuccess: #503: 1: Success after binutils: 11 commits new b6c8a1207c 36: onsuccess: #505: 1: Success after glibc: 3 commits new 3812928a50 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new c0b19948b6 38: onsuccess: #508: 1: Success after binutils: 3 commits new cd74de4663 39: onsuccess: #511: 1: Success after binutils: 8 commits new de0b8b1902 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 2f4a6dd0ff 41: onsuccess: #514: 1: Success after linux: 64 commits new 0379932895 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 2ebbc85eca 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 9d7b6be83a 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 44bd81d775 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new b8c6677c71 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new d87adb624c 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new e3385f3c7e 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 1810403c61 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 25c9117b17 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new cd75f4def2 51: onsuccess: #525: 1: Success after binutils: 8 commits new d92c4332ec 52: onsuccess: #528: 1: Success after binutils: 8 commits new 467aa77fb4 53: onsuccess: #531: 1: Success after binutils: 12 commits new a5433ec1ce 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 0584eb64d5 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new c115b957ac 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 67fa027eab 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 453bf1cbd1 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 5df46e4987 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 76345ffd31 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 2eed7f786d 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 013606d91b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 112d4fe7ac 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new b47fa2a0fc 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 7fea4d7855 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 23469f23b9 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new f4c3047c4c 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new e37da163a0 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 5857f4fa8b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new c0fe61a434 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new fb5b589734 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 7abaf86e67 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new c3aadec5a9 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new e9efae994d 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new c269c3f3c3 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new d5ab3a135f 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 5c1d696bf0 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 721c02d4d3 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 4883ca2015 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 8d2aa2b4d4 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new acb96e0627 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 3ef175961c 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 82c8d3d791 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new e4c96ade00 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new b9258ec1d6 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 8e515ccbba 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 3d597d29d2 87: onsuccess: #567: 1: Success after binutils: 8 commits new 529c81f680 88: onsuccess: #569: 1: Success after glibc: 10 commits new 9d55b54e72 89: onsuccess: #570: 1: Success after linux: 11 commits new 9c3ddff8c3 90: onsuccess: #572: 1: Success after binutils: 15 commits new a2b7a5bc00 91: onsuccess: #574: 1: Success after glibc: 3 commits new c722414de5 92: onsuccess: #575: 1: Success after linux: 34 commits new 7bc56c54d2 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 440e4f9979 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 8bd2630851 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new bcc2ec2e73 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new ce13b6d34e 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 30fdea8bdd 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 46173d5654 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 98407df66c 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 97fafd46d0 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...]

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 (45104503a2) \ 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 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 52548 -> 52180 bytes 04-build_abe-gcc/console.log.xz | Bin 233172 -> 233684 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8828 -> 9720 bytes 07-build_abe-glibc/console.log.xz | Bin 235148 -> 236732 bytes 08-build_abe-gdb/console.log.xz | Bin 50880 -> 49440 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2324 -> 2236 bytes 11-check_regression/console.log.xz | Bin 13644 -> 14352 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 39 +- 11-check_regression/mail-body.txt | 157 +- 11-check_regression/results.compare | 80 +- 11-check_regression/results.compare2 | 6804 ++++++++++++------------- 11-check_regression/results.regressions | 80 +- 12-update_baseline/console.log | 40 + 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 | 159 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 80 +- sumfiles/gdb.log.xz | Bin 1788172 -> 1702088 bytes sumfiles/gdb.sum | 8338 ++++++++++--------------------- 30 files changed, 6341 insertions(+), 9486 deletions(-)