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 d446919534 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 74ef522aba 100: onsuccess: #521: 1: Success after binutils: 10 commits discards b55b1649f8 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards e639de8ac3 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 073e726bda 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 3a769a937d 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 2ffb45c4bc 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 7471bd6341 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 9f321864ca 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 6933d23556 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 04c1520ef6 91: onsuccess: #511: 1: Success after linux: 27 commits discards 41805c7bd5 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 2551fe2b6c 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 75076ec5a9 88: onsuccess: #506: 1: Success after linux: 34 commits discards 7f6683cc29 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 5196c98c0f 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 9666a7de38 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards c49022079d 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards fbaa47da67 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards cc2af9b82b 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 6c7adaa175 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 43ca493fda 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 9560df2b4f 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 722b301c1f 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 6f4b19b52a 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards b3f287ce8e 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 5a66bf2d64 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 2a51eb64d1 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards b71e4a385b 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards ebd82d0c4c 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards ee6eefdd08 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 50d95b50e1 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 2fd096b250 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 85bf592cd4 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards cf1129fdae 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards a77ba24642 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 661e9a5615 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 833859f37b 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 564e22662a 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards b910d15112 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 47073298ae 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 37b3fb1ef3 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards abcc947377 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 813720dea7 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 07320feb02 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 7c8660a707 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 4e52748336 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 1bfea7b0d4 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 07abc7a35e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards d3e4d44bd4 52: onsuccess: #467: 1: Success after binutils: 9 commits discards f7a91cc7e7 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 9012ab2342 50: onsuccess: #461: 1: Success after binutils: 12 commits discards d472fd487a 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 5c4f807c34 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 3b5e0de740 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 1984ccf523 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards c21d35277d 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards a8b84d60fc 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards f9dd7ecc93 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 9e6fd0e336 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 0ea9b13baf 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 0b3171d122 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 6f506d655c 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 13627e17d3 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 81122cf4fa 37: onsuccess: #443: 1: Success after binutils: 2 commits discards e630f5b80e 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards f0ea52416d 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards fb7b37f545 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards dee4d14dfc 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 53e33751e9 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 37ce1f5e5d 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards bad675f21a 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards b3d5ab25f0 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 45f5c176d6 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards d9f5dfdd07 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards c19ddc44bb 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 9b0eeb66eb 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards f0fcdb3b5e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards b183ceb05c 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 87533de764 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 29b0856c9b 21: onsuccess: 1: Successful build after linux: 79 commits discards 05f39940fa 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 40d0650d75 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f12583a674 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 867cace1f4 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7432dea941 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7f69835f61 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e7d1aecd5b 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 129404d9c6 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a8c6f8fc38 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cbcc538fa8 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d8506a106f 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce907df869 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ac1541867c 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5341e1fd28 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b6e00aff51 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 8af29f3db4 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 2e6cf7324d 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 1f5824e3f3 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards fd12045593 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3b4dbd5279 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a3d0da73c8 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8a32a5e073 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6653052042 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new caa062a71f 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 253267125b 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8142dd1c64 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 44a611f4ac 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5a84c4bf58 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a3bba6cb86 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new caae9173d6 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8e7c076251 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e7c148b8b0 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 281a451058 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce12390a33 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dc17a8fcf3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1bd3feb0e4 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2228e3d7e 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fe87497ff6 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 934c410ddd 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 78ee892fec 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a6f76425e8 21: onsuccess: 1: Successful build after linux: 79 commits new 5ceae8cac0 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4601a79c10 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5e32853e71 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 12812f7d73 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 9d78cfeed2 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 7e503bdb02 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 3592780831 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 7112616d1d 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 599a22e69a 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new dfbc7b50d3 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 8322194978 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 6393f4cdee 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new b5f2698c21 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 072c740d53 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 994a07d4fa 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new cba4e21449 37: onsuccess: #443: 1: Success after binutils: 2 commits new 9b3ef471eb 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 7474c543d0 39: onsuccess: #447: 1: Success after binutils: 5 commits new f7147372d5 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 78509d1cfe 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 091561f41f 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 3f7775d4b0 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new a64294ba36 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 1047ad4756 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new ac0305f710 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 9b10387565 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new c290746073 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 16e1d06a2f 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 6a078d7aa1 50: onsuccess: #461: 1: Success after binutils: 12 commits new c9f5e7941b 51: onsuccess: #464: 1: Success after binutils: 6 commits new 058088da88 52: onsuccess: #467: 1: Success after binutils: 9 commits new c8491190b5 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 8c5e88ae0c 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 2244f8f8cb 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 145d32ef0d 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 9e774d7647 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 13aa38525e 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new f5b3464335 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new c48595b2bd 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new f76e29e8bd 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 693f66f9a9 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new bf411b97d4 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 913735cb14 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new c9d976099b 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new c85b334353 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 37a11cf4c1 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 6ebff0dec5 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 2f536f2812 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 9e72b75cd3 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 94e24ee30f 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 95a01b11a3 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 8066feea11 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 129d0996be 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 3b164ffbef 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 9f3bd6841c 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 3ee1ba3ea8 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 35008fab77 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new a47801432f 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new d9523af140 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 2d9ee5b2d3 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new ce4ec1cfb7 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new c246bc8907 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new b44e86a2af 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 7042d3355a 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 152a7562d0 86: onsuccess: #503: 1: Success after binutils: 12 commits new ab6eaca20f 87: onsuccess: #505: 1: Success after glibc: 7 commits new f23cc67c8f 88: onsuccess: #506: 1: Success after linux: 34 commits new d9c54f0258 89: onsuccess: #508: 1: Success after binutils: 12 commits new 8212827aad 90: onsuccess: #510: 1: Success after glibc: 5 commits new db872b583c 91: onsuccess: #511: 1: Success after linux: 27 commits new c8d287b24d 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 016b80c424 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new edde6dddd8 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new ddd9bae991 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new af520a1496 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 2392881092 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 15d9859c6e 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new aaeba419ef 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 57c2437e3b 100: onsuccess: #521: 1: Success after binutils: 10 commits new 8c7520995b 101: onsuccess: #524: 1: Success after binutils: 2 commits new f4c63db5e3 102: onsuccess: #527: 1: Success after binutils: 5 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 (d446919534) \ 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 1616 -> 1620 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 50920 -> 51160 bytes 04-build_abe-gcc/console.log.xz | Bin 233012 -> 233916 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9808 -> 9692 bytes 07-build_abe-glibc/console.log.xz | Bin 236112 -> 235008 bytes 08-build_abe-gdb/console.log.xz | Bin 50960 -> 51028 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3860 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2112 -> 2272 bytes 11-check_regression/console.log.xz | Bin 4456 -> 4700 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 64 +++--- 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 62696 -> 62476 bytes sumfiles/binutils.sum | 65 +++--- sumfiles/gas.log.xz | Bin 97916 -> 98040 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 131436 -> 131440 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 26 files changed, 404 insertions(+), 395 deletions(-)