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_binutils/master-arm in repository toolchain/ci/base-artifacts.

discards 30959c53f6a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards d26ac98b1d7 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 5f7313526a3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 0d57f2637f8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 5e244102f32 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f964344d751 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 2fdfd22b5d7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards dee35930d31 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 8b451925d82 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a1a6c2715dd 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 9ec7ed20ea5 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ce52a248e73 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 85238d93ea0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 1eef3551871 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 584319d2fd3 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ac911c5d0bc 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards efdbcb04f8b 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 37e1ff75b6f 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards d165e0997b9 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards fb80ed273c5 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 9c99c29e11c 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards b7f2f51db0d 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards eaa9c030116 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 473ac772e07 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards eb64428099b 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 2bddedc37f8 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards ee8453e8407 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 9b992cca2cf 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 45308e82ff4 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards ffd51616aa1 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 7b647879e9d 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards efd54f992fe 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 599e9230f89 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 8a72cceb3e0 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 99e6fe243e6 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 30282ee9b8d 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards f711a5a1f8b 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 5279c550d58 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards f952b4d4268 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards f323bbe6f2b 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 9b7839928d5 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards c8eccbfcbd3 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards df89b8f78f5 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards ae35c201dde 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards b1a321a092d 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 02c9be8a6f8 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 7410de29131 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 2bdc44dcbd9 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 8d7475c7906 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 08bd13a93af 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 07815e1e7a6 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 0c3ac80c77e 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 872561bc0e6 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 9400387fb07 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 5904781f60d 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 1c460611863 154: onsuccess: #583: 1: Success after linux: 10 commits discards 51059449943 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 40a37bfb2c8 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 4ec0bf26f50 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 54b488bfa78 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 4da6db06f05 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards ab5a6ce6149 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards a5a6f7c31df 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 67f9ffcbe77 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 66a871d8f39 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards c7eb11abc88 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards b955211d612 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 6beea0369c0 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 9a742f7bc12 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 9cec31fb259 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards deb73647345 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards d8da57ae7a6 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 2cbbcf1312c 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 248827c1808 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards f26a79a41ab 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards dcf1c2a4a0f 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 9f3d26619ab 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards dfe1016f24e 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 98df8d6833e 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards d87f3a2970e 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 1fef2f70a98 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 12f72cbfcc7 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards f2670dc1d65 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 89d4a7463eb 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards a6b5d9c0931 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 3cca3cfa6f5 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 86e66fea02e 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 3982ac57efb 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 8bcceb5615b 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 9915a76a7ab 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards ec5e28d8b9b 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 0e607569d37 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards bbaf9d5c189 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards dbe1581bba2 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 5c61907c2c4 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 67508ae869d 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 612ebfe7b60 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards d83c7b87192 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards b3f2930f28d 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards ac99343e424 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards bf55bc1d383 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 8b4c5e7c2da 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new ad32bcc149f 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new e7feb6b5e1d 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new 3e78a8cf3d8 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new e0473f89a11 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new ee61407aa5b 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 53c1f05b5c4 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 78a8408a822 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new a0f9ab9d722 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 027e5473ea1 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 846e6d3afc6 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 71f083eb315 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 9a12b70e0f2 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new d5c33669f09 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new a5f2a86f23b 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 77fd5516980 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 6abdf98bb43 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new f03f5fbac65 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 6098aff2bce 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new bd84373d473 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 49882686942 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 1248a549936 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 07d894e7407 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 5411b745883 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new ee1fb396b5f 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new baacc180e91 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new f94eda300e0 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 5ffdb15e8b3 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 4d14ec273df 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 900b988c429 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 63a5da07389 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new cba6b0c9142 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 5e9e45067a7 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 5a311711d5f 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new cc234c3a7b7 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 81415749478 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 0ee595cf5f3 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 314618dde2c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 4386f2f2774 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new dd4ba42664d 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 0203051552e 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 25e0c3b54fd 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new d7c89663784 151: onsuccess: #579: 1: Success after binutils: 21 commits new d71f0ecc569 152: onsuccess: #580: 1: Success after gcc: 6 commits new 425c90ab63b 153: onsuccess: #582: 1: Success after glibc: 9 commits new e1d421e9dc0 154: onsuccess: #583: 1: Success after linux: 10 commits new da843ed10e0 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new a149c862437 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 15ceb9ea4f9 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 4fc57bec0b0 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new cce4be96929 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 0265d3baab2 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new e212133871d 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 1f2bbafe064 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 6da37886221 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 63b42fda8af 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 3451fb55ba1 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 6378c26909a 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 18ae577bcaa 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 427a795d32f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new a7280335284 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new f6573196708 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 6a01045b933 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new b51f7994954 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new a00e94388be 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 5bb62f0e6f4 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new e47b1818edd 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new a4746e967da 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new a4360df29d1 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new e3603aa1d66 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 5ef299fc8f8 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new f5d8a4aa9b6 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new de25b185226 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 20bc7c479d3 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new cc8c9163150 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new bfd4a24fbf9 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 9cef45e354e 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 12c76022994 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 818affaa396 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new a2f05c1ae7c 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 4959b47153a 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new fcccfd3d161 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new e4a98029063 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 90e1e136814 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 1fe2307b6a2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new fae00a4d980 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9e55383b72b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 2bc7f3ac3a8 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 274da1cc906 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 3198c8e8d41 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 012728b8f84 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new c6db606f49c 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b6cf4197cf8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new e7d8ca992bf 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 7cfe2476ac8 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 23901bc3153 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 33b16a02ef5 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 43193300853 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 8984e4539fa 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 977847ae29e 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 54cb3f1318b 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 1367a9f5b0c 210: onsuccess: #19: 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 (30959c53f6a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]

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 1732 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 52736 -> 52524 bytes 04-build_abe-gcc/console.log.xz | Bin 236472 -> 236760 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8280 -> 8604 bytes 07-build_abe-glibc/console.log.xz | Bin 235420 -> 237032 bytes 08-build_abe-gdb/console.log.xz | Bin 51076 -> 51316 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3736 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2052 -> 2188 bytes 11-check_regression/console.log.xz | Bin 5844 -> 6012 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- sumfiles/binutils.log.xz | Bin 62180 -> 63020 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100616 -> 100608 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 132048 -> 132056 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 394 insertions(+), 394 deletions(-)