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 855b3dd410 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 60d123b520 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards fce33d35cf 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 097b4a8735 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards e62a9fa803 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 3d4f08871e 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 608e0a1a60 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 27b2b5abd0 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 0222ae3840 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 54f4c64683 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards f37d2e661e 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 23833dce0c 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 029968810d 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards fbfa5fe787 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 41dd761de8 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 0562c149db 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards c5d0144c87 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 986f379096 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards d5e90a78cf 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards e617598dab 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards b9aa09c998 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 0dc81df90b 215: onsuccess: #26: 1: Success after binutils: 10 commits discards bd1b377d36 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards c6ad5829b6 213: force: #24: 1: Success after binutils: 2 commits discards e6348b63ba 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 4f6afb4c5f 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 0228b10f79 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards a4f345a305 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 04147220b1 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 696f853bc5 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 8359343e46 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards c3bb00e049 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 850c94b83f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 01131fd584 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 0c230f0c47 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 0468ef2100 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards dae7a1ecc9 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b6932e79e9 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards ba2e3b9964 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 6d9b497376 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 7fecda589b 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards eef5077994 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 00e888cdbd 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards d70a5b8d37 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards cf1b11f5b7 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 013d65e773 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 7f4989fa8a 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards e967fd6612 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards f24b3f0e75 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 91f58f9fed 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards cb8e930ad1 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 0a9fc90078 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards d21f8f1e44 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 4db1bee013 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 7e0a184a8e 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards de28b273d9 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 918274dff3 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 71c4b0b62b 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 7affba5982 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 45407460a5 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards c73d8335f4 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 1a484e3690 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 4066c2e242 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards e3dc9578c4 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 6268222a01 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards afc66c42b8 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 643bd89323 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 8ce3539900 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 17b18a8f3a 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 2f277edcf4 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards c71ba2f0be 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 59f2a2a954 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 2fcd745b9a 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 68ff9bccee 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards a3a675ab5a 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 8919cd6808 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 29dd948ca4 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 61a0932cfb 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 8c2466322d 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 834a30f7c5 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 84e24a6dd0 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards eb383c9ce3 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 79425c1328 154: onsuccess: #583: 1: Success after linux: 10 commits discards 7719f3e8ae 153: onsuccess: #582: 1: Success after glibc: 9 commits discards fdebddde0a 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 36b57443c8 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 9b38dab53e 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 3e8b82c57d 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards a41985621f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 81160301ec 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 02107941e1 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards c4380028fe 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards 5d2f8e594f 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 5be897601b 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 25d82b7336 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 9f0f8a7fe4 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards f96d222dbe 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 919285fd13 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 6cb6257065 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards aba9325482 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 189386dd50 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new db000ab422 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new 5dccc09fd2 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 8b4ea04b26 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new bbf53b1b4a 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 25c99a5f29 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new a2baecbf44 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 702551fa91 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new 10d67e54ec 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 1bbc07f2d1 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new f25d00dc9b 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new b70ec1d09c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 060a358ad0 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 64f198ec2d 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 2c760bb415 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 79a07421f2 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 9be5de97b1 151: onsuccess: #579: 1: Success after binutils: 21 commits new e534d0e709 152: onsuccess: #580: 1: Success after gcc: 6 commits new 15db2cf806 153: onsuccess: #582: 1: Success after glibc: 9 commits new 6e4b142196 154: onsuccess: #583: 1: Success after linux: 10 commits new 3d808384c1 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 3dcbb75f8a 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 7ccc883d8f 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new e9c1e539be 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 55f7862856 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 715c30e1dc 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 126061f7b3 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 1d930b8950 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 8465bc3221 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 9677bb3d59 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new c01bcfaa7e 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 9237f06d00 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new b6416b22e7 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new c8c1ddc7a6 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 186537cb30 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 2463c184a6 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new c2a01ecffd 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 5219d7459f 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new dfe0e624f8 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 95fe9f6f70 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 3864edc3ff 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 240b20b828 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new dbd987bb9d 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 0afa52f88e 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 334b48b19f 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new a74990fc10 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new e5f9526156 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 8fde05c0c0 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 0cc1e64844 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new 5b29b3f6c7 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new b28bf55278 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 3330bf4fc3 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 27b8878a30 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new f41cb65286 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 8c1b2f0928 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new eddae5679c 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new d753edc1b4 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 23ab80bdea 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new a522505362 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 8cb2271e2c 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 0951c34148 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new e0af7a9360 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 720cbaac73 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new d1c3911843 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 260af95bae 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 16b6a30c87 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f90544c496 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new ccc3734040 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new a77c72c203 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new e7de30de7c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new f44fb85ae1 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 4a9b775f48 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 088a7bf135 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 2d1ad50a56 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 7cf846938f 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new f8cff9acdb 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new dd9aa451bd 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new bdb34e58af 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 20f88c9787 213: force: #24: 1: Success after binutils: 2 commits new 01502faec9 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 00251fc67c 215: onsuccess: #26: 1: Success after binutils: 10 commits new abfc9dc622 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 273bef5357 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new b9a0aec767 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new b50719f6df 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new b7147f58b5 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 8f485dac63 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 1dd4f1330c 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 828ef28ec0 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 13b03b07f1 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new c94228a08b 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 4fd281688c 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 6fb3c71769 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 6fa177aadd 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new b643123438 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 59d08c73fa 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new a409894937 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new bc79624640 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 9cd5761223 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new f78629e090 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 6574a0f848 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 695ea710f4 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 3cb39bf711 237: onsuccess: #51: 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 (855b3dd410) \ 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 2024 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 48956 -> 49044 bytes 04-build_abe-gcc/console.log.xz | Bin 236776 -> 235936 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8492 -> 8276 bytes 07-build_abe-glibc/console.log.xz | Bin 232268 -> 232472 bytes 08-build_abe-gdb/console.log.xz | Bin 46788 -> 47444 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2164 -> 2176 bytes 11-check_regression/console.log.xz | Bin 4928 -> 4348 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 38 +++++++++++++-------------- 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 | 40 ++++++++++------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++++++++------------- manifest.sh | 32 +++++++++++------------ sumfiles/binutils.log.xz | Bin 62732 -> 62708 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100584 -> 100644 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132320 -> 132324 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 84 insertions(+), 98 deletions(-)