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 82e5cb4afd 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards cce5d46bb8 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards e81b6a8692 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 55591dfb99 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards eeb2bd0c8f 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 040240ad3d 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 39e5b717dc 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 2876191fe8 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards b2e855f87e 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 43e8c0ba1e 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1a4561b97f 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 496eae0edd 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 0db3e58492 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 43decccef9 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 7f373a8a95 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 121f2471e9 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 52b6abf3b9 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 1433fa18a7 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 23132dc147 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards ca14037e01 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 82d19be59e 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 51350e4574 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 130080b5ff 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards d944736cd3 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards d5f05eb858 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 9b2930acff 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 2c126c3743 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 6a9d428314 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 5fa48545b2 215: onsuccess: #26: 1: Success after binutils: 10 commits discards a48e0c7ca8 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 8e7a6372c0 213: force: #24: 1: Success after binutils: 2 commits discards 5744b45fca 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 18c1dc4f8d 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards f2ecc8ea53 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards e552e253da 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 69c98ed286 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 17d940ba98 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 4b080c673f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards a1193d9b5b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards afdd0d1d06 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 1688e250d0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards ebb3e73b1a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards d7e9239a2a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 3561c3949a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards cc621bd3cf 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 68246e81df 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 5378f123d2 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards e0f326bb0c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 607ac5e5fa 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 0302295643 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 7e2954f799 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 0386ea237a 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 7d4510b20b 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 654e5abbae 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 82fde81bc2 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards df73088f55 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 8256880019 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards 1a5e9f41ad 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 4c51adfcd3 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards ccd1485c95 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards ccf4dfbb94 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards ae05ca0e3e 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 874d506e49 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 9e3a9abdb8 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards bdd18100cd 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards a4de8b8ca9 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards a7d9085c2c 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 71b8d686b4 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards da6047524f 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 8bfbbc6e58 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 61e8397f56 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards a4e872998a 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 1ca1f619ea 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards a68c36b650 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards c65f82292d 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 78ac2b4812 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards bc1bff2e77 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 44df1c7d7b 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards be60b70530 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 96d2132504 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards e6d9920d73 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 697202a16a 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards c303cf64cd 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards d9b1542b89 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards fddb970158 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 3fa7d860ce 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 00f62df265 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 0d2496d01b 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 94683d4bb3 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 9d6afa7e50 154: onsuccess: #583: 1: Success after linux: 10 commits discards 70d4add427 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 70e094bba1 152: onsuccess: #580: 1: Success after gcc: 6 commits discards f0541a54a8 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 0e466b8350 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 90f9f62064 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 00eb590df9 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards fb5030b43e 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 8035946959 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards a35e9115d4 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards 35ca02f27c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards b3c14cbe8b 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new a9c498437e 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new c9419b24f9 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 329f291332 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new c254655f8c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 66d3ed1ecf 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 3ed73e91b1 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 08d3db46c3 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 8d78b2d3ba 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new c6216410ff 151: onsuccess: #579: 1: Success after binutils: 21 commits new 2b24168a06 152: onsuccess: #580: 1: Success after gcc: 6 commits new 00af46f5d7 153: onsuccess: #582: 1: Success after glibc: 9 commits new 562cca4b81 154: onsuccess: #583: 1: Success after linux: 10 commits new 67a6464e71 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 01ba643934 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 7278126480 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new d58c0b33f2 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new dc10b8ba72 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 194226bdb6 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 8be8256de1 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 413b2309a0 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new e3725f3e08 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 99c4ef015c 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new b85ec9aeb7 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new cce9219706 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 70436f10de 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 55f18433d3 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 66ee325176 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new c6d4c492cf 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 7bca46d216 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new b7424e9804 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 35ff3e3489 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new b86d879a19 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 498bbf2e57 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 74a2cf2140 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 73ebc1c407 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 787439a098 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 7e856f6b93 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new db5498ac6e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new d26f721b9b 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 0877973277 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new a70ceab67b 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new da008d977d 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new c032445da7 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new a992134d04 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new e80d679494 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new 44f495b55f 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 626b7738cc 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 09de3cdb50 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new d66ca29593 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new d08c158614 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 6f52eee66f 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 55c40855c4 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 28c7613931 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 4514839688 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new a36eec4294 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b3170d23e5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new eb0a34dc19 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 0d2f12d578 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f9eca89737 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 3fbb881f00 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new b8b3fe97af 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 98d41cc764 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new dd859c3f17 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new d87232228d 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 833d34a82d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 3e21b0ec45 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new f59018d451 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 94cd46d2a6 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2b79367a03 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new f2ca01476b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 3dcc623cf8 213: force: #24: 1: Success after binutils: 2 commits new 486b90b700 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new f3f0e48838 215: onsuccess: #26: 1: Success after binutils: 10 commits new 0bd4a77594 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new c3b41db06d 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 94135bc5c3 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 3bce1fd6e7 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 064f7447df 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 9c0b5b8a89 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 78cf88b960 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 32e6e09cf2 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 33a831a2c0 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 3b07c842e8 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 0e7899f8a7 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 7183a48e79 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 2bba3677b8 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 61e4831f2a 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 8f8a02d159 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new a97acaa86f 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new c31513f171 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 990d0aef04 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 8e2b2f5f9b 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 37773fb565 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 2f4ef10de0 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new cb20c0d00f 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 00378f76c7 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 398cba2a4b 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0a43d565a1 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8a3d09756e 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 50374da001 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 3df2d79599 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 8a9411c75f 244: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...]

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 (82e5cb4afd) \ 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 2176 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 49896 -> 50120 bytes 04-build_abe-gcc/console.log.xz | Bin 236504 -> 236604 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8904 -> 8952 bytes 07-build_abe-glibc/console.log.xz | Bin 235272 -> 233040 bytes 08-build_abe-gdb/console.log.xz | Bin 46728 -> 46604 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3888 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3024 -> 3072 bytes 11-check_regression/console.log.xz | Bin 1604 -> 1628 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.regressions | 8 +++--- 11-check_regression/trigger-bisect | 4 +-- 12-update_baseline/console.log | 44 ++++++++++++++--------------- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 +++--- mail/results.regressions | 8 +++--- manifest.sh | 8 +++--- results | 8 +++--- sumfiles/binutils.log.xz | Bin 62476 -> 62016 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100592 -> 100576 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132300 -> 132344 bytes sumfiles/ld.sum | 2 +- 27 files changed, 54 insertions(+), 54 deletions(-)