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 8ff27634e5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards c7a043e9f7 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 5043dab7c8 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards c04bc4c5c2 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 1f08cec5c2 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 416eacd448 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards fd10c9d537 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 9e115977d8 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards bf1846730d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 720bf16da1 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 11baa7ffbe 103: onsuccess: #589: 1: Success after binutils: 3 commits discards e31cde74eb 102: onsuccess: #586: 1: Success after binutils: 5 commits discards c8968012f4 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 7629f65d19 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards d008f6538a 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards e17de61114 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards b3bf3aac53 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards ba994ebfeb 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 8931a772f3 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 21c24872ac 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 8e8220d55d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 83d06ad6cb 92: onsuccess: #575: 1: Success after linux: 34 commits discards 8a66f8f75b 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 63c252ddd6 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 8d80aecce3 89: onsuccess: #570: 1: Success after linux: 11 commits discards eadf489dd4 88: onsuccess: #569: 1: Success after glibc: 10 commits discards f61579a8f6 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 03f7252cfd 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 196dec1bb9 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 13118e7fe5 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 4cb808ebf3 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards e848d52b98 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 8a971d0743 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 3ebf4da571 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 139a0275ec 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 8f073a9baa 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 8a6d52d2b0 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 77d39aa2c0 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 3c2c6c27d3 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards c6d606d2ac 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards b08ff49f9b 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards e6bdcc0d5e 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 80f815dcba 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards e7e0b168d7 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards ed9173ca1b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 610709e496 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 3b0d2472d7 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 6aaea03175 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 843d73a9a2 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards fab90fb8f8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 56217eacf5 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 078a9c0b0d 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards a55638cc7e 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 2a27919237 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards d7ec2cd875 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards fefe85f5f3 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 9e5e1702ed 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 18843227cc 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 8073d0897c 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 1fcf2b954c 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 92280a2415 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 6559e6bdc1 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 5a99df54bb 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 926698864e 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards c5f827d215 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 7bbd764588 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards ec68993817 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards f45d1b4e48 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 5e86e29e10 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 77209f524c 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 29e48d2682 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 2957a77c8f 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 2b48ce5997 41: onsuccess: #514: 1: Success after linux: 64 commits discards 165d0d236f 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 986a2224c7 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 17bb21b3ad 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 876a8cb3a6 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 956525e549 36: onsuccess: #505: 1: Success after glibc: 3 commits discards ede1dd8526 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 413ba11147 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 2f94156d64 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards da01324472 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 96705b4954 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards c80a7004f4 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards d31a3ed36f 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 91290ef0ff 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards ecf3032d6c 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 068e7ff370 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards a12afc12b9 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 5930c03987 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 9ae4e2dc58 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards e41e4b4a32 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 5ce576918d 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b4ef6daa8e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce53188256 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3b2089211e 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fbb29c4cf8 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 887fc2a2ec 16: onsuccess: 1: Successful build after binutils: 4 commits discards 028ce2c26e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9c91487718 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c435f1f287 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bc2df8a76c 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 957ad2b95a 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 698125396e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4f5a1121a0 16: onsuccess: 1: Successful build after binutils: 4 commits new f34b51930d 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c3ff5c37df 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8b389c6e3c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5982764234 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 207ca527ed 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d0bb34c1dd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 45390dfe89 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 561d5045be 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 7a69bdf78b 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 62907c6b66 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 0fc0e0cb6c 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 369df10621 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new 5c676de996 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 74535c4aa9 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new cd4a46dfb5 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 0642abaaa6 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 1bf24b1946 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 5907948485 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new f496aaa272 35: onsuccess: #503: 1: Success after binutils: 11 commits new 715daa7568 36: onsuccess: #505: 1: Success after glibc: 3 commits new 520e3a029f 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 2421b9f968 38: onsuccess: #508: 1: Success after binutils: 3 commits new 25812f4c73 39: onsuccess: #511: 1: Success after binutils: 8 commits new 865fec032d 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 6160c1abbb 41: onsuccess: #514: 1: Success after linux: 64 commits new 0eb09ffec2 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 6f8230a7d0 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new e13543a260 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new d055de2ecd 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new a33ce666a7 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 588ea4a649 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 943bbe27be 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 11e29c45c6 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 62474d4697 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 8b51e2c73f 51: onsuccess: #525: 1: Success after binutils: 8 commits new f7af3aa0fc 52: onsuccess: #528: 1: Success after binutils: 8 commits new e56b4398a9 53: onsuccess: #531: 1: Success after binutils: 12 commits new 40bdb10c0d 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 3e2954af2b 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 8eca219a5f 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new c4d354de00 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 68f8df0259 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 60b538ef25 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 68278180a4 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new a79931e200 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 2dea08bcc3 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 44b7825827 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 62b41388e8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 88a05dc20c 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 23219ab8a1 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e07423f12a 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new ff5e347f92 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 1ffa29a1b6 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 07b3c67f86 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 48a851e9f3 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 374cc8b51a 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 5069c682f0 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 7a0e83d562 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new b92a0237ae 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 8c500c4bdf 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 6f83c9a469 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new d8401757a6 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new a961ce5263 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 042d463c12 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 5af4fca387 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 94e7868fb2 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 29b76b4d6f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 06c0808525 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 95cf077696 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 5dc532145a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 1a713019f1 87: onsuccess: #567: 1: Success after binutils: 8 commits new 6acbb309df 88: onsuccess: #569: 1: Success after glibc: 10 commits new b48a8f5d3a 89: onsuccess: #570: 1: Success after linux: 11 commits new 562ed38490 90: onsuccess: #572: 1: Success after binutils: 15 commits new 36cee161f8 91: onsuccess: #574: 1: Success after glibc: 3 commits new c18d259f18 92: onsuccess: #575: 1: Success after linux: 34 commits new 1816adc89d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 6e15001e88 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 6086146385 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new a3b1698c3b 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new a396ffa81e 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 4da5d7f22e 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new b0a5d22ea1 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new ad33d5fd2e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 13caf389d6 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 560f3fe33f 102: onsuccess: #586: 1: Success after binutils: 5 commits new 32aec39e09 103: onsuccess: #589: 1: Success after binutils: 3 commits new aacbd8fb3c 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new ddc4fae52e 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 3fcb03b091 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new d086e96055 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 3ac5ca222c 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new e5804fe921 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 27aa36a8ed 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 99bc0112e0 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new c077794124 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 53bbc64df5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new b1861fc090 114: onsuccess: #601: 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 (8ff27634e5) \ 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 1704 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 53192 -> 53152 bytes 04-build_abe-gcc/console.log.xz | Bin 236040 -> 234924 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 9520 bytes 07-build_abe-glibc/console.log.xz | Bin 236392 -> 237144 bytes 08-build_abe-gdb/console.log.xz | Bin 51660 -> 51912 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3864 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2176 -> 2200 bytes 11-check_regression/console.log.xz | Bin 12508 -> 10360 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 55 +- 11-check_regression/mail-body.txt | 203 +- 11-check_regression/results.compare | 113 +- 11-check_regression/results.compare2 | 1698 ++------- 11-check_regression/results.regressions | 101 +- 12-update_baseline/console.log | 62 +- 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 | 205 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 101 +- sumfiles/gdb.log.xz | Bin 1711952 -> 1730220 bytes sumfiles/gdb.sum | 5989 ++++++++++++++----------------- 30 files changed, 3349 insertions(+), 5228 deletions(-)