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 c9b7d9a4fab 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 5a85943cf94 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 220a5b02396 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 8f8b0db5625 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 426bbc5b95f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 598ee26624e 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 99a497bae3a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 75abfec0733 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 016291a4b72 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ebcdcb665ba 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards eecacf03345 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards aecb66fb00e 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards c47f3ec44b4 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 52f76410fd0 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c36f4a1deaf 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 2546f04860b 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 6b874608737 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards a4e6177844d 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 8853648fd70 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 3a9656da87e 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards f74d3e0c5f0 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards e94c2a8af29 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards bb414ffb315 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards eaec59cfddb 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 48c3ca0e7cc 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 8a3c771e9f7 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 05c5d7915c2 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e96b0bfe382 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards b1bd415a98d 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 9a23a71c1d8 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 8eb2adad6a8 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards c0b7091b634 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 73668ad9374 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards c90645bfc32 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 792bf02a3aa 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 35b014375f8 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards d59745fb529 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 507c3532de2 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards bda039db4af 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards a69c68df95e 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards ffc837004f7 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 3fe28bae502 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards a5158a5bdfc 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 2c23e226be2 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 6a9304df195 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards b4cdabf4544 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 1f9080a83e3 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 28542926316 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 62cfab36f62 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards dc4a2448788 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 7577f5a134b 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 6bacc961dc4 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 904ae52a996 154: onsuccess: #583: 1: Success after linux: 10 commits discards 6896c488485 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 006e763a021 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 7e5727bc93e 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 0b1b8315b3b 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards cb5c49d383e 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 3026ef2e3c6 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 498acae4e34 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards e87272a1129 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 962cf3d9822 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards ce2a5eb8a14 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 7512a7d8a36 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 2735448ec84 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards c41237835f2 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 43668707fbf 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 6c9b79be623 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 4eff40a6924 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 0a81664182a 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards df64ac685ce 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 8248c16ea7f 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards de4a41b662e 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 523453c6b85 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards deaa9b8ad9d 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards f676b8efe37 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards f182caa65a9 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards eeb400a333a 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards abbf225d5aa 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 014081e7532 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 97e56b93686 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards df45ae90f25 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 53ae99ad467 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards fc381bfbbd9 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 6578578ab4b 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 1e31b4ef302 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards ff05c194e2e 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 2431f74cb52 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 4f6615b5094 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 82249692a39 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 2241c9353f2 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 31f9b52d9d8 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 6a2c59aa899 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 0c7eac23cbc 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 8377febc3b2 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 3e74480737a 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 4e97af2d21a 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards 044ebec5132 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards 75436205c15 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 4a6588b9ba2 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards 383d0cef44d 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new 450b7889fbd 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new bef0e46ea21 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new 94f4b2241b7 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new f2c1d365fbd 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 9c9d7ff99f5 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 6bcbadcb6b9 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new bc2c96093f0 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 6029412f4cb 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 86419cc7844 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new d1fff2205b0 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new d1442649d9b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 8740b38c9e7 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new f6f4b17ac99 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 2142c9a4563 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 4b40a63dcd1 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new e2447aea99b 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 1e7e955effd 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 4785040ba1d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new a8f621e09c0 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 7dbc0cd6e8a 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 866b83fa6d4 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new f661cd76292 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 0fce4fac5cc 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 200d96e9b3f 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 8faebafde15 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 08c58b0ab48 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new a783557ce91 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 3e4f1b84249 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 3742b4961b7 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 8e8e90bcf9f 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 1adf39bfb7f 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 38ae7c3de8a 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 3b559f6107f 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 59e76622dcd 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new af0270ce2fd 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new e3fca0838e9 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new a2f861d372d 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 4c2b1f9b605 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 2c02c4351da 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 031bd6c5f82 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 164480ecb36 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 8dde6f57abf 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 4ab1133519b 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new e2d4c5a2aef 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new beffbad45cc 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 84ef1f4dac7 151: onsuccess: #579: 1: Success after binutils: 21 commits new 1fd3c6fc8df 152: onsuccess: #580: 1: Success after gcc: 6 commits new 5305838fd96 153: onsuccess: #582: 1: Success after glibc: 9 commits new eac6fb1cc42 154: onsuccess: #583: 1: Success after linux: 10 commits new c5244978479 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 954ab0c6176 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new ac105d22e80 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new f064601a759 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 8f8bc8aa3ed 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 0363e5b8d9c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 8336218aa20 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 74e4fb86591 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 99f7bf398a0 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 3f6f8deda51 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 2fe494577a6 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 869bb821cf8 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 060b88f9bdc 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new b1ff51fdec6 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 6ec3b2e73ad 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 2da6ba74db3 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 0031bd76216 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 20b8163f5d0 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 308608b6226 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 4333aa2fe84 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 439b6908547 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new d2c8184100d 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new d4c30ed109b 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 1775a87e0db 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 20af5999111 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new cd38557b641 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 822e21b0ce0 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new cb7fee146bf 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 9805fc2550a 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 9bd97b78d11 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 53e580b3fc3 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new a8fbbb376eb 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new cb2ac84ffef 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new a3ddf1b074c 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 2f321746d36 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new c3565bf5389 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 6496d304f17 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 5eb567a6118 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 6665d74fa9a 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 86513d9c473 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 952a1e8a5da 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 52bd1cf031c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 79820e6fb0e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 4615957fbca 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new d024d0f9297 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new dcfc71d1245 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 34b68231f1d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b3db5b94cc3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b7f5c928f0b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 91e045c875a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 371daa63614 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 3ed85e5f5be 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 459173b8e7b 207: onsuccess: #16: 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 (c9b7d9a4fab) \ 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 1736 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 52920 -> 52612 bytes 04-build_abe-gcc/console.log.xz | Bin 236256 -> 236128 bytes 06-build_abe-linux/console.log.xz | Bin 9604 -> 8700 bytes 07-build_abe-glibc/console.log.xz | Bin 236388 -> 236060 bytes 08-build_abe-gdb/console.log.xz | Bin 51128 -> 50908 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3792 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2044 -> 2036 bytes 11-check_regression/console.log.xz | Bin 5828 -> 6384 bytes 11-check_regression/results.compare2 | 34 +++++++++++++++++++---- 12-update_baseline/console.log | 42 ++++++++++++++--------------- 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 | 36 ++++++++++++------------- sumfiles/binutils.log.xz | Bin 62864 -> 62476 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100648 -> 100544 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 133520 -> 132000 bytes sumfiles/ld.sum | 23 +++------------- 28 files changed, 83 insertions(+), 76 deletions(-)