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 1257f8586e 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 4eeba4837f 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards bef6c7f065 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards eef20bc017 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 94496d84a7 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6101662636 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 6d6ae4ebd6 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards a602c67652 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 6300598878 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 87231d9740 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 4e56b4efb3 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards d694562ece 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 13bddfa6ba 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 4d51c7f76d 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 0bebf4f0da 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 9e6acbc04a 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 74bc9b70b5 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards f557a924e2 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 7fa51f528c 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 623d25b49e 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 104b41ef46 213: force: #24: 1: Success after binutils: 2 commits discards 7788c9dc7b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 1646a5d6b9 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 472ec66a0c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards db6f555c0a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 44286e469c 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards be3dad1bca 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards a60baea6e7 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 5717da2856 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 15971e3f6d 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards dea3407806 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 7dec57f6b6 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 4d0a5b3d09 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards d53d0c2356 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards bb46336785 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards b1dcd70299 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 76bee91875 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 12989e18fe 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 4597716d18 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards a2a06e50f6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards ca8149db28 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards c341218caa 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 8bf2745f24 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards d5b1c332bf 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards d913647455 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards 3a55615b9a 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 2e02f2eb5d 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards 50e2c751af 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 08cf09c34c 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 5fbd6afbc7 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 6d3cb11b48 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 3dd6fb5a7d 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 85a2719dd0 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 3ffeb7ada5 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 7b904a4189 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 26a6615323 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 3a3a42d5ce 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards ed9c253e81 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards abf20a0d8b 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards ea840400d5 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 0bee080151 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 7228da0710 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 78e2717977 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards f0be367d81 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 5fae900468 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 8e155d26a9 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 812af05404 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards a7f3339e0e 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards cc925f6faf 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 706fceb701 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards fbc6e51f05 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 5af4b02a15 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards e9394ab3a9 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards b5c3b807d3 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 953540b0eb 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards ec758e19f0 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards ab91091372 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 82a0dabdf3 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards ae431a1e6f 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards b0a4881cfb 154: onsuccess: #583: 1: Success after linux: 10 commits discards fa455d8832 153: onsuccess: #582: 1: Success after glibc: 9 commits discards ed9a0e958c 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 8570ea8e62 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 4fbdf9b596 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 9b008cd7b7 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards c0577dae05 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 1cd64afc77 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 67afb1e3db 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 658ed9d1fe 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards ee86ba62c0 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 73f0b32708 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 40e39146f8 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards e52c695a69 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards c7a119de7f 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards bb6bae37a3 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 2602b5dab3 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 9153e528d7 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 79628312ef 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards e2de15875a 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 99d920b04e 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards d21f187562 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 045b3d4204 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 43eaccd163 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 928567e871 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 188310edf2 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new 07f66bc1e1 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 26a56309de 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 206976d415 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new a181771707 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 60fe9c336a 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 65f3d9b7b0 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new 9148106eca 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new b21447d3fc 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new d2ba39f2b0 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 1040d78083 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new cc1c1e1409 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 64925c2897 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 67fd09786c 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new ea49fb52f0 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 8b94020316 151: onsuccess: #579: 1: Success after binutils: 21 commits new 687593b743 152: onsuccess: #580: 1: Success after gcc: 6 commits new 1df2099f2b 153: onsuccess: #582: 1: Success after glibc: 9 commits new 91493cfc86 154: onsuccess: #583: 1: Success after linux: 10 commits new 0ea394ccaf 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new b511329f84 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 38cfd19ed1 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new aca3bd5222 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 3011b2d6bf 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new f6bd84fddf 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 27cc673f97 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new f10f1d270a 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 927947e913 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 734e35e13a 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 3477191cf9 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new f62d8e6376 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new b004d1e86a 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 4db5b4d2a5 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 40dc488306 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 25e626f6e0 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 94fb335310 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 9db1f7cc54 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 988ce35af7 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 066e273411 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new bac90aae08 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 98fc89805c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 946512c206 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new ea0aa285ad 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 4e8a084b9d 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new c8e4fafc0e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new c721d879ec 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new ba819f6d92 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 96fec44844 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new 22c6cdf346 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 5b058b4aef 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new e653bcea8d 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 9f71ad91d7 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new cac8506f67 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new a1f0de6564 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 25f05ed58a 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 09eb098b9a 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 78f43b2610 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 3e21feb20d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 4c6bf84c7b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 17eda2d286 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 3df6d354ee 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new d94ba8f30a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 1e674a8c0a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 87c1e13fcb 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 0a51bd42ea 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new cbc8dbd9cb 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 2159d425be 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 170436f4f4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new f5762dfa6b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new c1a4747e7a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 12cbb28a95 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 4e1d93b9eb 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new a979cae2d0 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 9c3e8d8ddd 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 56b2f9b94f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 26b9df8b44 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 6216e0bbeb 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 27e0703da9 213: force: #24: 1: Success after binutils: 2 commits new 45d1004cc9 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 579443ddb3 215: onsuccess: #26: 1: Success after binutils: 10 commits new 9d63c3703f 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new d3bdf79ed4 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new d9f5ba4f50 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new a05d34e250 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 7da4813224 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 66003f270d 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 91b193834a 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new bb7aadb197 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 3423bebd4d 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 773e053cd7 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new e550a40d02 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 0c14cca51e 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new b148e203d2 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 4e11de3d95 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 90e50e259b 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 294fc84e1d 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 6ee38f1307 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new d314f143d4 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 0e19f43120 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...]

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 (1257f8586e) \ 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 2076 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 49036 -> 49000 bytes 04-build_abe-gcc/console.log.xz | Bin 235156 -> 234928 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8820 -> 9484 bytes 07-build_abe-glibc/console.log.xz | Bin 233132 -> 232688 bytes 08-build_abe-gdb/console.log.xz | Bin 47488 -> 46876 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2240 -> 2412 bytes 11-check_regression/console.log.xz | Bin 4892 -> 5024 bytes 11-check_regression/results.compare | 8 ++--- 11-check_regression/results.compare2 | 6 ++-- 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/changes-list-long.txt | 56 +++++++++++++++-------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++---------- manifest.sh | 38 ++++++++++---------- sumfiles/binutils.log.xz | Bin 62312 -> 62784 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100556 -> 100604 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132292 -> 132312 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 108 insertions(+), 104 deletions(-)