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 99ed7db65775 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards d9fe1754d827 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 57e3c2c3cecb 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 127e6bdd25a7 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards ad76fd4c3e8a 225: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 8ca75d2e9559 224: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards ce5f661d64ac 223: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 5715c2a41009 222: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 663714ede42b 221: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 846effb2e6e2 220: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards eb3d7cc892d4 219: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 11ced40c922c 218: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 062d16ddd786 217: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards f7a80d648d50 216: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 285ee426243a 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 7e11338d65cf 214: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards 954adad20bb1 213: force: #24: 1: Success after binutils: 2 commits discards 88edab9f7514 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 467126ef9283 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards b8407dd06f6d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards f2c387c1610a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards cc7f9317ea43 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards e33d38400634 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 564178235ad2 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards e0a8c1439b05 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 44eec7b26dc8 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 5b063155c33a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 33591fe27381 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards e6a308fe1e8d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 8a88b8c1df51 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards eaaea742596a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 28449cbce8c7 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 9fe338162b4f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 9147969344bd 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards a42cb0107680 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards df05211cca3f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 43a7c26ee01b 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards f4e229a32546 192: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 4ef8f3f191db 191: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards c8d9dd49964b 190: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 459dd03711cc 189: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] discards cff36e47d57d 188: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 730b28b8604a 187: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] discards 12fef85f55f2 186: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 9372fe4153e6 185: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards 4ab292cd4226 184: onsuccess: #614: 1: Success after binutils/gcc/linux/ [...] discards 7ffb00bea6bb 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/ [...] discards a10053b86a30 182: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] discards f460f3a18355 181: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards 3ca62f3ea2e4 180: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 4490358044d8 179: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards f4a2e749b708 178: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards 16e54d48da90 177: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards 8f5c3d82b41c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards 40ef5a7102fd 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/ [...] discards 2c83d78df613 174: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards f70de0172036 173: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards a91f41f4a80a 172: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] discards 2da088fb7c8c 171: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] discards b7d3bea60b2e 170: onsuccess: #599: 1: Success after binutils/gcc/linux/ [...] discards 25f6a052992d 169: onsuccess: #598: 1: Success after binutils/gcc/linux/ [...] discards c0550ca8ffbd 168: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards 8b05e708e9c2 167: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards 6b92b0ffe6f5 166: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards d4bb65f53cef 165: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards f477a54bf6da 164: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards da2c9feab6d8 163: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards 94ddc3267cd8 162: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards 4cafd6772987 161: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] discards 80b76180c241 160: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] discards d29cf53d03eb 159: onsuccess: #588: 1: Success after binutils/gcc/linux/ [...] discards 49afae82bdf2 158: onsuccess: #587: 1: Success after binutils/gcc/linux/ [...] discards afd3b21eda90 157: onsuccess: #586: 1: Success after binutils/gcc/linux/ [...] discards 1a261f89b2cc 156: onsuccess: #585: 1: Success after binutils/gcc/linux/ [...] discards 8485487bc21d 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/ [...] discards 50a5d47553ef 154: onsuccess: #583: 1: Success after linux: 10 commits discards 0621f105e878 153: onsuccess: #582: 1: Success after glibc: 9 commits discards c38caa2f4051 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 1d273d97312b 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 6b960f4d161f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] discards 39d6e5d0336b 149: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] discards 243dacba2c52 148: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] discards d63f0815bdc2 147: onsuccess: #574: 1: Success after binutils/gcc/linux/ [...] discards 4de6e4f2343b 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 1 [...] discards 5d2466ec7e09 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 2 [...] discards b06be7188e3a 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 2 [...] discards ac56e6f23455 143: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] discards cabe3cb226d5 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 4 [...] discards c02054cb0bf8 141: onsuccess: #568: 1: Success after binutils/gcc/linux/ [...] discards 514cc7598b01 140: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] discards f2080e09ef84 139: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] discards 7f26143c1cec 138: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] discards 8a56dda55774 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] discards 4645fb58bfa8 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] discards dd98ca38b9f3 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards 9fa5b0e5b889 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards 6c7719d8a7fd 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards e3ce1941fb28 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] discards 8cd26953c57a 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] discards 7c736dea59f2 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] discards 07ebe4e6ef78 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] new 22f199f94ab2 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] new 6168f0e42d0e 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] new 13c1f5fb69d9 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new f9776fb81681 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new 17006a57b468 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new 9f1ff68ba708 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new 1b3c0b6e0595 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new 125573b1c816 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] new e8329c098e21 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] new cc13f1fca578 138: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] new 099c55bfa2bf 139: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] new 2fcdf25b1daa 140: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] new 4bcab73039cf 141: onsuccess: #568: 1: Success after binutils/gcc/linux/ [...] new b154c403ba67 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 4 [...] new b72ffac6f353 143: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] new e2add6476414 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 2 [...] new 7c983a11c415 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 2 [...] new b518aeb762a7 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 1 [...] new d0745a1cb20a 147: onsuccess: #574: 1: Success after binutils/gcc/linux/ [...] new 35393579b3e6 148: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] new 3532e84be21c 149: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] new 14f0f6687dd3 150: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] new 76e22c256468 151: onsuccess: #579: 1: Success after binutils: 21 commits new 043126ed2c94 152: onsuccess: #580: 1: Success after gcc: 6 commits new 0ac0fe25e306 153: onsuccess: #582: 1: Success after glibc: 9 commits new b952638ee116 154: onsuccess: #583: 1: Success after linux: 10 commits new b251f1cac34c 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/ [...] new 0cfe09864cfb 156: onsuccess: #585: 1: Success after binutils/gcc/linux/ [...] new e2fba4fc0f9d 157: onsuccess: #586: 1: Success after binutils/gcc/linux/ [...] new 247054d9f070 158: onsuccess: #587: 1: Success after binutils/gcc/linux/ [...] new 049e25622659 159: onsuccess: #588: 1: Success after binutils/gcc/linux/ [...] new 742c01d777d0 160: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] new 9cb87c941b4a 161: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] new 48122ff54279 162: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new 1ecb4c66ba97 163: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new 1378fba720e2 164: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new 262871d3f527 165: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new c1df20fd9a44 166: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new d841a6fb509f 167: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new eb40ffdffd0d 168: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new d9360bd737d8 169: onsuccess: #598: 1: Success after binutils/gcc/linux/ [...] new 2d333530eace 170: onsuccess: #599: 1: Success after binutils/gcc/linux/ [...] new 4cf789236d4f 171: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] new edb742d3c28e 172: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] new 690f58ad55e7 173: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 38e1a70bf834 174: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new 0b667ab9cf8f 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/ [...] new 21c9bc2ce5ac 176: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new fa6b9ca60075 177: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new 39f4294a7bd7 178: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 266996b2b12c 179: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new 37a7d2cf5f9d 180: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new 12bac42690f8 181: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new ce575cd98c33 182: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] new 8b2f9a76dca5 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/ [...] new fcebf0a7d0e5 184: onsuccess: #614: 1: Success after binutils/gcc/linux/ [...] new b8eddc0d3e15 185: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 5a76d4fefc49 186: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new 690365b4f4e2 187: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] new f23243db49be 188: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new 8c1edeb45b3f 189: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] new 484b2d55b8cf 190: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new f5139a0f1a29 191: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new c86d18b08382 192: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new 831f5025cc29 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new af525d9afeae 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 970ebdfff394 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new f8724cba2db8 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new c775d606124b 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 31ecff98df83 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 7f0e62e71c81 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new bde052e13cef 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new e3b0e503cf5e 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 02128da92ef1 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 62cf1f5813d2 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 70fd4086c3e8 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new b0354ccb151e 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 74f88fa1408d 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new b96a103a27b7 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new d2f46b48fcb4 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 336d56976167 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 58ed1166358a 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new da03aa989675 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 2f411c64e828 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new d0735a1159ca 213: force: #24: 1: Success after binutils: 2 commits new 1da4cefcecad 214: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new 3e0468e40c88 215: onsuccess: #26: 1: Success after binutils: 10 commits new aed79887acae 216: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 8890875c36e8 217: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 087f1fc986d2 218: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new d9c1c363aff0 219: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 45aa04b8df46 220: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 0206877c1c15 221: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 6b9836642847 222: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 4d15b35e2022 223: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 270d4009b356 224: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new cfb6c127b395 225: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 4e59ea2aece9 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 6125622e9958 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 9d5460dc1b25 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new c9758f24ccf7 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 62a3f33ef8af 230: onsuccess: #43: 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 (99ed7db65775) \ 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 2068 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 49248 -> 49076 bytes 04-build_abe-gcc/console.log.xz | Bin 233740 -> 235816 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 232616 -> 232532 bytes 08-build_abe-gdb/console.log.xz | Bin 47164 -> 46748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2108 -> 2108 bytes 11-check_regression/console.log.xz | Bin 4964 -> 4480 bytes 11-check_regression/results.compare2 | 18 ++++------- 12-update_baseline/console.log | 46 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 43 +++++++++++---------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++++++----------- manifest.sh | 32 ++++++++++---------- sumfiles/binutils.log.xz | Bin 62224 -> 62360 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100584 -> 100664 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132328 -> 132296 bytes sumfiles/ld.sum | 4 +-- 27 files changed, 90 insertions(+), 107 deletions(-)