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 dcfcac35632b 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards 21b9d0477a43 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards a07bf3f9feee 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 478659b2172e 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards dca9a2274a5b 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards ef21493a9c9e 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards d78323356abd 225: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 0315bc0cac4b 224: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 820622e0d6e6 223: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 12b52ac5df3b 222: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards ad47a0a3c3e4 221: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards cf06a65e29d6 220: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 0530f3fbcc8b 219: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 78e32303d787 218: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 07b6fb62601f 217: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 05dcecb93330 216: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 71603122ec5d 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 7f8763a4e8f9 214: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards 8c90ad5193cf 213: force: #24: 1: Success after binutils: 2 commits discards 5c72beb689bb 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards ddddfc3dd2e1 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 6ce3ee0217eb 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards e9abb230883f 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 8f819d2c6ba3 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 4e388e1e2c79 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 5155898b8e00 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 9b0fd3b0902e 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards f066da4c5c9c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards d1c83f51485c 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards ea51e67b1ce6 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 727e4606b121 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 26edc673b243 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 4eb3bd400afb 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 71624d257bb0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards a6cfd64d4262 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 2a0371429d2e 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 6927f55c5f57 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 0f0e48ba6ff7 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 3d7b4b46f022 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 6c92b9778888 192: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 3f60b4910b07 191: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards e9ff77890d10 190: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 5040c232a3b5 189: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] discards 96f686a7faf0 188: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 5027f6c8bac8 187: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] discards 841516f76ce7 186: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 870ebde88441 185: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards a3ecbe35eab1 184: onsuccess: #614: 1: Success after binutils/gcc/linux/ [...] discards 57189e10aa77 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/ [...] discards 4a2d284dd5ab 182: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] discards 037ee25ab311 181: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards 5d1fe03abe7b 180: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 5bc407d50196 179: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards 47e67c49047b 178: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards 254fb1917ef3 177: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards a7b6c781a5a8 176: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards 28d6d411a7ea 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/ [...] discards 9de83fd4d949 174: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards de1cd7f5b316 173: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards 3bc2ae384d10 172: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] discards c98d550bce1f 171: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] discards 8f48ed0ad4ad 170: onsuccess: #599: 1: Success after binutils/gcc/linux/ [...] discards 957e1a970612 169: onsuccess: #598: 1: Success after binutils/gcc/linux/ [...] discards 78b881260987 168: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards c18fb13ef304 167: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards fc7b75662c6b 166: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards d739b96aeb4c 165: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards b6588f4e55b0 164: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards f2f1e0cbe455 163: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards 29264f223ca1 162: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards 1f00c92af641 161: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] discards 58479c3d9971 160: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] discards e550f40c0c23 159: onsuccess: #588: 1: Success after binutils/gcc/linux/ [...] discards 137aa5638066 158: onsuccess: #587: 1: Success after binutils/gcc/linux/ [...] discards 044547d24a03 157: onsuccess: #586: 1: Success after binutils/gcc/linux/ [...] discards 3d7994b0fefb 156: onsuccess: #585: 1: Success after binutils/gcc/linux/ [...] discards cb58a6c10b1c 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/ [...] discards a46d4ca74292 154: onsuccess: #583: 1: Success after linux: 10 commits discards ed26acec8605 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 71a768d4160f 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 5f075817a779 151: onsuccess: #579: 1: Success after binutils: 21 commits discards bcc19c5f2c17 150: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] discards c530937f2291 149: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] discards fce3537769e6 148: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] discards 639dc29c91eb 147: onsuccess: #574: 1: Success after binutils/gcc/linux/ [...] discards 19d78408dfbf 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 1 [...] discards 9ccd4bb1ccdd 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 2 [...] discards d0bd3bfb54a4 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 2 [...] discards e731ffdb223d 143: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] discards e9c027a6c49e 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 4 [...] discards c76c3246bd22 141: onsuccess: #568: 1: Success after binutils/gcc/linux/ [...] discards 1b8b061f4485 140: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] discards f67b9ad8e978 139: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] discards 57e2620def63 138: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] discards 010e52d0eb9b 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] discards 8920684c9549 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] discards fb8b925b5f1d 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards 63f0712f51f9 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards b5c32d3fcee0 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 1c68e5f469c3 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] discards d89e1f181ab9 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new e048a385a98a 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new 4e19037cc6af 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new 0d07ad2c65d6 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new 17650ba6de54 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new 58537a751fab 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new e4e979611c2f 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] new dd30482b3cba 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] new 8a07da858775 138: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] new e365381c4bb3 139: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] new 1af0d6584a68 140: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] new 80471e34b001 141: onsuccess: #568: 1: Success after binutils/gcc/linux/ [...] new 6431415a8a4c 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 4 [...] new 679df1f6aac8 143: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] new 4033ce19bc8b 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 2 [...] new 086c06cee6f3 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 2 [...] new 543398be649b 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 1 [...] new adbbdfd716b5 147: onsuccess: #574: 1: Success after binutils/gcc/linux/ [...] new d5a729c15084 148: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] new f51c3c978470 149: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] new be1682d0c75f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] new f134063e17dc 151: onsuccess: #579: 1: Success after binutils: 21 commits new 1bcdb444f1ce 152: onsuccess: #580: 1: Success after gcc: 6 commits new 997e01ac4b93 153: onsuccess: #582: 1: Success after glibc: 9 commits new 6e6cccb3d165 154: onsuccess: #583: 1: Success after linux: 10 commits new 8c77badd61f1 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/ [...] new 93f722a2423d 156: onsuccess: #585: 1: Success after binutils/gcc/linux/ [...] new a59f1db0ae50 157: onsuccess: #586: 1: Success after binutils/gcc/linux/ [...] new b9dccb165c82 158: onsuccess: #587: 1: Success after binutils/gcc/linux/ [...] new a976069f733d 159: onsuccess: #588: 1: Success after binutils/gcc/linux/ [...] new 8680dcf0280c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] new d6caa547c7cf 161: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] new fe69a84c407e 162: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new ca5828936640 163: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new 136bacd11014 164: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new 9837fc7e3359 165: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new 3ce23fbf2dfc 166: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new 6b06fe3000f0 167: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new 3d7fe3803891 168: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 0e1da8864740 169: onsuccess: #598: 1: Success after binutils/gcc/linux/ [...] new 33ff075f0f75 170: onsuccess: #599: 1: Success after binutils/gcc/linux/ [...] new 4c63670e663f 171: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] new c0a6c7bbf184 172: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] new c208aa46efc4 173: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 4bb6bd594402 174: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new f2a3fba14c29 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/ [...] new cdb6eed77254 176: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new 7804c9f2d8b5 177: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new aeb9450f2f16 178: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 4acc885a13ba 179: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new 897397def77a 180: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new 38a7ae140651 181: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new 2ef571d1b06b 182: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] new 7721ca510577 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/ [...] new 49ba3c27ff69 184: onsuccess: #614: 1: Success after binutils/gcc/linux/ [...] new 717f9983fc60 185: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 3dfe034cca6d 186: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new 217a5535a8c8 187: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] new 14f15906b420 188: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new 40b2d89304dc 189: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] new 50ab89bd0117 190: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 137f64ac06e1 191: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new 3ce688bb9011 192: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new 6cf6e7932c15 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new f1dc87c4a673 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 156c788b2567 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 3b6fc6428195 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 16c40eca5fa9 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new c472ff3921af 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 5f8e3ddd65bc 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 464ea9e41728 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new c9702b5fcdc6 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 0360c1b5ac83 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 65bee9a2a4f2 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 47381576e002 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new d7196961f974 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 5d97c493d84e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new ec7c6be1724e 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 45b22f2f81bc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new fcf36c6f2dd9 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 30f8dd8b7373 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 1415936fdd58 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new d44d814cb099 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new ef400e834cda 213: force: #24: 1: Success after binutils: 2 commits new 04c12dd6432c 214: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new 85235a2cef41 215: onsuccess: #26: 1: Success after binutils: 10 commits new 8dc1f716df6f 216: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 02962b6394c4 217: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 3420198efcc5 218: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 0a3da242f882 219: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new e6cada9473a8 220: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new c6840c111d72 221: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 2df5d8883a06 222: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 89a6836792e4 223: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 6297a9e30df8 224: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 94102b85de82 225: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 3b88d6c484cc 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new a6e61aa5ca23 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 31d3f55f12f6 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 1b0280870ae5 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 83ea30d629f6 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new a954566b1b85 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new 4050d857f73d 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...]

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 (dcfcac35632b) \ 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 2016 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 49048 -> 50144 bytes 04-build_abe-gcc/console.log.xz | Bin 234760 -> 236360 bytes 06-build_abe-linux/console.log.xz | Bin 8208 -> 8784 bytes 07-build_abe-glibc/console.log.xz | Bin 232668 -> 233332 bytes 08-build_abe-gdb/console.log.xz | Bin 46756 -> 48036 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3792 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2104 -> 3476 bytes 11-check_regression/console.log.xz | Bin 4964 -> 5168 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 68 ++++++++++++++--------------- 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/changes-list-long.txt | 57 ++++++++++++------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++-------- manifest.sh | 38 ++++++++-------- sumfiles/binutils.log.xz | Bin 62052 -> 62184 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100660 -> 100664 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 132312 -> 132348 bytes sumfiles/ld.sum | 4 +- 29 files changed, 115 insertions(+), 116 deletions(-)