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 68f64b1f25f 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 30e55ff723e 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 9c9728ae0da 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards ec595061b6a 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards b77603bd55b 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 86dec16af50 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 90104569448 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards bbcc57bba86 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 4bc2e6ed67d 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards df9b06984df 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards aab591ef62d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards cc68072c0e7 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards d372aac77bc 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 6ea6fd70b4f 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 2b10c3bfbd2 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards cbe6faf68ad 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 67be1399c39 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards b4310633d32 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards be1289552dd 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards e3d62e3ab80 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 66843fe86e0 94: onsuccess: #616: 1: Success after binutils: 2 commits discards fbc8775c85b 93: onsuccess: #613: 1: Success after binutils: 19 commits discards d24932fd238 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 9a6e1c0ce7a 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 67a1b905a4c 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 5529a4b5839 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 04addbf8202 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards 4ceaaa371e2 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 69ed3bcdc0a 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards d978d26f388 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards 7d2e86e3df0 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 63b9ad90684 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 8a196990b32 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards a193d721566 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 190023d5d4f 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 309ebf03094 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 8968987a329 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 5600abe1e91 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 4d38a601358 76: onsuccess: #592: 1: Success after linux: 63 commits discards 690b82e75ba 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 9b636912916 74: onsuccess: #590: 1: Success after binutils: 16 commits discards b0064b3650f 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 5f33174b893 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 1a57e2cdcdf 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 991d4b6e59f 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards af8c8172450 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 6465331048c 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards f38a9906eb1 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards d70dbb1716a 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 1dca5740667 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards a6b39208832 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 5fbe1bf19bb 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards d02bad6dd56 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards bd2421c43c8 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 08fe5bee3bb 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards a922ec5cdef 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards b96bf7f88f3 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 4f6c977637e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards a54724f5348 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards 01a5a7452bd 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 9002ab4920a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards c8365fea811 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards e0dcccb9277 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards cd46aad4d7b 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 9033a557e5b 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 4d991d6d635 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 03356fbf8ad 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 78e2061eb64 47: onsuccess: #556: 1: Success after binutils: 12 commits discards f6f19396a14 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards fcc135d3143 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards c64bd32acf2 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards d4863855383 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards f91d1600b54 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 73e525ab6de 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 151cbeb160e 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 1d04602db3c 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 1ea58947790 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 2141497cc20 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards f5c89f1ebfa 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 14879c7e528 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 13ac3dd7530 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 19e9719f293 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 4471feab3bb 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 4d01ecb4cd6 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards e2fde621ed0 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 9f8eaa538dd 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards b97d9d0dc49 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 688e572fec7 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 4c56f2e35e3 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards f7a3a147789 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 9dd9fa1287e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 50142837a2d 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards 85d36d94aff 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 93d639b286d 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 77f991f0390 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards fd106c7a27c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 92b784d1d9b 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 2daea3b540d 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 8a84de95fb9 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 37580b5c40e 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards a7fb1f5a605 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 9312e621049 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 87af7af69d3 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4ab70a2da1d 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 8c574b283f7 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 9a27dd4b3d1 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 94b5895354c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 86c3654e44f 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c193e38e6ad 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new bdc3e832d15 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new c74d93a3cf9 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 8feb6d8d672 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 922b7464545 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 0735e45e875 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 0174d0dcd88 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 95ff4d6849f 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new a3862bac251 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new bbbc46e35c8 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 6a9e64b261b 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 6f347cc0af3 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new f4898695474 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new da76c72519e 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 39f36661a83 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 8b906e154c4 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 3c5caa8d2c7 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new 1709bac1dfd 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new d5644b1f98e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 896694a8c50 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new f163a3e1225 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 6353d98b69d 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new e7ec495b512 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 2f62bbc7e24 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 88281315f97 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 1aa24cc753a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 430159cfb26 47: onsuccess: #556: 1: Success after binutils: 12 commits new aa6c000c6bd 48: onsuccess: #559: 1: Success after binutils: 6 commits new cf5971dfeef 49: onsuccess: #562: 1: Success after binutils: 9 commits new f8fc21c9680 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 49e147597f5 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 0c3e16eaddd 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 8db2c121732 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new c57104eeb05 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new fd72b79ef67 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new f62aaa6cf38 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 18ed0aef8b5 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 15bf34c9717 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 6d8e6737c3e 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new d079506bb9c 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 2f666f025ad 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new a68fcc13fba 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new b511611af3c 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 9f0050cedf9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new aeedc7b7315 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 763447b7c73 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new dc79bd5245c 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 50057aaef4d 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new f7bf8620a2b 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 51008df1482 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 4287a12b29d 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new b13a737e105 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 68ebe895c60 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 3ff20763107 74: onsuccess: #590: 1: Success after binutils: 16 commits new aa232909e21 75: onsuccess: #591: 1: Success after gcc: 25 commits new 1a2a88b3f4c 76: onsuccess: #592: 1: Success after linux: 63 commits new f8ba2d209ea 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new e27b598a50a 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new b33549bd289 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 1812fb4d0de 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 1f4fbb6198d 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 5afc2777680 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 5a9f38bc093 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new d1f96bdebd9 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 819e000573d 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 4ca0b7bc4ba 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new e1d8b56cee7 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 4c713e48e72 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 249dd80f39d 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new f084ce1f3fb 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 8549291ad17 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 30b25abba02 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new ab9333dc39c 93: onsuccess: #613: 1: Success after binutils: 19 commits new 0076ef88770 94: onsuccess: #616: 1: Success after binutils: 2 commits new 0890c408ef7 95: onsuccess: #619: 1: Success after binutils: 5 commits new aff1bbc0845 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 7734f267037 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 491280fdea0 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 27b5995be91 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 5b2fd34fcaf 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new ef852d9c6ae 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new b732258fde4 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new 4019cc2a082 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 657b35b7a4a 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 62dc5896bb6 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 4dcf638a128 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 329c3ce795f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new f1009aa7de9 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 77d84d1890a 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new b8b3ecdbbb5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new e9b593aff72 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new e215365a6fc 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 5f28072b635 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new c23e94a9aec 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 809e1de4c6b 115: onsuccess: #645: 1: Success after binutils: 27 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 (68f64b1f25f) \ 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 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39548 -> 39492 bytes 04-build_abe-gcc/console.log.xz | Bin 214172 -> 214644 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8276 -> 8420 bytes 07-build_abe-glibc/console.log.xz | Bin 244944 -> 244912 bytes 08-build_abe-gdb/console.log.xz | Bin 38796 -> 38912 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3832 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2136 -> 2208 bytes 11-check_regression/console.log.xz | Bin 5716 -> 4764 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 56 ++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +-- sumfiles/binutils.log.xz | Bin 63288 -> 63072 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81792 -> 81772 bytes sumfiles/gas.sum | 275 +++++++++++------------ sumfiles/ld.log.xz | Bin 121940 -> 121704 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 26 files changed, 404 insertions(+), 399 deletions(-)