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 9b6c1300521 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards d90bcfed047 215: onsuccess: #26: 1: Success after binutils: 10 commits discards d77553c2851 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards ab54db94064 213: force: #24: 1: Success after binutils: 2 commits discards fead459da38 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards d382b228ee7 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards ac60e5490e8 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a8467b7039e 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c940f9526d0 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 2f60c64fdc3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f029ffcc635 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards c079d1d8cd3 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards ea89d52ba1c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards a693e59cba9 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 2beebdbdc5b 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ed20fa9de24 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e8003463b54 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 95c6fa74396 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d1b86c801ad 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 09403c86972 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 0996584e677 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 944f5b06d84 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 3e8edcb3ed6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards fb06ab267bb 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 79a29abc2e7 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 6470713b355 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 1bd37bc9da7 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 1bbc0109245 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards b8e681fc940 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d0ff16c2ad2 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 36ec155e831 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 5b71c84e1c9 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 70b389a8368 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards ac265baffe8 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards edf00aa86e4 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 60df225594c 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 261e67cc004 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards bb2dd342a1f 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 67f14ba6d5f 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 495d701b31b 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 5a722a81669 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards d6708dee7ef 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards d814bfb3bcd 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 3e75720c39e 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards f7565df0f32 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 9b65061a69d 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 407676cf05c 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards a2ee415275e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards abf304c5f87 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards df03567dbc8 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 25cf77eb386 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards cee8b0c29ed 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 759c96fcc54 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 0a48e62847d 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards c3266dc701f 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 5a297b18034 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards ee5d9981226 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 7b421739a80 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 3c67df923c8 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards f00d0c4d365 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 16ac071b552 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 0717f975a2f 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards ce4cfe5a7ba 154: onsuccess: #583: 1: Success after linux: 10 commits discards 44517e9e168 153: onsuccess: #582: 1: Success after glibc: 9 commits discards b2b148027e3 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 35f855fbf6a 151: onsuccess: #579: 1: Success after binutils: 21 commits discards d2d21954643 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 4815d803507 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards c7f77634657 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 57914399350 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 4bcc44d024a 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 0a84ffc39f0 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards d5c76478793 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards d17ae276870 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards a85dc986b12 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 267c0f57dea 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards e186da0cad7 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards ee2f31b2799 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards e781887fdab 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards f729c40a1c9 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 5d32dfcea75 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards f0314f19ef0 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 82d87620918 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 3e2bf7d0883 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards d100b586268 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 060b3850a48 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 8f099a0e785 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 80206000f1e 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards df34782edaf 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards a1eb0a76840 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards b6636aedcab 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 42872226fda 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards fd9ac1fc7b4 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 6034632f3ca 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 351057396af 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards df9fd1b2079 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards e61a4940172 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 5b14621efe0 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 86a401908c9 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 037bb336faf 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards c2bfbfbd2e6 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 451995f7bf2 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 62383428b60 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 68401c8df37 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 16e09c2f304 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 0d2859a21d5 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 9ba979236ca 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new dd00247e80e 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 740f7d2528f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new ad6e0be2c74 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new eb27a776134 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 93ed7686f1c 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 25efdaa46ce 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new d86162fe3e9 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new e5541dea43a 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 6e6215ebc83 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 1971ab238a4 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 8296451eee4 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 139ba3bbfa1 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 250cbaa5cf0 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 3faa03e8871 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 6faa4ef9950 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 2d49d097609 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 218c85bb966 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new f7ca202204a 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 999d74f4c5c 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new a171fdc57eb 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 8f4eb5d33f9 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 8304c7f0923 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new f89241a2949 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 47fe9698d6a 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new a1d8df65f01 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new ca8d626ffdc 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new a1f3fc955fc 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new cc65863d589 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 46c8415d2c4 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new d0b18dc9ac5 151: onsuccess: #579: 1: Success after binutils: 21 commits new 37db674672d 152: onsuccess: #580: 1: Success after gcc: 6 commits new 264704846e1 153: onsuccess: #582: 1: Success after glibc: 9 commits new 19aa6924f85 154: onsuccess: #583: 1: Success after linux: 10 commits new 2fee2974381 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new b8e7c40b3b8 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new a1d3828c2f4 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 21e40db2e05 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 9b163a70051 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 07a1453359e 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new e86adf896cf 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 30a77c2dd05 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 91e955e0c28 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 993eff5a2f7 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new df6ea40ebf1 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new ffd1728e8ce 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 7345086d2f9 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new f4ffab407f6 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 41bc5d102b1 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new da3a1ad1c1f 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new bf33283a4ef 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new c6957ad5c96 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 21f43130e30 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 70659b1bd44 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new cb9a104bf61 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 8ed42dabc27 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new af7ee660b2c 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 84165dd07a0 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 0c06aab21bd 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new f68b5127613 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new b286678b17a 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 676653ce3be 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new b468eb10111 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new ad86c0b0903 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 3162e6d3c4c 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 33fcb45a541 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 540b946f7fa 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new f5a90777563 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 28ea978ab5b 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new a065e5782a1 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 0ab09c82e91 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 284072c1173 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new a789304a9e2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 01c9cd7694f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 35f082a25ee 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 588658a8477 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new faf286e8b48 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 474952f2eba 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 7a871e5fbc0 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 435ac013fae 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 78cdb252b43 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new f4a59ba2363 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0df1b125ba0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new a5eba888bdb 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 51cc47d8479 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 6471cc9f1ae 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 3946e7e7ce0 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 3fa47fba262 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new fde1e3f6e33 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 42eca74e78a 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 7ef36df70e7 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 9c5fe080036 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 2d6cdb45a69 213: force: #24: 1: Success after binutils: 2 commits new 15b05c91d4c 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 8f8eb7c66d9 215: onsuccess: #26: 1: Success after binutils: 10 commits new ad374716eb7 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 6720fdf801a 217: onsuccess: #28: 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 (9b6c1300521) \ 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 1772 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2480 -> 2452 bytes 03-build_abe-binutils/console.log.xz | Bin 49196 -> 48744 bytes 04-build_abe-gcc/console.log.xz | Bin 234440 -> 236332 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8532 -> 9912 bytes 07-build_abe-glibc/console.log.xz | Bin 232952 -> 232884 bytes 08-build_abe-gdb/console.log.xz | Bin 47164 -> 47364 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2108 -> 2116 bytes 11-check_regression/console.log.xz | Bin 5020 -> 4760 bytes 11-check_regression/results.compare | 25 +++-------- 11-check_regression/results.compare2 | 23 +++------- 12-update_baseline/console.log | 68 ++++++++++++++--------------- 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 62380 -> 62800 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100560 -> 100596 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 132136 -> 132192 bytes sumfiles/ld.sum | 4 +- 29 files changed, 76 insertions(+), 100 deletions(-)