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 459173b8e7b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 3ed85e5f5be 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 371daa63614 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 91e045c875a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards b7f5c928f0b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards b3db5b94cc3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 34b68231f1d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards dcfc71d1245 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards d024d0f9297 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 4615957fbca 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 79820e6fb0e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 52bd1cf031c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 952a1e8a5da 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 86513d9c473 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 6665d74fa9a 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5eb567a6118 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 6496d304f17 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards c3565bf5389 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 2f321746d36 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards a3ddf1b074c 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards cb2ac84ffef 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards a8fbbb376eb 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 53e580b3fc3 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 9bd97b78d11 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 9805fc2550a 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards cb7fee146bf 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 822e21b0ce0 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards cd38557b641 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 20af5999111 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 1775a87e0db 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards d4c30ed109b 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards d2c8184100d 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 439b6908547 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 4333aa2fe84 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 308608b6226 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 20b8163f5d0 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 0031bd76216 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 2da6ba74db3 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 6ec3b2e73ad 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards b1ff51fdec6 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 060b88f9bdc 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 869bb821cf8 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 2fe494577a6 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 3f6f8deda51 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 99f7bf398a0 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 74e4fb86591 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 8336218aa20 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 0363e5b8d9c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 8f8bc8aa3ed 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards f064601a759 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards ac105d22e80 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 954ab0c6176 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards c5244978479 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards eac6fb1cc42 154: onsuccess: #583: 1: Success after linux: 10 commits discards 5305838fd96 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 1fd3c6fc8df 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 84ef1f4dac7 151: onsuccess: #579: 1: Success after binutils: 21 commits discards beffbad45cc 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards e2d4c5a2aef 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 4ab1133519b 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 8dde6f57abf 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 164480ecb36 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 031bd6c5f82 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 2c02c4351da 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 4c2b1f9b605 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards a2f861d372d 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards e3fca0838e9 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards af0270ce2fd 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 59e76622dcd 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 3b559f6107f 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 38ae7c3de8a 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 1adf39bfb7f 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 8e8e90bcf9f 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 3742b4961b7 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 3e4f1b84249 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards a783557ce91 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 08c58b0ab48 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 8faebafde15 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 200d96e9b3f 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 0fce4fac5cc 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards f661cd76292 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 866b83fa6d4 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 7dbc0cd6e8a 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards a8f621e09c0 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 4785040ba1d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 1e7e955effd 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards e2447aea99b 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 4b40a63dcd1 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 2142c9a4563 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards f6f4b17ac99 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 8740b38c9e7 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards d1442649d9b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards d1fff2205b0 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 86419cc7844 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 6029412f4cb 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards bc2c96093f0 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 6bcbadcb6b9 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 9c9d7ff99f5 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards f2c1d365fbd 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards 94f4b2241b7 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards bef0e46ea21 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new c4cb1afe125 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new 9df44a0df2b 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 6adfa438e91 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new d2db057d238 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 4391a309789 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new e7d8b325b27 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new af5fbbd19a3 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 65a1068b6d6 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new bc1fff5f29e 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new d7073913fd4 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 7c9eda03779 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 5add9c5d2d7 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 86bfd3554ca 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 891872ccb91 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 3623aa849bb 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new a78a50bd99f 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 718c4f8954f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 3c9faa675c9 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 517bd210ca9 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 1c4205056c0 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 702f30c0112 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new c3f572b500a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 2af525a9d5a 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 01ed1193885 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new f6bcc72b9c2 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new efb3f58b360 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 04319bfe394 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 83b88f524ca 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 4dffefade76 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new abcf6ad0a5d 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new f8a32ffd4b3 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 29dacffa194 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 70efe845e83 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 0b0845085ac 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 6853f78a745 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 2f5c038cf8b 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 240cf542971 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 9572eae5a4d 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 346a619002b 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new a402c66f25c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new d203129f89e 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 40e5d3368f0 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new b925a738df5 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new f184e94db79 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 8d0b54c06df 151: onsuccess: #579: 1: Success after binutils: 21 commits new c8052f97eda 152: onsuccess: #580: 1: Success after gcc: 6 commits new efc38d18cb3 153: onsuccess: #582: 1: Success after glibc: 9 commits new 7434a01274c 154: onsuccess: #583: 1: Success after linux: 10 commits new 580a445b327 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 9e42881c2cb 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 45d525219d0 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 53184e7fc74 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 42c483d492a 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new f7371b70b74 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new b7c22281f50 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 710b9134cd4 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new aee28b0c1ab 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 3e5dda9bac2 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new f5f929503b4 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 773c3dab82f 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new af28551342e 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new dbf41858fdd 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 4f96512cb92 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new fd4ce81e609 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 0343ae824c5 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 26f9c263a01 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 51048af6d41 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 3a5614a80b4 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 95a965c491c 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 2cfd1d555d8 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 92692fcc86b 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new e5605dced81 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new cbf3198b765 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 29b34a8ecd1 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 9da29446b41 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new bcd43f2367f 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new e486259d9ed 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 07386f28f61 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 374839e9518 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 8f2f83ae64c 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 5f24001bd4d 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new cfed9471c62 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 70d800b3c0a 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new ec2f9a9ebb2 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 75f22917cd6 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 66af982d494 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new d1f12adccab 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4db53a884c9 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9e77b248b66 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 20e35cb65e0 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 315a285b91f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 55ee55fcbb3 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 89f8de6fe45 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new fc32a6f0bb6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 86b5669f916 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 9f0bad0b621 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new f3c20a90888 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 51580484c89 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 69031d3b3d8 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 8bbd69bd96c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new c7b7fce7de3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 28ccaa0aa4e 208: onsuccess: #17: 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 (459173b8e7b) \ 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 1792 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52612 -> 52632 bytes 04-build_abe-gcc/console.log.xz | Bin 236128 -> 236388 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8836 bytes 07-build_abe-glibc/console.log.xz | Bin 236060 -> 237276 bytes 08-build_abe-gdb/console.log.xz | Bin 50908 -> 50516 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3748 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2036 -> 2028 bytes 11-check_regression/console.log.xz | Bin 6384 -> 5756 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 36 +-- 12-update_baseline/console.log | 64 +++--- 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 | 32 +-- sumfiles/binutils.log.xz | Bin 62476 -> 62820 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100544 -> 100620 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 132000 -> 131984 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 406 insertions(+), 430 deletions(-)