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 cd46baf4ed 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards a1b84fa4e2 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 05dc2797fc 104: onsuccess: #530: 1: Success after gcc: 7 commits discards b138f16961 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 8a0d0bcc1f 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 16268805c6 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 1866c1e7fa 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 70eac1cd98 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 6358fc5864 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 6de424bd82 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards a9073d3463 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards f3268c84e6 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards a7b729e5fd 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 643f800e44 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards b5672fe3f8 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 276d813bc9 91: onsuccess: #511: 1: Success after linux: 27 commits discards a49fb79b5b 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 7bd9dea700 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 64500e0dd8 88: onsuccess: #506: 1: Success after linux: 34 commits discards 8b3b62b7e6 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 6fa42b076a 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 41b38c605b 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 2df43fd088 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards ce870cc184 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 6004fd0b2e 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 11f2639ea4 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 37a913ab62 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 43fbea37ff 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 3d384b2cfc 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 7c8f5bd56b 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards b058bbf60a 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards b9773a5bc9 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 3af2e12cd2 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 1a2e8a15ec 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 3e5e6a957a 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards f30edd25fb 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 961f35337c 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards bf08279cc7 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards b57c2a2d9d 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards edb6bad823 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards f0f4d66ab7 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards e184e0e3d0 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards f247f58226 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 584793c497 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 6072f3a7ca 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 0d74f0579f 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards cc1b6ab484 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards ecc6580c1f 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 28fdc48f7b 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 2dee42a1fa 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 8b0e302c34 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 398c13f4a2 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards be946f806c 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards f0829c8620 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 07f0db9e88 52: onsuccess: #467: 1: Success after binutils: 9 commits discards b3fe60a9af 51: onsuccess: #464: 1: Success after binutils: 6 commits discards b3d6031e04 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 89e2d97a06 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 5589f2eee0 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards e635eba9f0 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 766e584dcd 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 47605c760a 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards dc0bab3767 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards c52735f4d2 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 1e2af937b7 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards d764c9c45c 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards db4cd1a8a5 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 38b49a0e6e 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 9f3b8e1687 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards f11d976890 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 6eea175224 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards cef31c9ddb 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards d1a01c12fc 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 2bde6ed56b 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 218653fa12 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 437bdb7d6b 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards a9a267a455 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 27498317bf 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 4b1152d1c3 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 37c6c3c938 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards a276e225bc 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 55a72dddbe 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards 8ce7329d9b 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards e8f2c7b5dd 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards cb71c94a9c 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c73d6588d1 21: onsuccess: 1: Successful build after linux: 79 commits discards b0ca06fb70 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 39a23332e2 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e9e30b4f59 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1458d20d7d 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 48f2cdc366 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a99a17c64 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bd0d856bc9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ceca7daf6a 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards deaf07695a 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f6aadb2bec 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b858216192 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 96c540d5a7 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 89e62aba3c 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5db2817e0c 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 2cbd1cabb1 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a1c06c7fea 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4edc5edbb5 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 01a7de5ad6 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c387c10664 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fa5dd1220d 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4a3a43f97e 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 25ed278907 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eed59c8cdc 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 46d45f63aa 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50441c7600 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f2ae372c9f 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 35a0de10f3 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 505ffa5caf 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ee97a9b078 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2fc1ac6c11 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 46ae7aebf0 21: onsuccess: 1: Successful build after linux: 79 commits new 24769a25a0 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 679e7a59c4 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new edfb29cfa0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new fb394fdc00 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 6d0fac6b56 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new a6bdffc719 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 1af6e63770 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 44b01af75a 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new b3d595f402 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new e910a6afa8 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 0ebd320ee6 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 1cd31589bc 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 4d63f69de1 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 32dfa29de7 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new edab435d67 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 8b3525a8a7 37: onsuccess: #443: 1: Success after binutils: 2 commits new c9b8bb79ee 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 59b0d433fd 39: onsuccess: #447: 1: Success after binutils: 5 commits new 26cba36e6a 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new b7da731790 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new c7b8ac1c89 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new e891468256 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 531c6acbd9 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new ff9e5cf7a3 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 1ecbe348dc 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 2e58ca81d1 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 225867be73 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 991dc377f2 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 209b68dcbd 50: onsuccess: #461: 1: Success after binutils: 12 commits new 53e0dc23e6 51: onsuccess: #464: 1: Success after binutils: 6 commits new 07d9c7a4c8 52: onsuccess: #467: 1: Success after binutils: 9 commits new 295b6865f0 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 45f3090000 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 6448498e74 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 9573690a53 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new a20a2067d9 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 943e096804 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new 26cac471ae 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new b88392b543 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 94e151e97e 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new e79af8eaf8 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 01ca5d0e2c 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new b8be950d07 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 27a8a3d9fb 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new b7074b8a90 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new aa1484717a 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 851eb7b42d 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 432ac797ac 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new f8874a7210 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 8f403eb361 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 3e8d3d04a5 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new f5bab20e6b 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 1030ccc9d3 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 5ff77300b4 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new ee06eabf14 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 4f8df9e802 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new f91954c1d2 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new feb60d39e5 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new a358aed9e8 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 7ccbf1a67c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 279d9b6442 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new fa0b743c16 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new ca41b62715 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new a7873ae292 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new d10bed8e08 86: onsuccess: #503: 1: Success after binutils: 12 commits new d0be164842 87: onsuccess: #505: 1: Success after glibc: 7 commits new 8392925f11 88: onsuccess: #506: 1: Success after linux: 34 commits new 99fd9a5693 89: onsuccess: #508: 1: Success after binutils: 12 commits new 130fd0ee5d 90: onsuccess: #510: 1: Success after glibc: 5 commits new c006427254 91: onsuccess: #511: 1: Success after linux: 27 commits new ff97ff0824 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new dcd0453d30 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new a855e12485 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new dd7da8dc2b 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new c65ed26f36 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new b0e9c9403d 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new a78be87388 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new a47b67aa1e 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new f28ed7c349 100: onsuccess: #521: 1: Success after binutils: 10 commits new 07b51ce88e 101: onsuccess: #524: 1: Success after binutils: 2 commits new 4cfdb91aa3 102: onsuccess: #527: 1: Success after binutils: 5 commits new 26eeeaeae3 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 6d90e00691 104: onsuccess: #530: 1: Success after gcc: 7 commits new ac24f17f07 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 9e92628079 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new a18ac070a7 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...]
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 (cd46baf4ed) \ 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 1720 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 52240 -> 53568 bytes 04-build_abe-gcc/console.log.xz | Bin 235772 -> 234656 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9172 -> 8864 bytes 07-build_abe-glibc/console.log.xz | Bin 235088 -> 235380 bytes 08-build_abe-gdb/console.log.xz | Bin 51676 -> 52208 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2136 -> 2772 bytes 11-check_regression/console.log.xz | Bin 6008 -> 5964 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 36 +-- 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 62344 -> 62592 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98160 -> 97980 bytes sumfiles/gas.sum | 270 +++++++++++----------- sumfiles/ld.log.xz | Bin 131636 -> 131500 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 388 insertions(+), 388 deletions(-)