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 d0598251464b 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 8e0a6fe2ad8b 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards a4b6b3fa5230 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards b3a4506cdb16 225: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 4b9c5cd0a3f3 224: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 082d57ce9ee8 223: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 1baecc07993d 222: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards dd53c2c080ba 221: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 6af9538a3274 220: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 047e0e059e23 219: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 3fd6e7e60d73 218: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 712da74ad557 217: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 0bed005b3d6f 216: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards d5ccc730495e 215: onsuccess: #26: 1: Success after binutils: 10 commits discards fcad06b721ef 214: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards 52841cac6bea 213: force: #24: 1: Success after binutils: 2 commits discards d509a4ff6b30 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards e2c6ffee95b8 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 69e156cce647 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 09113a913540 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards ddec2beb23a8 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 5db7d4866368 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards c7e67123d220 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards ddf53c3cf802 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 5bc56a50d57f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards c0ed873fbea5 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 5713bee3e48d 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards a7363e2a8d24 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 01535574613b 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 1a54366ca669 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards a446b2eccccf 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 547bfbb345a3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards f56c8e8b8458 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 9b3f7b37fa85 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 3e1adcf07258 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 964418e8bd3b 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 5120b732f57d 192: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards a139d7af437e 191: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards 295397523679 190: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards ed0ae0bab20a 189: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] discards 924051661a47 188: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 7a7ce3276cbb 187: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] discards cf2282b6d3c3 186: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards b003c28356e6 185: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards e37f535d93fd 184: onsuccess: #614: 1: Success after binutils/gcc/linux/ [...] discards fe877b8c1fdf 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/ [...] discards ece68ef34672 182: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] discards 0135667723d0 181: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards 514760f3b571 180: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards fe12d207316d 179: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards 2c1e88319f25 178: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards 887c5ebbf5a4 177: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards e30b86c44704 176: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards 7dcebad02b72 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/ [...] discards dc063f11ca67 174: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards 11f75ac548ee 173: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards 27e99c9e0427 172: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] discards 9e2075df0583 171: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] discards ec1368632117 170: onsuccess: #599: 1: Success after binutils/gcc/linux/ [...] discards ea8f571d517e 169: onsuccess: #598: 1: Success after binutils/gcc/linux/ [...] discards d98621da9724 168: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards 8cf2558c5cca 167: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards bac60aff09d2 166: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards 4e1c03cb3c5f 165: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards 6ff34a26de58 164: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards e72c87107989 163: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards f58a8ff20c9b 162: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards a1755405f589 161: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] discards ed85d21c1301 160: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] discards b1226dc5149a 159: onsuccess: #588: 1: Success after binutils/gcc/linux/ [...] discards 91fad1f13a12 158: onsuccess: #587: 1: Success after binutils/gcc/linux/ [...] discards 2b908da31ba1 157: onsuccess: #586: 1: Success after binutils/gcc/linux/ [...] discards bfbde6be3f63 156: onsuccess: #585: 1: Success after binutils/gcc/linux/ [...] discards bc8380a6332c 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/ [...] discards 4c8f1e7048c2 154: onsuccess: #583: 1: Success after linux: 10 commits discards 40f16f4be2a2 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 28ae1bc54f1f 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 587f5815180f 151: onsuccess: #579: 1: Success after binutils: 21 commits discards ec9cf3994ba8 150: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] discards d9bb5d184aed 149: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] discards cbfb3c72ef00 148: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] discards a34935f65301 147: onsuccess: #574: 1: Success after binutils/gcc/linux/ [...] discards 89f6c5ba9ec8 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 1 [...] discards b2a3d5b4b2a3 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 2 [...] discards 29a4671bc3d5 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 2 [...] discards b891bc98b4a9 143: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] discards 67b2329beba3 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 4 [...] discards 2847f55f0c19 141: onsuccess: #568: 1: Success after binutils/gcc/linux/ [...] discards 665659384dc0 140: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] discards a1f525482aed 139: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] discards f52aad8bf7f5 138: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] discards bba7ea740bed 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] discards 0db2ed28ca5e 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] discards 98d9f921e35c 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards db5371fa4309 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards fb339f1bc430 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards aac4ea642f55 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] discards beed6f06c593 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] discards f549c00b5b0b 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] discards d03c9733e71f 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] discards 38304092d102 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] new 323429d2f739 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] new 07ebe4e6ef78 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] new 7c736dea59f2 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] new 8cd26953c57a 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new e3ce1941fb28 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new 6c7719d8a7fd 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new 9fa5b0e5b889 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new dd98ca38b9f3 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new 4645fb58bfa8 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] new 8a56dda55774 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] new 7f26143c1cec 138: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] new f2080e09ef84 139: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] new 514cc7598b01 140: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] new c02054cb0bf8 141: onsuccess: #568: 1: Success after binutils/gcc/linux/ [...] new cabe3cb226d5 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 4 [...] new ac56e6f23455 143: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] new b06be7188e3a 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 2 [...] new 5d2466ec7e09 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 2 [...] new 4de6e4f2343b 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 1 [...] new d63f0815bdc2 147: onsuccess: #574: 1: Success after binutils/gcc/linux/ [...] new 243dacba2c52 148: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] new 39d6e5d0336b 149: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] new 6b960f4d161f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] new 1d273d97312b 151: onsuccess: #579: 1: Success after binutils: 21 commits new c38caa2f4051 152: onsuccess: #580: 1: Success after gcc: 6 commits new 0621f105e878 153: onsuccess: #582: 1: Success after glibc: 9 commits new 50a5d47553ef 154: onsuccess: #583: 1: Success after linux: 10 commits new 8485487bc21d 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/ [...] new 1a261f89b2cc 156: onsuccess: #585: 1: Success after binutils/gcc/linux/ [...] new afd3b21eda90 157: onsuccess: #586: 1: Success after binutils/gcc/linux/ [...] new 49afae82bdf2 158: onsuccess: #587: 1: Success after binutils/gcc/linux/ [...] new d29cf53d03eb 159: onsuccess: #588: 1: Success after binutils/gcc/linux/ [...] new 80b76180c241 160: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] new 4cafd6772987 161: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] new 94ddc3267cd8 162: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new da2c9feab6d8 163: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new f477a54bf6da 164: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new d4bb65f53cef 165: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new 6b92b0ffe6f5 166: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new 8b05e708e9c2 167: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new c0550ca8ffbd 168: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 25f6a052992d 169: onsuccess: #598: 1: Success after binutils/gcc/linux/ [...] new b7d3bea60b2e 170: onsuccess: #599: 1: Success after binutils/gcc/linux/ [...] new 2da088fb7c8c 171: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] new a91f41f4a80a 172: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] new f70de0172036 173: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 2c83d78df613 174: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new 40ef5a7102fd 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/ [...] new 8f5c3d82b41c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new 16e54d48da90 177: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new f4a2e749b708 178: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 4490358044d8 179: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new 3ca62f3ea2e4 180: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new f460f3a18355 181: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new a10053b86a30 182: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] new 7ffb00bea6bb 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/ [...] new 4ab292cd4226 184: onsuccess: #614: 1: Success after binutils/gcc/linux/ [...] new 9372fe4153e6 185: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 12fef85f55f2 186: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new 730b28b8604a 187: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] new cff36e47d57d 188: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new 459dd03711cc 189: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] new c8d9dd49964b 190: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 4ef8f3f191db 191: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new f4e229a32546 192: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new 43a7c26ee01b 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new df05211cca3f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new a42cb0107680 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 9147969344bd 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 9fe338162b4f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 28449cbce8c7 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new eaaea742596a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 8a88b8c1df51 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new e6a308fe1e8d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 33591fe27381 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 5b063155c33a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 44eec7b26dc8 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new e0a8c1439b05 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 564178235ad2 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new e33d38400634 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new cc7f9317ea43 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new f2c387c1610a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new b8407dd06f6d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 467126ef9283 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 88edab9f7514 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 954adad20bb1 213: force: #24: 1: Success after binutils: 2 commits new 7e11338d65cf 214: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new 285ee426243a 215: onsuccess: #26: 1: Success after binutils: 10 commits new f7a80d648d50 216: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 062d16ddd786 217: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 11ced40c922c 218: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new eb3d7cc892d4 219: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 846effb2e6e2 220: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 663714ede42b 221: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 5715c2a41009 222: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new ce5f661d64ac 223: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 8ca75d2e9559 224: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new ad76fd4c3e8a 225: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 127e6bdd25a7 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 57e3c2c3cecb 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new d9fe1754d827 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 99ed7db65775 229: onsuccess: #42: 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 (d0598251464b) \ 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 2036 -> 2068 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 48804 -> 49248 bytes 04-build_abe-gcc/console.log.xz | Bin 236820 -> 233740 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8440 -> 8892 bytes 07-build_abe-glibc/console.log.xz | Bin 231984 -> 232616 bytes 08-build_abe-gdb/console.log.xz | Bin 46732 -> 47164 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3768 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2104 -> 2108 bytes 11-check_regression/console.log.xz | Bin 5004 -> 4964 bytes 11-check_regression/results.compare | 10 ++--- 11-check_regression/results.compare2 | 20 +++++++--- 12-update_baseline/console.log | 58 ++++++++++++++--------------- 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 | 49 ++++++++++++------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +++++++++---------- manifest.sh | 36 +++++++++--------- sumfiles/binutils.log.xz | Bin 62988 -> 62224 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100660 -> 100584 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 132232 -> 132328 bytes sumfiles/ld.sum | 7 ++-- 30 files changed, 123 insertions(+), 115 deletions(-)