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 0dca3152a74 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards bacf11875cc 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 2433219c74f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards fa61a935cc7 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 89a19e4fece 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 1f335a063a9 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 2badad06c5c 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 810a4da60c0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 27a5d93a408 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 9bc3b18d392 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 8a2a9773f14 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 53b3bbf70e2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 04ddc021d8f 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 11ff1455224 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards af04b302808 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards fd4525b3d39 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards e42fdc2f2ad 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 05629d3a6ca 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 035c597a208 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 411f5fec2d9 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards cd0dbe4fc25 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 2c62a170e3f 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 36cbc71e51c 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 9eb9bc6c5e0 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 55c5f1d9ddc 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards a9c5ea2e50b 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 7c761c1d931 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards f44683bf0a2 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 3c2ac67109e 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 338f4728fe2 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 4a8ba7025a8 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards df53142765a 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 18025caea88 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 23985f13b86 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards b96461162b8 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards b1fefcde5ce 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards d229d037c1e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 1b8893c8c97 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 2ec67b97157 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 89c0ef43746 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards bbbbb1cf57b 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 01e40038aa1 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 30f675affcb 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 96768b35f91 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards ead9512431e 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 1771cd75277 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 8ebbb239f0b 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards de57c70f219 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 8079171de5b 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 15bda6c1e56 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards d1c32b6d0f4 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 6ce31608e7a 154: onsuccess: #583: 1: Success after linux: 10 commits discards 34137d5bf30 153: onsuccess: #582: 1: Success after glibc: 9 commits discards e9c7b4b8868 152: onsuccess: #580: 1: Success after gcc: 6 commits discards f5587d3d680 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 02e599c0c7c 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 2b9b18fcc8d 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 87c1e31151f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards e59444d394f 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards d5d8364be35 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards b21babf4e50 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards a8717ac8c7f 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 24f16ad4b2d 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 6125db952a2 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 490e0cd87b3 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards f2ab6a7e360 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 38e7bb65c95 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards f5f3906554a 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards f34a4484826 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 6aee9cf7213 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 00a45bf2185 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards f8ef35a1e8f 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 99db46537a3 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 538e6f989f6 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards ce5e5fcf52e 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 17f7fd549c0 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 10061d68454 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 20cea35f6e9 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards adecad14266 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards ab02b668af1 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 6bea3256b9b 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards cf8bca26a1b 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards a87673a15b7 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 6e6591a1532 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards c3b360f169e 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 154c3c50180 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 7404cb45a73 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 7d65bce7600 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards b10c3f91797 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 53fa6284a90 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards d720a6fb36d 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 195582f7bae 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 83533a8d0a4 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards b1c64bcd59c 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 66cac8a8f9d 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 90b7da7343c 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards 930b4de4734 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards ec7f0a2bc47 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 94cbcf91eba 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards d4915905f4f 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] discards a42644c04c1 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new 38a9872fd0c 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new 383d0cef44d 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new 4a6588b9ba2 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new 75436205c15 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 044ebec5132 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 4e97af2d21a 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 3e74480737a 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new 8377febc3b2 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 0c7eac23cbc 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 6a2c59aa899 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 31f9b52d9d8 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 2241c9353f2 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 82249692a39 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 4f6615b5094 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 2431f74cb52 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new ff05c194e2e 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 1e31b4ef302 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 6578578ab4b 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new fc381bfbbd9 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 53ae99ad467 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new df45ae90f25 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 97e56b93686 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 014081e7532 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new abbf225d5aa 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new eeb400a333a 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new f182caa65a9 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new f676b8efe37 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new deaa9b8ad9d 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 523453c6b85 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new de4a41b662e 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 8248c16ea7f 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new df64ac685ce 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 0a81664182a 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 4eff40a6924 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 6c9b79be623 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 43668707fbf 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new c41237835f2 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 2735448ec84 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 7512a7d8a36 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new ce2a5eb8a14 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 962cf3d9822 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new e87272a1129 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 498acae4e34 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 3026ef2e3c6 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new cb5c49d383e 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 0b1b8315b3b 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 7e5727bc93e 151: onsuccess: #579: 1: Success after binutils: 21 commits new 006e763a021 152: onsuccess: #580: 1: Success after gcc: 6 commits new 6896c488485 153: onsuccess: #582: 1: Success after glibc: 9 commits new 904ae52a996 154: onsuccess: #583: 1: Success after linux: 10 commits new 6bacc961dc4 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 7577f5a134b 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new dc4a2448788 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 62cfab36f62 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 28542926316 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 1f9080a83e3 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new b4cdabf4544 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 6a9304df195 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 2c23e226be2 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new a5158a5bdfc 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 3fe28bae502 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new ffc837004f7 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new a69c68df95e 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new bda039db4af 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 507c3532de2 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new d59745fb529 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 35b014375f8 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 792bf02a3aa 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new c90645bfc32 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 73668ad9374 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new c0b7091b634 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 8eb2adad6a8 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 9a23a71c1d8 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new b1bd415a98d 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new e96b0bfe382 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 05c5d7915c2 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 8a3c771e9f7 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 48c3ca0e7cc 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new eaec59cfddb 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new bb414ffb315 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new e94c2a8af29 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new f74d3e0c5f0 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 3a9656da87e 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 8853648fd70 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new a4e6177844d 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 6b874608737 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 2546f04860b 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new c36f4a1deaf 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 52f76410fd0 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new c47f3ec44b4 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new aecb66fb00e 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new eecacf03345 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ebcdcb665ba 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 016291a4b72 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 75abfec0733 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 99a497bae3a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 598ee26624e 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 426bbc5b95f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 8f8b0db5625 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 220a5b02396 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 5a85943cf94 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new c9b7d9a4fab 206: onsuccess: #15: 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 (0dca3152a74) \ 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 1752 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 52460 -> 52920 bytes 04-build_abe-gcc/console.log.xz | Bin 236352 -> 236256 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 9604 bytes 07-build_abe-glibc/console.log.xz | Bin 235516 -> 236388 bytes 08-build_abe-gdb/console.log.xz | Bin 51048 -> 51128 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3744 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2036 -> 2044 bytes 11-check_regression/console.log.xz | Bin 6508 -> 5828 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 35 +-- 12-update_baseline/console.log | 40 ++-- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +-- sumfiles/binutils.log.xz | Bin 62736 -> 62864 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100632 -> 100648 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 133516 -> 133520 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 395 insertions(+), 418 deletions(-)