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 809e1de4c6b 115: onsuccess: #645: 1: Success after binutils: 27 commits discards c23e94a9aec 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 5f28072b635 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards e215365a6fc 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards e9b593aff72 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards b8b3ecdbbb5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 77d84d1890a 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards f1009aa7de9 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 329c3ce795f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 4dcf638a128 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 62dc5896bb6 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 657b35b7a4a 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 4019cc2a082 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards b732258fde4 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards ef852d9c6ae 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 5b2fd34fcaf 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 27b5995be91 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 491280fdea0 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 7734f267037 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards aff1bbc0845 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 0890c408ef7 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 0076ef88770 94: onsuccess: #616: 1: Success after binutils: 2 commits discards ab9333dc39c 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 30b25abba02 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 8549291ad17 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards f084ce1f3fb 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 249dd80f39d 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 4c713e48e72 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards e1d8b56cee7 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 4ca0b7bc4ba 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 819e000573d 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards d1f96bdebd9 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 5a9f38bc093 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 5afc2777680 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 1f4fbb6198d 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 1812fb4d0de 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards b33549bd289 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards e27b598a50a 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards f8ba2d209ea 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 1a2a88b3f4c 76: onsuccess: #592: 1: Success after linux: 63 commits discards aa232909e21 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 3ff20763107 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 68ebe895c60 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards b13a737e105 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 4287a12b29d 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 51008df1482 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards f7bf8620a2b 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 50057aaef4d 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards dc79bd5245c 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 763447b7c73 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards aeedc7b7315 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 9f0050cedf9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards b511611af3c 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards a68fcc13fba 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 2f666f025ad 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards d079506bb9c 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 6d8e6737c3e 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards 15bf34c9717 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 18ed0aef8b5 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards f62aaa6cf38 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards fd72b79ef67 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards c57104eeb05 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 8db2c121732 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards 0c3e16eaddd 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 49e147597f5 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards f8fc21c9680 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards cf5971dfeef 49: onsuccess: #562: 1: Success after binutils: 9 commits discards aa6c000c6bd 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 430159cfb26 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 1aa24cc753a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards 88281315f97 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 2f62bbc7e24 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards e7ec495b512 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 6353d98b69d 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards f163a3e1225 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 896694a8c50 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards d5644b1f98e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 1709bac1dfd 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 3c5caa8d2c7 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 8b906e154c4 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 39f36661a83 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards da76c72519e 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards f4898695474 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 6f347cc0af3 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 6a9e64b261b 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards bbbc46e35c8 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards a3862bac251 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 95ff4d6849f 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 0174d0dcd88 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 0735e45e875 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 922b7464545 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 8feb6d8d672 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards c74d93a3cf9 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards bdc3e832d15 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards c193e38e6ad 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 86c3654e44f 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 94b5895354c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 9a27dd4b3d1 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 8c574b283f7 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 4ab70a2da1d 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 87af7af69d3 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2e12c75178f 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new fb71445d08c 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c80a8f95f14 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 70e12a2d59e 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new eee71ebe917 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 0782d6b53de 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new fee1cfb9736 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d69c03f3250 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 4904c7b31e3 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 8044e352631 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 41aad23346c 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 59d118c7465 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 5ffaf96bc9a 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 206a9f40a26 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 949c7377388 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 3765fce0542 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new e099029be92 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new a4636020e33 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 67cb632b6a6 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 0cc936f0821 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new c8d964306ae 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 82a7fcdd168 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 55a543066d7 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new 0f5297ff0da 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new ab1b8f6d3d9 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 95ab006a4b2 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 0f45bab3a46 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 170a0b27675 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new ea693fa6580 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 4964bfe4de0 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new a39c0cffaed 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new e43b4fe4b5a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 6e0398a773a 47: onsuccess: #556: 1: Success after binutils: 12 commits new 0437c504e40 48: onsuccess: #559: 1: Success after binutils: 6 commits new fd24e6f2f9c 49: onsuccess: #562: 1: Success after binutils: 9 commits new 599f2c59e29 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 8e816effba6 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 94eb9635333 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new d433d7537f5 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new e6dd8a6ff94 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new 45628aa586a 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 5e14bf34080 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 95c17cdbace 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 45642447983 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 133c8e8d13c 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 219f09203a4 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 8ab371c1e1a 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new ff6f95f857c 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 4efd3037147 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 7f061c9a7ce 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 7356ea51a88 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 72a1d9a3592 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 746ea92d66b 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 6f35245a9b9 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 6e06e4b28e8 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new c8f788d5962 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new f351cb51348 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 568b1080c37 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new b73097c8303 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 924274486b8 74: onsuccess: #590: 1: Success after binutils: 16 commits new bed7054ac8e 75: onsuccess: #591: 1: Success after gcc: 25 commits new bde70a15f11 76: onsuccess: #592: 1: Success after linux: 63 commits new 78bce507493 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new e9ecb59dee7 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new aa727093a39 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 52e69e77533 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new f4178b41b04 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 670e00e7147 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 997843f0dbe 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new c04200ab8f5 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new a22d680a058 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 12fcc25a31d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 35fd8f038b5 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new e7a867a9424 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 6ae9ce20312 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 3223ba057b6 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new f9f4ab46395 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 1c572805d7f 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 44a379e276e 93: onsuccess: #613: 1: Success after binutils: 19 commits new efe7a9391e7 94: onsuccess: #616: 1: Success after binutils: 2 commits new 197e1322888 95: onsuccess: #619: 1: Success after binutils: 5 commits new d30ff9ed5fc 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 51dc16c10a6 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 840bff1cd09 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 36cd4b0f084 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 1d3315f99f8 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new cdd4eed6d75 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 5bcd4a3b38b 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new c92583273c5 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 16f6449e2fe 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 14fe9f742d3 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 7e8792e9a08 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new f1962d7bc7f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new d2da6af3744 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 05240d1deb4 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 71104bae473 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 30d25ee04cb 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new bfdcd83867b 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 9584436edb5 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 264d921360a 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 51ce6a57f6e 115: onsuccess: #645: 1: Success after binutils: 27 commits new 2a7f489d3fe 116: onsuccess: #647: 1: Success after linux: 3 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 (809e1de4c6b) \ 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 1692 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39492 -> 39232 bytes 04-build_abe-gcc/console.log.xz | Bin 214644 -> 214332 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8420 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 244912 -> 244104 bytes 08-build_abe-gdb/console.log.xz | Bin 38912 -> 39128 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3848 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2208 -> 2208 bytes 11-check_regression/console.log.xz | Bin 4764 -> 4576 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 44 ++-- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- sumfiles/binutils.log.xz | Bin 63072 -> 63128 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81772 -> 81772 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121704 -> 121704 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 26 files changed, 384 insertions(+), 392 deletions(-)