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 4050d857f73d 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] discards a954566b1b85 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards 83ea30d629f6 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 1b0280870ae5 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 31d3f55f12f6 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards a6e61aa5ca23 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 3b88d6c484cc 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 94102b85de82 225: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 6297a9e30df8 224: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 89a6836792e4 223: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 2df5d8883a06 222: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards c6840c111d72 221: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards e6cada9473a8 220: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 0a3da242f882 219: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 3420198efcc5 218: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 02962b6394c4 217: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 8dc1f716df6f 216: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 85235a2cef41 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 04c12dd6432c 214: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards ef400e834cda 213: force: #24: 1: Success after binutils: 2 commits discards d44d814cb099 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 1415936fdd58 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 30f8dd8b7373 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards fcf36c6f2dd9 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 45b22f2f81bc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards ec7c6be1724e 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 5d97c493d84e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards d7196961f974 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 47381576e002 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 65bee9a2a4f2 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 0360c1b5ac83 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards c9702b5fcdc6 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 464ea9e41728 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 5f8e3ddd65bc 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards c472ff3921af 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 16c40eca5fa9 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 3b6fc6428195 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 156c788b2567 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards f1dc87c4a673 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 6cf6e7932c15 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 3ce688bb9011 192: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 137f64ac06e1 191: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards 50ab89bd0117 190: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 40b2d89304dc 189: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] discards 14f15906b420 188: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 217a5535a8c8 187: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] discards 3dfe034cca6d 186: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 717f9983fc60 185: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards 49ba3c27ff69 184: onsuccess: #614: 1: Success after binutils/gcc/linux/ [...] discards 7721ca510577 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/ [...] discards 2ef571d1b06b 182: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] discards 38a7ae140651 181: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards 897397def77a 180: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 4acc885a13ba 179: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards aeb9450f2f16 178: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards 7804c9f2d8b5 177: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards cdb6eed77254 176: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards f2a3fba14c29 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/ [...] discards 4bb6bd594402 174: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards c208aa46efc4 173: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards c0a6c7bbf184 172: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] discards 4c63670e663f 171: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] discards 33ff075f0f75 170: onsuccess: #599: 1: Success after binutils/gcc/linux/ [...] discards 0e1da8864740 169: onsuccess: #598: 1: Success after binutils/gcc/linux/ [...] discards 3d7fe3803891 168: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards 6b06fe3000f0 167: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards 3ce23fbf2dfc 166: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards 9837fc7e3359 165: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards 136bacd11014 164: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards ca5828936640 163: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards fe69a84c407e 162: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards d6caa547c7cf 161: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] discards 8680dcf0280c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] discards a976069f733d 159: onsuccess: #588: 1: Success after binutils/gcc/linux/ [...] discards b9dccb165c82 158: onsuccess: #587: 1: Success after binutils/gcc/linux/ [...] discards a59f1db0ae50 157: onsuccess: #586: 1: Success after binutils/gcc/linux/ [...] discards 93f722a2423d 156: onsuccess: #585: 1: Success after binutils/gcc/linux/ [...] discards 8c77badd61f1 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/ [...] discards 6e6cccb3d165 154: onsuccess: #583: 1: Success after linux: 10 commits discards 997e01ac4b93 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 1bcdb444f1ce 152: onsuccess: #580: 1: Success after gcc: 6 commits discards f134063e17dc 151: onsuccess: #579: 1: Success after binutils: 21 commits discards be1682d0c75f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] discards f51c3c978470 149: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] discards d5a729c15084 148: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] discards adbbdfd716b5 147: onsuccess: #574: 1: Success after binutils/gcc/linux/ [...] discards 543398be649b 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 1 [...] discards 086c06cee6f3 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 2 [...] discards 4033ce19bc8b 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 2 [...] discards 679df1f6aac8 143: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] discards 6431415a8a4c 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 4 [...] discards 80471e34b001 141: onsuccess: #568: 1: Success after binutils/gcc/linux/ [...] discards 1af0d6584a68 140: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] discards e365381c4bb3 139: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] discards 8a07da858775 138: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] discards dd30482b3cba 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] discards e4e979611c2f 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] discards 58537a751fab 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards 17650ba6de54 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards 0d07ad2c65d6 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 4e19037cc6af 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new 782aed4a75bb 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new d21f1875629d 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new 99d920b04e90 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new e2de15875aba 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new 79628312ef34 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] new 9153e528d72b 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] new 2602b5dab3ff 138: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] new bb6bae37a3e8 139: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] new c7a119de7f06 140: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] new e52c695a6926 141: onsuccess: #568: 1: Success after binutils/gcc/linux/ [...] new 40e39146f85f 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 4 [...] new 73f0b3270800 143: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] new ee86ba62c033 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 2 [...] new 658ed9d1fef5 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 2 [...] new 67afb1e3dbcc 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 1 [...] new 1cd64afc772d 147: onsuccess: #574: 1: Success after binutils/gcc/linux/ [...] new c0577dae05c2 148: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] new 9b008cd7b771 149: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] new 4fbdf9b5967d 150: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] new 8570ea8e62fa 151: onsuccess: #579: 1: Success after binutils: 21 commits new ed9a0e958c0d 152: onsuccess: #580: 1: Success after gcc: 6 commits new fa455d883226 153: onsuccess: #582: 1: Success after glibc: 9 commits new b0a4881cfbb2 154: onsuccess: #583: 1: Success after linux: 10 commits new ae431a1e6fca 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/ [...] new 82a0dabdf3c0 156: onsuccess: #585: 1: Success after binutils/gcc/linux/ [...] new ab91091372ea 157: onsuccess: #586: 1: Success after binutils/gcc/linux/ [...] new ec758e19f084 158: onsuccess: #587: 1: Success after binutils/gcc/linux/ [...] new 953540b0ebd0 159: onsuccess: #588: 1: Success after binutils/gcc/linux/ [...] new b5c3b807d3e2 160: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] new e9394ab3a9b7 161: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] new 5af4b02a15e7 162: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new fbc6e51f056c 163: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new 706fceb70137 164: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new cc925f6faf74 165: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new a7f3339e0e2c 166: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new 812af054041f 167: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new 8e155d26a9c6 168: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 5fae9004689d 169: onsuccess: #598: 1: Success after binutils/gcc/linux/ [...] new f0be367d81eb 170: onsuccess: #599: 1: Success after binutils/gcc/linux/ [...] new 78e27179772f 171: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] new 7228da0710e6 172: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] new 0bee0801512a 173: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new ea840400d52d 174: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new abf20a0d8b96 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/ [...] new ed9c253e8127 176: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new 3a3a42d5ce1d 177: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new 26a661532371 178: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 7b904a4189f8 179: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new 3ffeb7ada590 180: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new 85a2719dd01d 181: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new 3dd6fb5a7df4 182: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] new 6d3cb11b487c 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/ [...] new 5fbd6afbc743 184: onsuccess: #614: 1: Success after binutils/gcc/linux/ [...] new 08cf09c34c71 185: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 50e2c751af56 186: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new 2e02f2eb5d6c 187: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] new 3a55615b9a8b 188: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new d9136474554f 189: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] new d5b1c332bf9c 190: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 8bf2745f24f3 191: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new c341218caae0 192: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new ca8149db28fd 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new a2a06e50f646 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 4597716d1820 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 12989e18fe51 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 76bee9187582 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new b1dcd7029904 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new bb46336785b0 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new d53d0c2356b6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 4d0a5b3d09c8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 7dec57f6b6bb 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new dea34078062e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 15971e3f6d7f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 5717da28565f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new a60baea6e7f6 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new be3dad1bca05 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 44286e469c06 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new db6f555c0a8d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 472ec66a0cef 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 1646a5d6b979 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 7788c9dc7bef 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 104b41ef4608 213: force: #24: 1: Success after binutils: 2 commits new 623d25b49ef0 214: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new 7fa51f528ca5 215: onsuccess: #26: 1: Success after binutils: 10 commits new f557a924e225 216: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 74bc9b70b584 217: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 9e6acbc04a77 218: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 0bebf4f0da67 219: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 4d51c7f76d54 220: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 13bddfa6ba8f 221: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new d694562ecebc 222: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 4e56b4efb39f 223: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 87231d97400d 224: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 6300598878c1 225: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new a602c6765255 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 6d6ae4ebd605 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 6101662636b9 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 94496d84a705 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new eef20bc017e1 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new bef6c7f06543 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new 4eeba4837f14 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] new 1257f8586e42 233: onsuccess: #46: 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 (4050d857f73d) \ 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 2028 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 50144 -> 49036 bytes 04-build_abe-gcc/console.log.xz | Bin 236360 -> 235156 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8784 -> 8820 bytes 07-build_abe-glibc/console.log.xz | Bin 233332 -> 233132 bytes 08-build_abe-gdb/console.log.xz | Bin 48036 -> 47488 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3760 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3476 -> 2240 bytes 11-check_regression/console.log.xz | Bin 5168 -> 4892 bytes 11-check_regression/results.compare | 10 ++--- 11-check_regression/results.compare2 | 6 +-- 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 | 55 +++++++++++------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++-------- manifest.sh | 38 ++++++++-------- sumfiles/binutils.log.xz | Bin 62184 -> 62312 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100664 -> 100556 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 132348 -> 132292 bytes sumfiles/ld.sum | 4 +- 30 files changed, 118 insertions(+), 121 deletions(-)