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 85720a341e 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards eb6387225b 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards ae850df5fa 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 5e55442aee 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 333f23d0f6 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 20d1180ec5 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 8765b9bf53 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 755eb03f0d 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 5c1abe7e04 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 73839f67b6 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 99e8515d0c 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 66f4cb105d 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 7056ab1932 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 4a425473d5 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards ba8d1c89c6 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards c77cf52bd6 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 80b21315f8 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 3daed549b4 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 4dbaab5b3a 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards fe1ac73030 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 4f49e22701 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards b5d6fef9ea 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 0382ef3c52 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 140210c4d0 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards c73d9d2a68 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 81f0488fbe 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 5b782ae073 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards e631d5636e 76: onsuccess: #592: 1: Success after linux: 63 commits discards 0ecb591df1 75: onsuccess: #591: 1: Success after gcc: 25 commits discards a37f421ac9 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 5cb9c9cdbd 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 6e8d1fadbb 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 1664e2825d 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 6d0aaeb823 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards ef676ebbf3 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 925d0d8ded 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards eb939503a6 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 0e7ec990bb 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 43daf5e465 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 560e11a8e4 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 3fef9ea2b9 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 6c0b86bfcc 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 829b39629a 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 86f25d95f5 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards ac4e6e6ed3 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards 3f8b6da3cc 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 98ba851a22 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 9d66ae12e9 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards f845e9b116 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 7fe4f29cb9 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 865c44c3c4 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards b4ed63bfbe 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 0edd8a7b17 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards a7986cb44c 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 74a13df2f7 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 2a8674f0b1 48: onsuccess: #559: 1: Success after binutils: 6 commits discards d767b718ce 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 3d49b22255 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards acd354d3ec 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards 0ceaa53c38 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 533ad9d92b 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 4dc3486d1f 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards beded1752d 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards c74cdc9a28 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards dae5f294dc 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards 6ca305aa3e 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 18a8baafee 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 8169908170 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 5165959bf3 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 62820f8090 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 2e19f4735a 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards d7eb1f976e 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] discards 3a93fb3583 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 177b5fd729 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 6d11162ddc 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] discards 3c92569bac 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards cd28561d17 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 0507fb57e2 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] discards f37214984c 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] discards 67f806caaa 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits discards 88929b8b98 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits discards 3d9928d779 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 8a1bad60ec 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9927e4624 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6b131871e4 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 103748a4bd 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 66e516a819 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8aa5e0b0bc 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards afb0e1502c 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 93e580235a 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 74f9dbb9a8 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b6ab8b6659 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6e6eec6a9f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 07a2f97306 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 596ff9fda1 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 88bc014044 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 059f5f2d94 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 4d4a9f2e6b 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards dd293846de 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 5d7bb1e6d7 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 64abe227a9 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a672cf8663 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 83473d4eec 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6c5b27df65 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 54fe62a24d 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 096f3cd379 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 245b4cb41f 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 272ee9333b 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1692642e9a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fb61122244 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aae27df3d6 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2d2e46caf9 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e0fc9af2de 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ac9689552e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new acad074084 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fa8746542f 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4e136d7a7f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cb6cf57efc 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ac323fc75 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1b2ce4b5f3 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new df7ab6c1ee 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new eaf10da73c 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits new 97d995c9b9 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits new b6d91fb851 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] new 73a1393b0c 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] new 817b9eb462 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 5f5c68d87d 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 72eb5f4760 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] new ed8dff5ced 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new d51bbd1c6f 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 4870319830 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new 0c079eacd6 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 7dd7fe9681 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 9842d9d100 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 327573ad60 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new e1b7eb8b54 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new 88ceb6f45e 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new a20fd37da4 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new 113201b22c 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new b32002ff19 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new e9f8f54f83 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 5aabc5008a 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 56537364ad 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 94871b57cf 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 042fe8e729 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 1b31d8b188 47: onsuccess: #556: 1: Success after binutils: 12 commits new 691cbe53db 48: onsuccess: #559: 1: Success after binutils: 6 commits new 884a969d26 49: onsuccess: #562: 1: Success after binutils: 9 commits new f8d4805a36 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 06b2b28bcc 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new cf735cf083 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new bce3dc48f7 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new f0c31a575e 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 55fd7ccb49 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 4e15d7e15b 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 6a1c5eeb6e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new d414f76ba6 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 5985e8acdc 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new e5773f5e11 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new e24e5be5b1 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 012f2b2daa 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 27ea9d77ce 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 7f64f64d37 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 9b734a9420 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 6d9da6ffc1 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 5744943f59 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new e986cc2991 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 1eb879a983 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 18ed24b7da 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new ab92e9a4d2 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new a00e1a2793 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 65bbefd3aa 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 3d891d1ba3 74: onsuccess: #590: 1: Success after binutils: 16 commits new 03b4fec9b2 75: onsuccess: #591: 1: Success after gcc: 25 commits new 8b5c54241e 76: onsuccess: #592: 1: Success after linux: 63 commits new 4ff151d39f 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new b17cf1af10 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new cad44fb08e 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 75296f57a1 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 0701456153 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 892f42faa4 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 8dda5b236f 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 8de09a1b16 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new c5a4230a1c 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new a203957341 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 73678dd649 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new adf93d7817 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 23a0291107 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 1354fd1892 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 0b68a63262 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new a8c7922434 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new ca512e03fa 93: onsuccess: #613: 1: Success after binutils: 19 commits new 800cc70fec 94: onsuccess: #616: 1: Success after binutils: 2 commits new e651df759a 95: onsuccess: #619: 1: Success after binutils: 5 commits new da6e35ead0 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 0f871b39ea 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 74458d5a1d 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 61ec35df5e 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new b007693540 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 8235ac3378 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new e9a2c777a1 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new a1f806b33d 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 57cebb4579 104: onsuccess: #630: 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 (85720a341e) \ 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 1736 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 40132 -> 40192 bytes 04-build_abe-gcc/console.log.xz | Bin 214252 -> 214340 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8520 bytes 07-build_abe-glibc/console.log.xz | Bin 243480 -> 243696 bytes 08-build_abe-gdb/console.log.xz | Bin 39696 -> 39516 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3848 bytes 10-build_abe-check_binutils/console.log.xz | Bin 3076 -> 2584 bytes 11-check_regression/console.log.xz | Bin 5308 -> 5696 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 63032 -> 62884 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81764 -> 81776 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121672 -> 121752 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 389 insertions(+), 389 deletions(-)