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 a928742e77a 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 5c1b889cca8 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 883ede36f77 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 710ae3589b2 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards d6f1f3ed9ac 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 6b9df53c5fe 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards f0be3ceaa37 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 3f471667892 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards abf2d0fca0a 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 2a11a9adc3c 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 4e9dd804434 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 5cf17badc35 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 2be858510cb 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 0525ade9320 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 2d0d550765c 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 8aa0cce400b 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 89927af15da 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 3d93ea80086 102: onsuccess: #586: 1: Success after binutils: 5 commits discards c34ab6e53b0 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards 06c9ff3a743 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 2d2f5de1930 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards 29c9677f992 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards c53b8082d50 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards 5a28a74611d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards 05e931c296a 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 2d8c731a9bc 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 7d8c91023bb 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards ebf4fe913b9 92: onsuccess: #575: 1: Success after linux: 34 commits discards e7c4c0ab574 91: onsuccess: #574: 1: Success after glibc: 3 commits discards dc1eb65acb4 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 4275b56ce92 89: onsuccess: #570: 1: Success after linux: 11 commits discards 961b2eb6ecd 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 4387f7ec083 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 3cfd040e325 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 05626c38571 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards f9e485b3743 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 094a1465a8a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards d3980d06087 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards cbcf8767442 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards e73e4c0ba41 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards f369737a084 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 9e0497ce0e5 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards 1ea64d45600 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards dbb4376bda5 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards 1478f8194f5 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards 1bde0216dfa 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 5acef4d51fb 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 729cfbe05f7 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 1fc0e5468ed 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards eb6c1e3ec2d 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards caf15b5a11f 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards e74c37f7468 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 1cfcdbb6bb3 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards e5e19f7c240 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards c5c27b41425 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards a1ce1a0b94f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards a0b0e667cb6 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards b734ff57e8b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 5dd96992524 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 8e3071e8f87 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards 1c43b4798cc 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 624a872d1a7 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 6a73f426561 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 98e6df4287c 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards d3055b89c22 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 25a9bf6a542 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards 78393e065ef 53: onsuccess: #531: 1: Success after binutils: 12 commits discards e08f71d1f93 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 44ea3a809ab 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 2da7f9d71f4 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards 15169060c84 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards 22bfffc185e 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards bda5aadb24b 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards e5f28b766fa 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards adedce41c05 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards 6f591f4a83c 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 0e96fec7105 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 6db491d296f 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards cb4520fa22a 41: onsuccess: #514: 1: Success after linux: 64 commits discards a16a63c94e6 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards ba371be8366 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 3051d23d4ba 38: onsuccess: #508: 1: Success after binutils: 3 commits discards f516c7c35c5 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 02dffdc7407 36: onsuccess: #505: 1: Success after glibc: 3 commits discards c71980adf4b 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 7a1a3dae0b6 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards b305a2766e1 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards 50fc88ca0ae 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 0ff4bcd9d69 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 40cfa37adab 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 6e235cfaa0d 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 787f11ccd4c 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] discards 2b4c27b6804 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards a2093c6da7a 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] discards 82ccc768bf4 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards cab6e9ab10e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards a5e65c1741f 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards b2aac918b31 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 7cdf5fd4b86 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c609a71b326 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards e01e3f33909 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 57b443449aa 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new cf14c162743 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 17d1ff2e52d 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ce8943468eb 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 6afe49af6ed 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 4f0e5e3c9de 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 3d45c83153f 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new f1a246b2e2a 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] new a5e610842d9 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new 966fe82dd0e 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] new 81525d6c6f8 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new aae26873d44 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 4a89e4b522d 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new d0727c23f47 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new ec7a3e21a2b 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new dcf00e71f92 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new a156927e9ce 35: onsuccess: #503: 1: Success after binutils: 11 commits new c3b3b2b633f 36: onsuccess: #505: 1: Success after glibc: 3 commits new a7ed7ebb988 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 49a12818bd6 38: onsuccess: #508: 1: Success after binutils: 3 commits new c28275edd27 39: onsuccess: #511: 1: Success after binutils: 8 commits new 6f47c459617 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new 281a336b4ed 41: onsuccess: #514: 1: Success after linux: 64 commits new a5d1d0f89b5 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new 9305223a266 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new d8a8593b8eb 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 2e3252bee16 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new bf8285f4526 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new fc0c464507f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new 63fe280cae4 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new ca6ccdfa3f1 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new 5d36a788b7a 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new b4e40ed0899 51: onsuccess: #525: 1: Success after binutils: 8 commits new 35da88ce0c1 52: onsuccess: #528: 1: Success after binutils: 8 commits new d42ee0bf323 53: onsuccess: #531: 1: Success after binutils: 12 commits new 883a47e2a9f 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new 04e46e59305 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 855b3502015 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new f12cd0ad84e 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new ef7d19d6748 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 9162ed79f62 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 614e56f1a96 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new 64fae7aae07 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new a6c4099264c 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 3e14d79f8d8 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new a7e80f71f9f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 4f46a69cb6e 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 69794520dbc 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 1631b021c3e 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new c4cec629d04 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new b5a8e238c47 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new b72496cbce3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 14ad3535bf5 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new ea25c7e9e18 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 628ac3ff68d 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 1a41a12c743 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 2d050553466 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new 36c1d4ca818 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new ab8edc1e231 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new c6b85cb1549 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new c9ff3b3d4d1 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 3af66f696e5 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new ad85f005d5d 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 459a0c65792 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new b090926bd58 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new fe48b1d0be2 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 640cccd8a36 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 11c7444207d 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new fa07b5eefeb 87: onsuccess: #567: 1: Success after binutils: 8 commits new e2e4791a3ab 88: onsuccess: #569: 1: Success after glibc: 10 commits new adca18a829f 89: onsuccess: #570: 1: Success after linux: 11 commits new 9a0adca8a7d 90: onsuccess: #572: 1: Success after binutils: 15 commits new 3347b5785da 91: onsuccess: #574: 1: Success after glibc: 3 commits new ddd0c38bef0 92: onsuccess: #575: 1: Success after linux: 34 commits new d2e9cfbb464 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 7e2581b91f4 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 9e84ab16b1e 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 3eec881711d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new 7ed31a3849d 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new fa6b260fcdc 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 34697d0099b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new f76672fb573 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 9c6efa4a6c3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new fb4c8e26cd6 102: onsuccess: #586: 1: Success after binutils: 5 commits new 7f3904959fa 103: onsuccess: #589: 1: Success after binutils: 3 commits new 969d92eb3ce 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 6c4340bd6dc 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 80d3d624336 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new e30a8a2d0d5 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new d29f747289d 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new fd7a4447ffa 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 5cde44e88bf 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 60e7c63366c 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new e9781e8846a 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 1ce5deaee27 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new a1cd67ebd97 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new cc22b968e2a 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 1cc1cc64982 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 731f2e8cf22 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new bc77f92bb49 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 6a6e32e8635 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new d8e06da0ac7 120: onsuccess: #607: 1: Success after binutils/gcc/linux/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 (a928742e77a) \ 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 1692 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 53140 -> 53700 bytes 04-build_abe-gcc/console.log.xz | Bin 235164 -> 235064 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9568 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 238256 -> 238336 bytes 08-build_abe-gdb/console.log.xz | Bin 51836 -> 51896 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2264 -> 2464 bytes 11-check_regression/console.log.xz | Bin 13292 -> 10236 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 57 +- 11-check_regression/mail-body.txt | 222 +- 11-check_regression/results.compare | 97 +- 11-check_regression/results.compare2 | 3094 ++++------------- 11-check_regression/results.regressions | 101 +- 12-update_baseline/console.log | 54 +- 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 | 224 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 101 +- sumfiles/gdb.log.xz | Bin 1698856 -> 1690736 bytes sumfiles/gdb.sum | 5645 +++++++++++++++---------------- 30 files changed, 3769 insertions(+), 5876 deletions(-)