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 d6545f42d9 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 3288503d1a 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 1ead25fe83 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 80106865cc 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards afbb402a1d 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 3d7569387e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 9614f47974 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards fcdd8d9f5b 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 71b585707e 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 11ce1dd8c9 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 01ca749531 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 6db97e57b4 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards fbcb0bd644 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 08e4599a19 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards bb1e82cfbb 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 0696e98bc6 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards bf4498db73 125: onsuccess: #614: 1: Success after linux: 12 commits discards b1642359d7 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 9a7a7f1069 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 2fd03e0954 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 7c42053977 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards b2d67fad2e 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 2cb302b650 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards ca191af5da 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 77afe34cda 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 139fcdc340 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 47fa96658c 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards ce194e6c18 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 357d8cf22f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 89ea5c778b 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards b4e3da6b7b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards f9ff128984 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 6e7036fc04 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 8461318c46 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards b02c0f9e3f 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 7d8ddfac7f 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards d54ff72480 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 03983f13b8 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards a4a9ddeddc 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 137eecbbd3 102: onsuccess: #586: 1: Success after binutils: 5 commits discards a3e7be687c 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 2d83b0ddc0 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards a7a479e98c 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 2b139d67cd 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 6f1d2d57b7 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards bcdd834fd0 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 87d2e70b69 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 007a68e802 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 138d8ea531 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards b857444360 92: onsuccess: #575: 1: Success after linux: 34 commits discards fb6294bc53 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 890891241f 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 0f0987574b 89: onsuccess: #570: 1: Success after linux: 11 commits discards 822a863944 88: onsuccess: #569: 1: Success after glibc: 10 commits discards f4f1f57a09 87: onsuccess: #567: 1: Success after binutils: 8 commits discards d6502a1e44 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 092e3440b9 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 0d05676e8c 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 0e97f85c7b 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards fdef66e78a 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards d3851d664b 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 8cc3f32ba2 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 1dafd5d142 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 1dfd6171f0 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards d84a3277dc 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards f018ad147f 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 9a5547c1b6 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 67ef6fadaa 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards b4f9183c9b 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 0a6004a23f 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 5971f893ca 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 951af94da3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards eb886001d4 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards c48b4b519e 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 116387c448 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards ced58409ec 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards be98b23023 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards e523007b26 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 40d1815498 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 6c05abf72b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 1622ca53d0 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards b5749e00f2 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 50c97142ba 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards eafc270abc 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 3257eae6cd 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 7681cb2227 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards c37814cbb7 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards d0c60f4195 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 68c7542530 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 1de617bd86 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 506e95cffd 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 06b6dfb37b 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 5dc6a0e725 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards c9cac3b780 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards c570d081b2 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 2ea03174f1 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 937101d6c3 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 6581b1b672 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 7605fd1fce 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards ea51c07a5d 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards badadd1850 41: onsuccess: #514: 1: Success after linux: 64 commits new d8503dd9a0 41: onsuccess: #514: 1: Success after linux: 64 commits new 4f96794414 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 69313cc12e 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new a4d29e4fbc 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 4a47320064 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 8b8cc76bc7 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 0b3bf1ca1a 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 53e338a1d9 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 74b6bb89b7 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 2c38f98fd7 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 42be672e6a 51: onsuccess: #525: 1: Success after binutils: 8 commits new b5708906dd 52: onsuccess: #528: 1: Success after binutils: 8 commits new f59fca0363 53: onsuccess: #531: 1: Success after binutils: 12 commits new fa31c1107f 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 60ef2f739b 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 78640bf7cd 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new a9e4408ffd 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 48f7221a3d 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new ecdce3dca6 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 8a675febb5 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 63020d9579 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 38ad9a79d7 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new dab7bbd2da 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 8d34c2d4f0 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 389a1f0ce4 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new dec7003fe4 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 79a2118acb 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 6d45adab86 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 1483373987 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 85c97762f4 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new c55e8b4290 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 7c8bf56159 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 130caefeda 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 8e4e014c8c 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new e05fd8a140 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 1947b4e61f 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new b83e4c7ba8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new d0ce457120 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 5289c69b9b 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 159ca5af87 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new ffa0105960 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new a870af3040 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 9679c165da 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 88a10332bc 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new eec8aec7a0 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 1359c8733f 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 60f88acfbe 87: onsuccess: #567: 1: Success after binutils: 8 commits new 44793017e8 88: onsuccess: #569: 1: Success after glibc: 10 commits new 3eb13ba3f5 89: onsuccess: #570: 1: Success after linux: 11 commits new 27ad8423b5 90: onsuccess: #572: 1: Success after binutils: 15 commits new 263a16fdd8 91: onsuccess: #574: 1: Success after glibc: 3 commits new da0be430f4 92: onsuccess: #575: 1: Success after linux: 34 commits new a8e482c73a 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new cb85ae6cda 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new a33c7cb5a1 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new e386db9f10 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 8f798e394b 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 2a5319ddc4 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new c8a01b5af4 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new a0bbf54835 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 9c04c0d64b 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 80ddd9a17a 102: onsuccess: #586: 1: Success after binutils: 5 commits new 1fece58186 103: onsuccess: #589: 1: Success after binutils: 3 commits new c052cd62c4 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new deb6a305bd 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new c9f5dadfeb 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new feaae6aa43 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 075b0983fa 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 45fdd9336f 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new a549f7804a 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new c90b19867f 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 6f3630c636 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new afd366ab6a 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 763c84c19a 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new c8237f8611 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new b7eaff97b1 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 48441f6205 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new cae230f90f 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new a9402546b8 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 4e5f91cf0c 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 6ea93c5617 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 1f97d3dfd4 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 43934b36ca 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 50ae00315d 124: onsuccess: #612: 1: Success after binutils: 18 commits new 751731ded0 125: onsuccess: #614: 1: Success after linux: 12 commits new e0d6135812 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 990f216a89 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new e98380b989 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new f636ba562b 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new c4fdd15c32 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new eb22b0d838 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new e14a3efefc 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 702fa5536f 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 0a213f0ef4 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 68c3c9bb93 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new f39b439be7 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new c9249648f5 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new a837068782 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 2728b20bfe 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new a0e5c8fccd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new a450e3b144 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 5deb2cc768 142: onsuccess: #634: 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 (d6545f42d9) \ 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 1756 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 54588 -> 53256 bytes 04-build_abe-gcc/console.log.xz | Bin 235700 -> 240668 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8808 bytes 07-build_abe-glibc/console.log.xz | Bin 236420 -> 239560 bytes 08-build_abe-gdb/console.log.xz | Bin 52208 -> 52188 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3824 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2376 -> 2428 bytes 11-check_regression/console.log.xz | Bin 12252 -> 9160 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 48 +- 11-check_regression/mail-body.txt | 178 +- 11-check_regression/results.compare | 93 +- 11-check_regression/results.compare2 | 2611 ++-------------- 11-check_regression/results.regressions | 93 +- 12-update_baseline/console.log | 52 +- 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 | 180 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 93 +- sumfiles/gdb.log.xz | Bin 1807220 -> 1809512 bytes sumfiles/gdb.sum | 5135 ++++++++++++++++--------------- 31 files changed, 3262 insertions(+), 5277 deletions(-)