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 e65b64029f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 5efa768779 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 20619e135a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards fdface4814 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 69f3efcac0 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards f495c21984 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards d3c132c9f7 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards c8eaa71f17 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards d4eac5f60f 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 00b7ec5032 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards d5284738b4 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 1509e5797c 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 42e5f71ccb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 8af445aa18 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards c144707224 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 796834a9eb 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 2c69eb2877 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards c417996f72 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards ef27c23be0 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards e2ade6fd2d 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 2634e5bf0e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 604c2bd192 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards cf7e457368 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 334c03bfe4 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 4cee2d2950 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards edf44e961b 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 9901cefd05 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 0873396681 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards cebd40e1a1 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards c06bc43455 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 79f0b4ad5c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 419be67eb4 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards d389ab9038 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 5e25f71759 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 072ea0b7b7 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 7ad6605bf4 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 17153ca1e3 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards dedca592c9 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 33473b23ab 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 707e8ea44a 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards dc94270d7a 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 8a5612df27 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards b2749e14d5 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 2a5367545b 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 8456034fa7 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 4b393bf995 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards f36290d92d 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards e3b7c0d9c8 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards eaab5de231 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 966840a433 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 2b8e6bc642 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards bc47f781ab 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 077f699948 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards e7b8eeb699 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards ca18686769 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards c81f5ce3ed 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 4189a19b81 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 8abd333bfe 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards c231abd333 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards a90ec40ac6 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 4552c4311a 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 5d06707876 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards fa287774e1 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards c0f35227e8 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 171d694d7e 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards cc97da76d9 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards a442a6cfcf 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards ab8659c514 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 6bea73d0fb 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 41768e13ee 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 1d17e9c071 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 5e94309426 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 7c21875276 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards fb91827a8e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards e7cd6fb9eb 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 0b8eab815a 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 2c7b729546 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 1deb774b71 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 0b6ef9bb3e 125: onsuccess: #614: 1: Success after linux: 12 commits discards 3b75e1a328 124: onsuccess: #612: 1: Success after binutils: 18 commits discards a556834f3f 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards dea3754b79 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 1f6636a317 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 243208f116 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 77ff8f0301 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 46a2214bc6 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards d8d566854b 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards f19250f138 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 59ce5accd3 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 9ec7b98eed 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards fc278f7444 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards c6c3965f8e 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards e2a3e5c104 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 0c9702f100 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards f022e278e6 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 89f1142101 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 0488a1cf12 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 13174709ed 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards b9d13f1001 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 7b142f60c4 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards a903d36212 103: onsuccess: #589: 1: Success after binutils: 3 commits new 0216e49b18 103: onsuccess: #589: 1: Success after binutils: 3 commits new 54a2688aa5 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new e9c024321e 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 55034f2159 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new cf8d1287ae 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 077f2527f8 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new e4fb7f4d96 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 03ec27b450 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 506418dc47 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new ac02db36dd 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new bf6ed6dd97 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 4f3ef4a048 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 91166f577f 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new c4934a9f1c 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new cbe0e744ac 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 8f2ee92b36 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 0853bd9256 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 5d8cb9714c 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new ba107db767 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 5fc6c20227 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 952b7ca240 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new a024effa05 124: onsuccess: #612: 1: Success after binutils: 18 commits new 3626e6c5a4 125: onsuccess: #614: 1: Success after linux: 12 commits new 0db30703e6 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 57525691af 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 6f18a81058 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new fd9e5bdde0 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 44d6b39ad3 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 57e613bfc4 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new cd3eb540b7 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 475b4c132f 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 846fb98efe 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 10523db4d0 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 70e054c9fa 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new c2a01c2298 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 29b55984cc 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 0085818e16 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 9e225321a0 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new d9368b48ca 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new e88f2e432f 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new dbe554ed30 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new a64ca28686 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 26f47f1e1b 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new dead2a097f 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new b72cf91500 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new bf4b817acd 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new edb55622a4 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 48dbc7dcba 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 6dd21b269b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new d9005c2820 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new caf2290f99 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 6f3de9eb0f 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 1678a4c08c 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 8da95baf73 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 2e39329136 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 734001b984 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new c6e77266f2 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 203923c26d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 7d9157e776 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new fbb03fce52 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 085b730c65 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 8c188a5078 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 51e7dd48ae 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 54186c896d 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 9f548d3467 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 7aaeffad61 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 534df809bc 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 1ef4bdfd47 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 5325862bcd 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new bc1b70d1f1 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new e8f0170fc4 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 6f436dbbef 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new e4ebd9d0f4 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new e8ccbdf5be 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new fb8521603d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 57eca79bf1 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 99476144c1 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 09b86c1613 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new d3c03d7bb9 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 19097b4b21 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 71b1a417fc 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new bd00dd17dd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new 1acc8e86f6 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 5e3200bd5d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 6c6c2262a5 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 1f83acbf8f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 152553cb17 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new a4e89db554 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 3723fcf875 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new 8baeeb222d 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new f903ce1f5c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 178abaecff 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 9784d034d8 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 625926bf49 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 20b51b06cf 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 2e1a5fcde3 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new db2ab0f8de 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 1c75ca6d2c 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 143597b9d8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 99114195cd 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 87149c2876 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new f42726ad67 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...]
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 (e65b64029f) \ 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 1776 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 52880 -> 53080 bytes 04-build_abe-gcc/console.log.xz | Bin 236824 -> 237836 bytes 06-build_abe-linux/console.log.xz | Bin 8324 -> 9572 bytes 07-build_abe-glibc/console.log.xz | Bin 236308 -> 236176 bytes 08-build_abe-gdb/console.log.xz | Bin 50908 -> 51500 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3756 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2128 -> 2340 bytes 11-check_regression/console.log.xz | Bin 7852 -> 8424 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 33 ++- 11-check_regression/mail-body.txt | 97 +++++--- 11-check_regression/results.compare | 60 +++-- 11-check_regression/results.compare2 | 428 +++++++++++++++++--------------- 11-check_regression/results.regressions | 60 +++-- 12-update_baseline/console.log | 34 +-- 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 | 99 +++++--- mail/mail-subject.txt | 2 +- manifest.sh | 38 +-- results | 60 +++-- sumfiles/gdb.log.xz | Bin 2806692 -> 2941420 bytes sumfiles/gdb.sum | 233 ++++++++++------- 30 files changed, 699 insertions(+), 461 deletions(-)