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-aarch64 in repository toolchain/ci/base-artifacts.

discards 7bb8453b5c 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards bd8f491d1d 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 57101497f9 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 441a25a631 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 32295d4344 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 301c9129e3 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 23c3ada1ac 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards a218e2f1b7 95: onsuccess: #619: 1: Success after binutils: 5 commits discards dadbd01bc9 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 40b1d86ff4 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 8cfb8c78b5 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards beec4d7d9a 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards baf9eb5fab 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards ca33632651 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards d3c572f145 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards e2e14b7e61 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards d5d0bc95d7 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 81badb58bd 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards a4365af0ed 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 3a256b7094 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 543bceafaa 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 20ba89b613 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 457ac9e0bb 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards f44ec25634 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards be530134b5 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 03edd8b955 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 0ad89df881 76: onsuccess: #592: 1: Success after linux: 63 commits discards 5ea6169622 75: onsuccess: #591: 1: Success after gcc: 25 commits discards c8f01d5d79 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 49a9f2f4ee 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 60c34c102a 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards d0d53fb814 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards b65bab8622 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 2d25ede6de 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 7141d617e6 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 7c198f5204 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 7b540efc6f 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards e9544a1c22 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 3f5556157d 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 3f53b72e10 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards b6c9a605a4 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards e880a7e5c7 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 6d62cb2800 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 16194bb3e8 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards c0899d32dc 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 1a313a6d40 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 9af322dd39 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards bd2c5e62cb 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards cd268b8ad0 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 850b02b59d 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 306b0c874a 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards d832b2e104 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards f391c7989a 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 99991d1547 49: onsuccess: #562: 1: Success after binutils: 9 commits discards d19a5c9f7c 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 57c182917a 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 886b8ee54c 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards 14075c3507 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards c43fb44504 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 064576b7b8 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 41efbe001e 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards f87f776625 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards 05b3fbe122 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 2197bcf65c 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards 205116c43d 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 926ac9368a 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards e29d0b2e50 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 2369d46922 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 227231a39e 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 96b9d3be82 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards b0061d35c8 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] discards 8a75dd94c3 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 1fc418fea6 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards efbe49d483 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] discards 6d1eff5359 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards b34691675b 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 0f835639d6 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] discards b215837773 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] discards c6422a530a 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits discards a9b13f9f44 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits discards bc58820df5 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 9957545f44 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3b5646e8d4 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4f4920666a 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards daefe1a934 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d90b474c79 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 436566e296 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c0deeb5d4b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0b2b2cac8c 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f7ddfd4c49 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8345814ffe 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2c17778b74 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fec9845c23 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cb9010220f 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6a71efe271 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 50655bd5f0 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 9253f724bc 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 335e7c3ec3 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 9a8de9c48a 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards d0e413dfc5 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 7f638d3a77 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 72b87e326f 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 64abe227a9 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5d7bb1e6d7 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new dd293846de 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4d4a9f2e6b 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 059f5f2d94 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 88bc014044 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 596ff9fda1 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 07a2f97306 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6e6eec6a9f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b6ab8b6659 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74f9dbb9a8 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 93e580235a 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new afb0e1502c 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8aa5e0b0bc 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 66e516a819 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 103748a4bd 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6b131871e4 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9927e4624 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8a1bad60ec 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3d9928d779 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 88929b8b98 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits new 67f806caaa 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits new f37214984c 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] new 0507fb57e2 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] new cd28561d17 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 3c92569bac 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 6d11162ddc 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] new 177b5fd729 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 3a93fb3583 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new d7eb1f976e 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new 2e19f4735a 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 62820f8090 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 5165959bf3 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 8169908170 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 18a8baafee 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new 6ca305aa3e 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new dae5f294dc 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new c74cdc9a28 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new beded1752d 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new 4dc3486d1f 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 533ad9d92b 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 0ceaa53c38 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new acd354d3ec 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 3d49b22255 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new d767b718ce 47: onsuccess: #556: 1: Success after binutils: 12 commits new 2a8674f0b1 48: onsuccess: #559: 1: Success after binutils: 6 commits new 74a13df2f7 49: onsuccess: #562: 1: Success after binutils: 9 commits new a7986cb44c 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 0edd8a7b17 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new b4ed63bfbe 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new 865c44c3c4 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 7fe4f29cb9 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new f845e9b116 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 9d66ae12e9 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 98ba851a22 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 3f8b6da3cc 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new ac4e6e6ed3 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 86f25d95f5 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 829b39629a 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 6c0b86bfcc 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 3fef9ea2b9 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 560e11a8e4 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 43daf5e465 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 0e7ec990bb 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new eb939503a6 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 925d0d8ded 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new ef676ebbf3 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 6d0aaeb823 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 1664e2825d 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 6e8d1fadbb 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 5cb9c9cdbd 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new a37f421ac9 74: onsuccess: #590: 1: Success after binutils: 16 commits new 0ecb591df1 75: onsuccess: #591: 1: Success after gcc: 25 commits new e631d5636e 76: onsuccess: #592: 1: Success after linux: 63 commits new 5b782ae073 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 81f0488fbe 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new c73d9d2a68 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 140210c4d0 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 0382ef3c52 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new b5d6fef9ea 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 4f49e22701 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new fe1ac73030 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 4dbaab5b3a 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 3daed549b4 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 80b21315f8 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new c77cf52bd6 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new ba8d1c89c6 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 4a425473d5 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 7056ab1932 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 66f4cb105d 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 99e8515d0c 93: onsuccess: #613: 1: Success after binutils: 19 commits new 73839f67b6 94: onsuccess: #616: 1: Success after binutils: 2 commits new 5c1abe7e04 95: onsuccess: #619: 1: Success after binutils: 5 commits new 755eb03f0d 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 8765b9bf53 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 20d1180ec5 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 333f23d0f6 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 5e55442aee 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new ae850df5fa 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new eb6387225b 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 85720a341e 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 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 (7bb8453b5c) \ 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 1680 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 39436 -> 40132 bytes 04-build_abe-gcc/console.log.xz | Bin 213644 -> 214252 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8408 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 244480 -> 243480 bytes 08-build_abe-gdb/console.log.xz | Bin 39184 -> 39696 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3856 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2184 -> 3076 bytes 11-check_regression/console.log.xz | Bin 5648 -> 5308 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 34 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +-- sumfiles/binutils.log.xz | Bin 63192 -> 63032 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81712 -> 81764 bytes sumfiles/gas.sum | 271 +++++++++++----------- sumfiles/ld.log.xz | Bin 121692 -> 121672 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 28 files changed, 385 insertions(+), 384 deletions(-)