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 8a9411c75f 244: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 3df2d79599 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 50374da001 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 8a3d09756e 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0a43d565a1 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 398cba2a4b 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 00378f76c7 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards cb20c0d00f 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 2f4ef10de0 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 37773fb565 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 8e2b2f5f9b 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 990d0aef04 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards c31513f171 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards a97acaa86f 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 8f8a02d159 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 61e4831f2a 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 2bba3677b8 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 7183a48e79 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 0e7899f8a7 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 3b07c842e8 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 33a831a2c0 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 32e6e09cf2 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 78cf88b960 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 9c0b5b8a89 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 064f7447df 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 3bce1fd6e7 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 94135bc5c3 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards c3b41db06d 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 0bd4a77594 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards f3f0e48838 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 486b90b700 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 3dcc623cf8 213: force: #24: 1: Success after binutils: 2 commits discards f2ca01476b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 2b79367a03 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 94cd46d2a6 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards f59018d451 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 3e21b0ec45 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 833d34a82d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards d87232228d 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards dd859c3f17 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 98d41cc764 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards b8b3fe97af 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 3fbb881f00 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f9eca89737 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 0d2f12d578 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards eb0a34dc19 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards b3170d23e5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards a36eec4294 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4514839688 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 28c7613931 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 55c40855c4 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 6f52eee66f 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards d08c158614 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards d66ca29593 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 09de3cdb50 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 626b7738cc 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards 44f495b55f 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards e80d679494 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards a992134d04 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards c032445da7 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards da008d977d 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards a70ceab67b 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 0877973277 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards d26f721b9b 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards db5498ac6e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 7e856f6b93 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 787439a098 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 73ebc1c407 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 74a2cf2140 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 498bbf2e57 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards b86d879a19 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 35ff3e3489 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards b7424e9804 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 7bca46d216 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards c6d4c492cf 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 66ee325176 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 55f18433d3 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 70436f10de 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards cce9219706 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards b85ec9aeb7 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 99c4ef015c 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards e3725f3e08 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 413b2309a0 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 8be8256de1 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 194226bdb6 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards dc10b8ba72 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards d58c0b33f2 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 7278126480 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 01ba643934 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 67a6464e71 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 562cca4b81 154: onsuccess: #583: 1: Success after linux: 10 commits discards 00af46f5d7 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 2b24168a06 152: onsuccess: #580: 1: Success after gcc: 6 commits discards c6216410ff 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 8d78b2d3ba 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 08d3db46c3 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 3ed73e91b1 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 66d3ed1ecf 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards c254655f8c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 329f291332 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards c9419b24f9 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 0327aa35e0 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 0baae35c96 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 568360e043 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new c5d5841e03 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 0081ca521f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 6c566c3494 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 0f9d009edc 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 207c1ac366 151: onsuccess: #579: 1: Success after binutils: 21 commits new 2739b529cc 152: onsuccess: #580: 1: Success after gcc: 6 commits new 60384422f3 153: onsuccess: #582: 1: Success after glibc: 9 commits new b9c7fedff4 154: onsuccess: #583: 1: Success after linux: 10 commits new 1bf75da0dc 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new b3f581f891 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 6de8609fc5 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new fc83516b97 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 162a8bf2fe 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 49a5d234ef 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 777f1a9dcd 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 2c8f7f62ac 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new fcffee7505 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new faee1b6fa3 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 9af0c53823 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new f1dc25349f 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new d9988f4ee3 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 102167b781 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new b2fc717f30 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 0031962786 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new f0922276ec 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 4be5b3cdd1 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 4b27908834 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new d6e323ddc0 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 440c50da59 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 0675747126 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 10797f6ad7 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 0d6156464f 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 627e2a7fc5 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new f9a92b1caa 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 8a89fe8265 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 3ac680d793 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new cc2df30792 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new 47cd4cb4a0 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 108037dee7 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new edf383f2a4 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 37eb70d953 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new 5368493d87 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new c91cb5a28e 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 49e4af9238 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 5264db53af 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 5ba61248ab 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 37d7bfc418 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new ab1fa5c67c 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new ab6e4a6a91 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new d9ae31f508 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 5df59305b9 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b5b65e72e1 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 7cee1e7e55 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 3478fc51e7 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 9aedd52016 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 5ddb5d2053 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 5473745f86 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 3d3e397580 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new b9deaa7ce2 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 3444912d07 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 3ed6ad1931 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 28c6b12c91 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 6775a9b849 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new ac8356fb0b 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new cbc0552718 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 9f1fa06563 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new cd57c3a1d9 213: force: #24: 1: Success after binutils: 2 commits new edef5d9e23 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 0afb9b2ac2 215: onsuccess: #26: 1: Success after binutils: 10 commits new ea1f0ad520 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 5d5d3c11f6 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 8dcc69ef0c 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new d139091008 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 2feb3abf54 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 019c4a90af 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new d60fbb2142 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 4359045ddf 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 8fd29c8d9d 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 2acdebf8cd 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 636a5769dc 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 5061e3b32e 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 62bd4d9f02 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 122dd0fea8 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 4cf641c927 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 80d1bce8f3 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new cb3e9434a6 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 8a3553d21c 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 6e97d37adb 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new cce7974c35 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new d04efd8d08 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new d1ff5a1701 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 9c6200e28d 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new f468e97df1 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9935f54e1e 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 621c5217e4 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9bb00689bd 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 241b3cde06 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 03eabc8612 244: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 0bb35817ca 245: force: #69: 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 (8a9411c75f) \ 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 2228 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 50120 -> 49928 bytes 04-build_abe-gcc/console.log.xz | Bin 236604 -> 236400 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8952 -> 8952 bytes 07-build_abe-glibc/console.log.xz | Bin 233040 -> 232592 bytes 08-build_abe-gdb/console.log.xz | Bin 46604 -> 46532 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3860 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3072 -> 3004 bytes 11-check_regression/console.log.xz | Bin 1628 -> 1600 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.regressions | 8 +++--- 11-check_regression/trigger-bisect | 4 +-- 12-update_baseline/console.log | 42 ++++++++++++++--------------- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 +++--- mail/results.regressions | 8 +++--- manifest.sh | 8 +++--- results | 8 +++--- sumfiles/binutils.log.xz | Bin 62016 -> 62456 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100576 -> 100632 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132344 -> 132344 bytes sumfiles/ld.sum | 2 +- 27 files changed, 53 insertions(+), 53 deletions(-)