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 e13db95d5de 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 63113f53c51 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards dbd0921534e 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 094e5d36ed7 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 67293ffbfcb 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards e80b354ed44 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards e3d7f25ba8f 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards c9c7a73229b 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 4693ccfd146 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 6f366500606 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 82e7df52d05 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards ce3ac4cb23f 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 2438d367a58 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 70bbbff9d79 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 5c206953085 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards d106770028c 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards b08aec8f65b 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards bec7b3164ab 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 59afc039d22 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards 979951f5344 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards f39f40064e2 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 4c5fa986324 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards 82239ad3ea2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] discards baf2dd9eb6b 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] discards 32bbf629d32 104: onsuccess: #530: 1: Success after gcc: 7 commits discards dc177c791f4 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards c4bc2d087fa 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 0fa44bc76ea 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 5ee7d39158f 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 66703986c65 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards fbc65825f14 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] discards ea84b2ac5f9 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 2e751c3b3e2 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 1f44f17d62a 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] discards d30d11e609d 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] discards cc06f73a23e 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards 8be82464928 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] discards 72622065938 91: onsuccess: #511: 1: Success after linux: 27 commits discards 39a789a6cc1 90: onsuccess: #510: 1: Success after glibc: 5 commits discards a9deb7c1cd3 89: onsuccess: #508: 1: Success after binutils: 12 commits discards cbbfb630dbd 88: onsuccess: #506: 1: Success after linux: 34 commits discards 96dd4899530 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 210eb88ead9 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 53c0b3fbc2d 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 178e4466332 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 05dc8ed47df 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] discards 4d966b4646f 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] discards ddacf1ac3d5 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 6c0726117d7 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards d6e14004f35 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 1fcb182649c 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards b098ed29209 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] discards 5ed091b6600 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] discards 95bf7249c36 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards 5c1fa07814a 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] discards 037a1e95197 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] discards ed76ed94c57 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] discards d010cd55ef2 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] discards 75260e69d90 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] discards 3932c7bff21 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards 2f9df1de860 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] discards d146a73cb49 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards f131ce14746 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] discards df67599f0e0 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] discards 2b67fb84b4d 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards c6059eb837a 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] discards ba3c6e73243 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] discards fdf4296a106 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] discards e4c260b192d 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] discards 3f1c47dbf98 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] discards 81644c9c233 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] discards 8654ae6542e 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] discards 47c38870aa4 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] discards 7584b3fb83f 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] discards a39e6175e35 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] discards 013293f753c 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] discards a60cc796b64 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 55a477f8fa5 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 6808b9b05c5 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 585079ea413 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] discards 6b39108106d 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] discards eef8113cd25 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards f74d0cbc04b 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] discards 622259d9869 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] discards 2832cf90146 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] discards a1060837a91 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] discards a2ff2563bb0 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] discards bf0762f4d24 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] discards e59f61998fe 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] discards b7ec820a2b7 39: onsuccess: #447: 1: Success after binutils: 5 commits discards f54366768dd 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] discards fa477bcd871 37: onsuccess: #443: 1: Success after binutils: 2 commits discards ead5f13715c 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] discards b3537b07094 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] discards 61133f12abe 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] discards 8471751c5e6 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] discards 01dde930fcf 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] discards 6e254a31c60 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] discards 41223ba556f 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] discards ab6ea92b0ec 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] discards 7364ab63119 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] new f03a9bf66ac 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] new b02c0a2a88c 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] new d1bc3030328 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] new 3cfdce437be 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] new 2c9894e42c1 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] new e109459a076 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] new 810e67dc874 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] new 1b59081e932 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] new cd2a4cc66d6 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] new f770ef31530 37: onsuccess: #443: 1: Success after binutils: 2 commits new 1ed044adef3 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] new 4c67cc5392a 39: onsuccess: #447: 1: Success after binutils: 5 commits new 0eb88dc2cef 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] new 94a32a974d5 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] new 10bb9bcf452 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] new 31d256598df 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] new 44d6fb6ad17 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] new c84085ad7d8 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] new 6041d271a83 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new f36c1b80c40 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new d85ef5131a8 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] new 5b8d1cce714 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] new 0f85ddde281 50: onsuccess: #461: 1: Success after binutils: 12 commits new 6e9d6cbcf5a 51: onsuccess: #464: 1: Success after binutils: 6 commits new 77d88a84ebf 52: onsuccess: #467: 1: Success after binutils: 9 commits new d691c33e2eb 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] new 0d50f756413 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] new a1d573cca0c 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] new 32c1a846ac1 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] new 38af421675b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] new 094cc1e1fe8 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] new 74d8b2d82c0 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] new 07e2aca85ab 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] new 9536a312f65 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] new 856e6506e77 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] new 3841d96cd09 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] new dc5053d6092 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new e76f894304c 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] new 6c7fd5bcf51 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] new 26a973c06e5 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new 388603cc66b 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] new 5f21d6b7308 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new 9f686243bd1 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] new 0196c034d74 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] new dcd0f0a5a98 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] new 68f1c3a962e 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] new 0a44ad45e40 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] new a59915b2959 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new 475588c82c3 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] new 37d3fd1eb53 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] new c26e69775c0 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new 3c1d25a400c 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new e9759394596 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new fb1cd0588f1 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 4f49fb70324 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] new f8b991eefe5 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] new e4aed33110a 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new 91e6334772a 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 37088fa76ed 86: onsuccess: #503: 1: Success after binutils: 12 commits new 47ff28d2415 87: onsuccess: #505: 1: Success after glibc: 7 commits new 250c4318e1a 88: onsuccess: #506: 1: Success after linux: 34 commits new eb6027ae77a 89: onsuccess: #508: 1: Success after binutils: 12 commits new 9123a311fba 90: onsuccess: #510: 1: Success after glibc: 5 commits new 5c36cfbdc2f 91: onsuccess: #511: 1: Success after linux: 27 commits new a911ba249f1 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] new 0426eca7439 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new c98bed07a96 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] new 4ebeb85eb03 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] new 13cb11ba860 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new fddf108d1be 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new bed41f5914f 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] new 649dd48cf5c 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 7b912fbba60 100: onsuccess: #521: 1: Success after binutils: 10 commits new e2696d7b30d 101: onsuccess: #524: 1: Success after binutils: 2 commits new 10d31f93603 102: onsuccess: #527: 1: Success after binutils: 5 commits new 9226bd359ea 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new 2efe3a59af5 104: onsuccess: #530: 1: Success after gcc: 7 commits new 54b52327dc8 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new ac6a59ac20c 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new 2c35bfcad76 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new b0c24aba53e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new e6f4224e1c4 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 62001339582 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 5d672d11162 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new fc70f18f031 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new b79d6566ec8 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new ca4d9145bff 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 8d6e7598256 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 118c3b94aaf 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new db28f693044 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 54d36940187 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 8025582d77c 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 4f0a600fe5b 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new f4fddf5e40f 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new e4b41b51b4d 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new b896d0247d3 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 51b0b522aaa 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 2802c371ba1 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new b8911df6dd9 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 3d1f97d28c4 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new abc92ec2ce4 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 7644fa5b624 129: onsuccess: #556: 1: Success after binutils/gcc/linux/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 (e13db95d5de) \ 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 1716 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 52400 -> 52248 bytes 04-build_abe-gcc/console.log.xz | Bin 235196 -> 233660 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8752 -> 8300 bytes 07-build_abe-glibc/console.log.xz | Bin 236420 -> 235280 bytes 08-build_abe-gdb/console.log.xz | Bin 51600 -> 50928 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2092 -> 2164 bytes 11-check_regression/console.log.xz | Bin 5360 -> 5780 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 62372 -> 62588 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98100 -> 98068 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131572 -> 131536 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 403 insertions(+), 403 deletions(-)