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 a4185444ce4 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 0899799d785 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 2ebc272643e 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards abc1f1e748b 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards e08f87a417c 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 4b65620aa6a 116: onsuccess: #647: 1: Success after linux: 3 commits discards 900530220a0 115: onsuccess: #645: 1: Success after binutils: 27 commits discards cd0502fac71 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards e69a278c6e3 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 20aff8c8c51 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards a4fae7433b9 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 5801f86d6a6 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 14ca0a8d5d7 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 5b265f9aa88 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards e6a63de9058 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 99e2f7be58c 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 28a776ee88c 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards bec22908dda 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 600e2d197e2 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 5782a6a8017 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 6259d2ac5f8 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 902774b3718 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 2952d33fe12 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards c68a2c85a04 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards bd74f669e72 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 64957bee49d 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 2b7e4090d4f 95: onsuccess: #619: 1: Success after binutils: 5 commits discards e210271c6ae 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 20ee27cce35 93: onsuccess: #613: 1: Success after binutils: 19 commits discards f418ab3cbfe 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards f4abcdd0827 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards f7504b2addc 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards f79070d350f 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 6d8c38e0410 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards 65bd07b036d 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 12a3cc7fbdc 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 8879a55a5c9 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards e906f4969ac 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 38946d588ee 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 0b5bb8cbc78 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 69b5c7227bd 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 98a4276b6d6 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards f2406a6dacf 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 6686234604f 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards ab8edddbb08 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 98f94a6dc04 76: onsuccess: #592: 1: Success after linux: 63 commits discards 853f0c1bf59 75: onsuccess: #591: 1: Success after gcc: 25 commits discards be22c22c8fa 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 6540e5dae62 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 70e75d994cb 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards ad0a4022960 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards a3159178a30 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards cf53a494cff 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards c4f1f3111d0 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 6abe2571183 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 403e8062f49 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 63e080633ad 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 3ceeb97771b 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 1d17d2214db 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 6bf0f2df3f3 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards ffa5d5d7b32 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 85243f595dd 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards f7e6f65772c 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards e799fc76ac8 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 77cb9e7b2c3 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 1d8cf96a0ba 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards dd09058b78d 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 73e64352a06 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 5716a5f0619 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards f7e55e032a9 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 93a1bbb38a4 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 2211eeacd80 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 3358dae9d3a 49: onsuccess: #562: 1: Success after binutils: 9 commits discards fa4d2e98247 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 40f0147a483 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 765234a241a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards 9e3c84ffa47 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards a875b4c01d6 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 249501c67de 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 76e93a0d3b2 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 1fc139d661f 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards b4900d52acb 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 63a30df01f7 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 409ce9c09ca 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 2f8e897d31e 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 96487087214 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards d61fb91d33f 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 7a2ec5dd6fa 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 520a001c1bf 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 5f1b38006f8 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards e706d30306e 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 881c9260a90 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards d58a4a36e97 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards b60ac3f1bb3 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards f001f6ad2dc 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards e22123c28c3 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards befd4851dfd 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 43194bced61 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 0ebeb998ffd 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards f026fbc7fb3 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 92742eba44d 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 7fb7afa416d 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2c600e408a5 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 7a4b6463ebd 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new fab754a3726 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 5d888b7185e 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 5f666c986ae 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 71fbf073269 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new fbb3581703e 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 20492bb9d52 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new c4e3e072b8c 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 06dd3881291 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 8d4f5e9054a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new e617f8a6881 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new ccda2538e8d 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new a5e8157810a 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new c00b40ff0af 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new ba21419a314 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new f469f13ab92 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 1c75bd0ab13 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new e3aacf3ce71 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 195e878068e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 2d7aa0a99fe 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 6e0833ee1ed 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new ce63803d666 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new a07cff8ae43 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 71216640ff6 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 39eda2a001f 47: onsuccess: #556: 1: Success after binutils: 12 commits new 6dafadc4401 48: onsuccess: #559: 1: Success after binutils: 6 commits new ac69b929e22 49: onsuccess: #562: 1: Success after binutils: 9 commits new 7ff981906c1 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 0a0094a6174 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new b5c3a61cfda 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 56dbeda40cd 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 285e58c05b6 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new cbb706427af 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 2b2aeda359e 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 49fda707e77 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new b15534157d1 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 24828ffd5bb 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new a0a0019e0fa 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 21abe7be7d7 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new 22b0d73d160 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 4d03e88aca2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new db44bb5f8e3 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new aef00226385 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new fcbb12a3694 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new eeeee479d2d 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 98b33fbb426 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 98cab56be76 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new fd4b78fabcf 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new e6c3fd27be0 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 003eff04049 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 6283be7ebde 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 06b8187fac4 74: onsuccess: #590: 1: Success after binutils: 16 commits new 1ce0af1b34c 75: onsuccess: #591: 1: Success after gcc: 25 commits new 5d6fcb4285d 76: onsuccess: #592: 1: Success after linux: 63 commits new f549e4229d6 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 7fe6a0e74fe 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new a85d1ac23d9 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 51aab7262c7 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new c694d442e88 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 6e799f8c9e7 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 822eb304d54 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new bdd39ef0056 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 9f94230a326 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 5a0b545fb2f 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new ff5b7251a9e 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 5f1ec5ae754 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 0371a77329f 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 4b196923c97 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new b88f454caa5 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new ac05f571e59 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 0f89b098b8b 93: onsuccess: #613: 1: Success after binutils: 19 commits new a788c97e7c1 94: onsuccess: #616: 1: Success after binutils: 2 commits new 6e2a468bbc4 95: onsuccess: #619: 1: Success after binutils: 5 commits new bec0548abcf 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 772c91b45a3 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 0a124ffd5b9 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 25547c278b4 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new ec78f6e3cf0 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 29a69a99312 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 545ea467e52 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new 43285083fae 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 3d2338c9e29 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new c2a0b45ce1c 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 272c09e5b7a 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 7d0fdfe9caf 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 30a01084d55 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 2abf080a614 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 04a29a3728d 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 37520ee68ac 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 967e9eac633 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 33410e3fc50 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 5b8a96c25c4 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 0914edb993e 115: onsuccess: #645: 1: Success after binutils: 27 commits new ecae101fa1d 116: onsuccess: #647: 1: Success after linux: 3 commits new 9e452f9e63f 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 3209ba3be10 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new cabf97973d2 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 06d44619500 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new ddd5de85e2e 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 0148f140f86 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...]

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 (a4185444ce4) \ 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 1732 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 39416 -> 40028 bytes 04-build_abe-gcc/console.log.xz | Bin 213328 -> 214504 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8304 bytes 07-build_abe-glibc/console.log.xz | Bin 243352 -> 243516 bytes 08-build_abe-gdb/console.log.xz | Bin 39056 -> 38900 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3836 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2064 -> 2144 bytes 11-check_regression/console.log.xz | Bin 5356 -> 5696 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 40 ++-- 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 63288 -> 62996 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81824 -> 81864 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121720 -> 121728 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 391 insertions(+), 391 deletions(-)