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 4aed52704f 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards e01ca5dce2 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 1391eb418e 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 064b8fd1f8 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards ea4c847070 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 06e4c2e08f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 7969ff5582 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards c4483c044a 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 7128771800 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards fee5130275 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 30224301b9 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 5e223ae896 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards bbb3abff8a 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 7e6325f66e 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 4455f43f93 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards df469041f5 103: onsuccess: #589: 1: Success after binutils: 3 commits discards e74704ab12 102: onsuccess: #586: 1: Success after binutils: 5 commits discards d502352970 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards b47a98ef77 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards bd36eee41b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 64e3350288 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 0a30a8ee51 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 7f817c354d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 2e4ea602ff 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 1eaacf01f8 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 882040f89b 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 90d8f6ae3e 92: onsuccess: #575: 1: Success after linux: 34 commits discards a357213025 91: onsuccess: #574: 1: Success after glibc: 3 commits discards ac698fc823 90: onsuccess: #572: 1: Success after binutils: 15 commits discards a7501019a0 89: onsuccess: #570: 1: Success after linux: 11 commits discards 3be320bf08 88: onsuccess: #569: 1: Success after glibc: 10 commits discards dba32e84ce 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 5ffa2d1b6e 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 15a11abf40 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 39dac79e95 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 3d776b834d 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 863feaf83e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards d3218724ac 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards fd46462076 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards ddbfdf7f22 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards afbe6af1a5 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 289a6cf744 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 0edeee1d50 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards e63bb967da 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 99faecb8c4 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 12a9e27bbb 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 4eaf442efd 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 9966fea75c 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 0fd851d994 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 3478d9715a 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards f7f0e1f4c9 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 0acb7ef511 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards cce8be2f62 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards dbf65cce4e 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards bc151648e8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 46532622b5 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 458d281234 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards a1ddc6afa3 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards c7764227a3 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards d7b212e7ed 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards d750b0aed1 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 18eab451e7 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards eec75a1a85 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards fbee1f0c24 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 049c266409 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards e1dfb29a7a 53: onsuccess: #531: 1: Success after binutils: 12 commits discards af92dee603 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 76e79e6862 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 352d8204ce 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards c42cb564b5 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 9e98a161d7 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 9acfc0a72c 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 255dc294d3 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 790f21a1a8 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 2a3d5576cc 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards b5ce5af525 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards be3c62db23 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 9cf9e79b29 41: onsuccess: #514: 1: Success after linux: 64 commits discards 6aad7e5ddb 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 7e47f7852d 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 3ee9303a99 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 7eade2f64e 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 7185fecc40 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 68d53f6366 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 5e6ac694d8 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 7f59382590 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 3406c912f5 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards efdb4d368f 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 502e414bc8 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards edd756eb6e 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 39d0b53224 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 12983f8b08 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards a25702db74 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards fd74aac8e7 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 02467c0d87 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 47d05f2ef7 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards fbc9dd33bc 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 65b3d9ede8 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d4affc1981 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7539fdd082 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a05378acbe 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8ec3a551d5 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e01e3f3390 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c609a71b32 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7cdf5fd4b8 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2aac918b3 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new a5e65c1741 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new cab6e9ab10 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 82ccc768bf 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new a2093c6da7 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 2b4c27b680 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 787f11ccd4 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new 6e235cfaa0 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 40cfa37ada 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 0ff4bcd9d6 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 50fc88ca0a 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new b305a2766e 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 7a1a3dae0b 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new c71980adf4 35: onsuccess: #503: 1: Success after binutils: 11 commits new 02dffdc740 36: onsuccess: #505: 1: Success after glibc: 3 commits new f516c7c35c 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 3051d23d4b 38: onsuccess: #508: 1: Success after binutils: 3 commits new ba371be836 39: onsuccess: #511: 1: Success after binutils: 8 commits new a16a63c94e 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new cb4520fa22 41: onsuccess: #514: 1: Success after linux: 64 commits new 6db491d296 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 0e96fec710 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 6f591f4a83 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new adedce41c0 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new e5f28b766f 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new bda5aadb24 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 22bfffc185 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 15169060c8 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 2da7f9d71f 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 44ea3a809a 51: onsuccess: #525: 1: Success after binutils: 8 commits new e08f71d1f9 52: onsuccess: #528: 1: Success after binutils: 8 commits new 78393e065e 53: onsuccess: #531: 1: Success after binutils: 12 commits new 25a9bf6a54 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new d3055b89c2 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 98e6df4287 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 6a73f42656 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 624a872d1a 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 1c43b4798c 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 8e3071e8f8 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 5dd9699252 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new b734ff57e8 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new a0b0e667cb 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new a1ce1a0b94 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new c5c27b4142 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new e5e19f7c24 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 1cfcdbb6bb 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new e74c37f746 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new caf15b5a11 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new eb6c1e3ec2 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 1fc0e5468e 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 729cfbe05f 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 5acef4d51f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 1bde0216df 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 1478f8194f 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new dbb4376bda 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 1ea64d4560 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 9e0497ce0e 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new f369737a08 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new e73e4c0ba4 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new cbcf876744 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new d3980d0608 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 094a1465a8 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new f9e485b374 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 05626c3857 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 3cfd040e32 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 4387f7ec08 87: onsuccess: #567: 1: Success after binutils: 8 commits new 961b2eb6ec 88: onsuccess: #569: 1: Success after glibc: 10 commits new 4275b56ce9 89: onsuccess: #570: 1: Success after linux: 11 commits new dc1eb65acb 90: onsuccess: #572: 1: Success after binutils: 15 commits new e7c4c0ab57 91: onsuccess: #574: 1: Success after glibc: 3 commits new ebf4fe913b 92: onsuccess: #575: 1: Success after linux: 34 commits new 7d8c91023b 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 2d8c731a9b 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 05e931c296 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 5a28a74611 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new c53b8082d5 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 29c9677f99 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 2d2f5de193 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 06c9ff3a74 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new c34ab6e53b 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 3d93ea8008 102: onsuccess: #586: 1: Success after binutils: 5 commits new 89927af15d 103: onsuccess: #589: 1: Success after binutils: 3 commits new 8aa0cce400 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 2d0d550765 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 0525ade932 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 2be858510c 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 5cf17badc3 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 4e9dd80443 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 2a11a9adc3 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new abf2d0fca0 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 3f47166789 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new f0be3ceaa3 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 6b9df53c5f 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new d6f1f3ed9a 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 710ae3589b 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 883ede36f7 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 5c1b889cca 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new a928742e77 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...]
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 (4aed52704f) \ 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 1752 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 52820 -> 53140 bytes 04-build_abe-gcc/console.log.xz | Bin 234196 -> 235164 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8860 -> 9568 bytes 07-build_abe-glibc/console.log.xz | Bin 234892 -> 238256 bytes 08-build_abe-gdb/console.log.xz | Bin 52012 -> 51836 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2544 -> 2264 bytes 11-check_regression/console.log.xz | Bin 17924 -> 13292 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 76 +- 11-check_regression/mail-body.txt | 235 +- 11-check_regression/results.compare | 166 +- 11-check_regression/results.compare2 | 6558 ++++++++++----------------- 11-check_regression/results.regressions | 121 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 237 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 121 +- sumfiles/gdb.log.xz | Bin 1699936 -> 1698856 bytes sumfiles/gdb.sum | 7464 +++++++++++-------------------- 31 files changed, 5568 insertions(+), 9526 deletions(-)