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 c0374f2933 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards f3d2fbcfbc 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 80e7406757 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 6a463a7625 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards b04b0f0a62 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards c4793f7fb9 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 7c3f4e11de 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 3940186e57 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 4e6eaf5066 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards fc1688897e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards b3308bf212 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 13958acce8 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 93f67febdc 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 880a840650 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 5a9123b7fc 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 4f03b287d6 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 34473d81f7 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 59286942c7 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 8c76eb5015 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards dc18858e1d 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 2d691aeda5 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards f367e7444e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 8b0701a3a5 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 699e5de0c5 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards e64c6ab984 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 37acbb5759 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 6ee39c8d9c 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 2fc2779049 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 6e673c216e 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards dc4c41665b 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards c48a934aea 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 02f2d07074 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 2817b9a6d5 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 50e574931c 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 844cf6ac10 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 9754bb8c36 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 53abab4b85 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 01aa5a9e36 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards ca59ce5889 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards f603ed4943 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards abf75e10c1 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 0402bdc5fd 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards c475ad79f8 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 5737ead371 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 14de95f031 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 3e257ee208 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 261545ca61 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 5891ebe621 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 67eabbe130 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards cf4431754b 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 0e1db8717c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 9e2b3918a8 125: onsuccess: #614: 1: Success after linux: 12 commits discards 56c9d2257d 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 87d0dec8d2 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 0a5c51cd0e 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 0aeb550883 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 155cdcdc6a 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards b043b1a967 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 0d6c245589 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 5e2a392db1 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 50fc3a5586 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 6b3d48235a 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards e3904504ff 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 93c0c5d538 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 853e3ea8ce 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards c9d801f82a 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 9815083269 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 6a8d2e82ec 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 8cc4ea2824 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 9bac817f52 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 74001d731b 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards fb976cf70e 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards b58e8590af 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards df8fbea185 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 970feb3308 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 96968677a4 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 366a538aff 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 0afb86b738 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards d8e8c2d3fe 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 5533760944 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 513b60cf29 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards fd8d93d83c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards a8c6a2ce5c 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 671c5daec7 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards d6a28b28d1 92: onsuccess: #575: 1: Success after linux: 34 commits discards 4e720eca63 91: onsuccess: #574: 1: Success after glibc: 3 commits discards e11bbc40c2 90: onsuccess: #572: 1: Success after binutils: 15 commits discards e231ee315e 89: onsuccess: #570: 1: Success after linux: 11 commits discards 31a3eeb128 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 16301ba38f 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 0f185008b4 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 37b74a2b9b 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards a6c79fce7b 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 1cdf69cb60 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 261bef7710 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 3b3c85d492 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 3bd9abb3ee 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 72b4a5ded4 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards ed71ce9329 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 7c3e4039ee 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 4b1b668147 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new dd69823dcf 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new aee4870f2b 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new a20392cf3d 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new fb46985f7e 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new be1cccfe5e 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 9f0a2a03c6 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 5160663612 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 48e13938af 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new a1f8e70112 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 36937a56c6 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 4544bf9393 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 4782b17fa8 87: onsuccess: #567: 1: Success after binutils: 8 commits new a6ad01c39d 88: onsuccess: #569: 1: Success after glibc: 10 commits new af10e76ceb 89: onsuccess: #570: 1: Success after linux: 11 commits new 1f8342c898 90: onsuccess: #572: 1: Success after binutils: 15 commits new 35ff889744 91: onsuccess: #574: 1: Success after glibc: 3 commits new cc863a1af7 92: onsuccess: #575: 1: Success after linux: 34 commits new 3a4639d673 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new f8fef32489 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new d429790a98 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 993c510493 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new c17f78e737 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 34a642f00b 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new d07d9e0c73 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 5c4299c9e4 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 38ad20de4f 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new cbb1c8fec5 102: onsuccess: #586: 1: Success after binutils: 5 commits new 5d8a998c10 103: onsuccess: #589: 1: Success after binutils: 3 commits new 7853b77cfa 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new d1bdbf4872 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new cac4118adb 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 3d241e6478 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 8a521d2222 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 5197f3e9ce 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 4a48ae946f 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new cde43b35a8 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 875d25a65c 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new b481b1471c 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 0abbc543c1 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 159930f428 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 726228e04c 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new a53c850f48 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 7db1373d27 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new d029f737d6 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 9a1a6bf963 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new f88b97f891 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 3e57a38201 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new b713b9e191 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new a4ba8e29a1 124: onsuccess: #612: 1: Success after binutils: 18 commits new 4467f5a519 125: onsuccess: #614: 1: Success after linux: 12 commits new 3003ab2521 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 4110327fad 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new cda95d5af2 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new adde3382e9 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 0e0628c405 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 654aac45d6 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 7cb27c7fc9 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new ae26b70175 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 24e27ed903 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new c9a4401432 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 47ec26a419 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 5481339484 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 1e8e837c9b 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 76c872c767 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new d2edee6fbb 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 637078bbf2 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new d1a437332b 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 145196b5f4 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 37ed268d3a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new e791e29287 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 4b3516d8d3 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 0f3f51b0ea 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new e3ce2d638b 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new c82a7a9526 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 3b2bb794a0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 1560129f1f 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 75de2008b7 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new c3515ca6de 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 4b40c55156 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 897c771670 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 546ef98999 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new f74999e11a 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new f90dd393f6 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 719151a69f 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 3fcd7d04ce 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new d44643dd8f 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 2665df8b02 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 56af823ff4 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 9aeb4c2afa 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new ed916554ee 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new e7c24eab87 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 561009bcba 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 51cf2695c3 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 17324f9c39 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 0938578988 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 3b46cd8243 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new a554eadcc8 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new d32e6113c8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new b824d77d77 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new f8e4497cda 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new a16e5d5298 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new ad8c2172e6 177: onsuccess: #671: 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 (c0374f2933) \ 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 1780 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 51584 -> 51792 bytes 04-build_abe-gcc/console.log.xz | Bin 237588 -> 238680 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 236612 -> 235964 bytes 08-build_abe-gdb/console.log.xz | Bin 51052 -> 51004 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2136 -> 2220 bytes 11-check_regression/console.log.xz | Bin 13988 -> 20624 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 58 +- 11-check_regression/mail-body.txt | 211 +- 11-check_regression/results.compare | 99 +- 11-check_regression/results.compare2 | 3773 +++++++++-- 11-check_regression/results.regressions | 96 +- 12-update_baseline/console.log | 40 +- 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 | 213 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 96 +- sumfiles/gdb.log.xz | Bin 2834644 -> 2796064 bytes sumfiles/gdb.sum | 10659 ++++++++++++------------------ 31 files changed, 7788 insertions(+), 7511 deletions(-)