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 3d48507a55 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 7fec3686ab 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 8150105b8f 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 1694602d7e 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 16a84d57ed 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards b422724cc4 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 93959662d4 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards ee6791f285 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 0e86aa0421 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 1fd20ec1f1 91: onsuccess: #511: 1: Success after linux: 27 commits discards d186240c8e 90: onsuccess: #510: 1: Success after glibc: 5 commits discards aace1ecf63 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 48950beba9 88: onsuccess: #506: 1: Success after linux: 34 commits discards 4ed9ffdc86 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 4d68eb3bcf 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 3187b83b53 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 55064e57cd 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards cd5b8d5073 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 2565c888d7 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards e4675b987d 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards ef7dd16d78 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards fe116a7448 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 9cc914c5e9 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 86d1f71e5a 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards cf335de2c4 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards e7c96c2f63 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 0802855045 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 43c3fb9d1b 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards e7c6031bb2 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 90d44c71f2 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards df3ab9258b 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 92500c9853 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards e1397e20c1 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 59661a70de 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 3bfe2772a4 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 690bac7587 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards a5d3a5e9ed 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 2198725fac 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards d91fce92db 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 09a3717270 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards f5dd8f290d 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards ed0bab5179 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards cb2d36a977 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards b2803ff5c2 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 643b38622f 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 2d0896b262 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 8e77c1d247 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 452e71714d 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 87cb9941ca 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 89e75bc93d 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 5d743c771e 50: onsuccess: #461: 1: Success after binutils: 12 commits discards c2120fef42 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 47a503832c 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 630b19e94c 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards d7859adabc 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards ef32ebaf68 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 5ef72bedd2 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 67ba072f7f 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 67d4ac38ba 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 53ffaa99c9 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards e2ec6cf3e7 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 9a8160cc2f 39: onsuccess: #447: 1: Success after binutils: 5 commits discards d289a8d1bf 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 5f906dc085 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 9d7d82df91 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 4a30eda413 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards 348446a665 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards dbc4b18fe8 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards fa8fa04bbe 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 579b9606fa 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 25bcf45d5c 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 0a9dbcfad4 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 1ccb896926 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards e07fdabd55 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards cb989c74ee 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards d6dbf551c3 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards e95333e581 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 4623b34749 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 7b35d6b4cf 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 22c7f214c3 21: onsuccess: 1: Successful build after linux: 79 commits discards f535fddb0a 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2472fe671e 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f83fc57e7d 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 12e00345db 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 50b745bbdd 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c8e7fe3bb3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ea7f1fb6f6 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d4083774d9 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2613780165 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a4af70fd28 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d61a66a84f 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 69d58b06a8 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 524bf189c5 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e33b0b3529 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 142f11de5c 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c89bb1ae62 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b0a44f7d26 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 06832227a5 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards a77163f602 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c3685ae183 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards f70720c82c 0: update: binutils-gcc-linux-glibc-gdb: 1 new c9ea792047 0: update: binutils-gcc-linux-glibc-gdb: 1 new 3b4dbd5279 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new fd12045593 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 1f5824e3f3 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 2e6cf7324d 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8af29f3db4 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b6e00aff51 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5341e1fd28 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new ac1541867c 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ce907df869 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d8506a106f 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cbcc538fa8 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a8c6f8fc38 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 129404d9c6 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e7d1aecd5b 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7f69835f61 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7432dea941 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 867cace1f4 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f12583a674 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 40d0650d75 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 05f39940fa 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 29b0856c9b 21: onsuccess: 1: Successful build after linux: 79 commits new 87533de764 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b183ceb05c 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new f0fcdb3b5e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 9b0eeb66eb 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new c19ddc44bb 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new d9f5dfdd07 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 45f5c176d6 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new b3d5ab25f0 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new bad675f21a 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new 37ce1f5e5d 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 53e33751e9 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new dee4d14dfc 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new fb7b37f545 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new f0ea52416d 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new e630f5b80e 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 81122cf4fa 37: onsuccess: #443: 1: Success after binutils: 2 commits new 13627e17d3 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 6f506d655c 39: onsuccess: #447: 1: Success after binutils: 5 commits new 0b3171d122 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 0ea9b13baf 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 9e6fd0e336 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new f9dd7ecc93 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new a8b84d60fc 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new c21d35277d 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 1984ccf523 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 3b5e0de740 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 5c4f807c34 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new d472fd487a 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 9012ab2342 50: onsuccess: #461: 1: Success after binutils: 12 commits new f7a91cc7e7 51: onsuccess: #464: 1: Success after binutils: 6 commits new d3e4d44bd4 52: onsuccess: #467: 1: Success after binutils: 9 commits new 07abc7a35e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 1bfea7b0d4 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 4e52748336 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 7c8660a707 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 07320feb02 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 813720dea7 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new abcc947377 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 37b3fb1ef3 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 47073298ae 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new b910d15112 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 564e22662a 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 833859f37b 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 661e9a5615 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new a77ba24642 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new cf1129fdae 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 85bf592cd4 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 2fd096b250 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 50d95b50e1 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new ee6eefdd08 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new ebd82d0c4c 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new b71e4a385b 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 2a51eb64d1 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 5a66bf2d64 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new b3f287ce8e 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 6f4b19b52a 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 722b301c1f 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 9560df2b4f 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 43ca493fda 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 6c7adaa175 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new cc2af9b82b 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new fbaa47da67 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new c49022079d 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 9666a7de38 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 5196c98c0f 86: onsuccess: #503: 1: Success after binutils: 12 commits new 7f6683cc29 87: onsuccess: #505: 1: Success after glibc: 7 commits new 75076ec5a9 88: onsuccess: #506: 1: Success after linux: 34 commits new 2551fe2b6c 89: onsuccess: #508: 1: Success after binutils: 12 commits new 41805c7bd5 90: onsuccess: #510: 1: Success after glibc: 5 commits new 04c1520ef6 91: onsuccess: #511: 1: Success after linux: 27 commits new 6933d23556 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 9f321864ca 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 7471bd6341 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 2ffb45c4bc 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 3a769a937d 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 073e726bda 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new e639de8ac3 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new b55b1649f8 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 74ef522aba 100: onsuccess: #521: 1: Success after binutils: 10 commits new d446919534 101: onsuccess: #524: 1: Success after binutils: 2 commits
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 (3d48507a55) \ 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 1632 -> 1616 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 51552 -> 50920 bytes 04-build_abe-gcc/console.log.xz | Bin 232852 -> 233012 bytes 06-build_abe-linux/console.log.xz | Bin 9744 -> 9808 bytes 07-build_abe-glibc/console.log.xz | Bin 235456 -> 236112 bytes 08-build_abe-gdb/console.log.xz | Bin 50956 -> 50960 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3896 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2580 -> 2112 bytes 11-check_regression/console.log.xz | Bin 4648 -> 4456 bytes 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 40 +++++++++++++++++++++++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++++-------- sumfiles/binutils.log.xz | Bin 62740 -> 62696 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 97924 -> 97916 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 131428 -> 131436 bytes sumfiles/ld.sum | 4 +-- 24 files changed, 62 insertions(+), 22 deletions(-)