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 0148f140f86 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards ddd5de85e2e 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 06d44619500 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards cabf97973d2 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 3209ba3be10 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 9e452f9e63f 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards ecae101fa1d 116: onsuccess: #647: 1: Success after linux: 3 commits discards 0914edb993e 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 5b8a96c25c4 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 33410e3fc50 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 967e9eac633 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 37520ee68ac 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 04a29a3728d 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 2abf080a614 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 30a01084d55 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 7d0fdfe9caf 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 272c09e5b7a 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards c2a0b45ce1c 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 3d2338c9e29 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 43285083fae 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 545ea467e52 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 29a69a99312 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards ec78f6e3cf0 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 25547c278b4 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 0a124ffd5b9 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 772c91b45a3 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards bec0548abcf 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 6e2a468bbc4 95: onsuccess: #619: 1: Success after binutils: 5 commits discards a788c97e7c1 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 0f89b098b8b 93: onsuccess: #613: 1: Success after binutils: 19 commits discards ac05f571e59 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards b88f454caa5 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 4b196923c97 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 0371a77329f 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 5f1ec5ae754 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards ff5b7251a9e 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 5a0b545fb2f 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 9f94230a326 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards bdd39ef0056 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 822eb304d54 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 6e799f8c9e7 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards c694d442e88 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 51aab7262c7 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards a85d1ac23d9 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 7fe6a0e74fe 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards f549e4229d6 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 5d6fcb4285d 76: onsuccess: #592: 1: Success after linux: 63 commits discards 1ce0af1b34c 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 06b8187fac4 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 6283be7ebde 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 003eff04049 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards e6c3fd27be0 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards fd4b78fabcf 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 98cab56be76 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 98b33fbb426 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards eeeee479d2d 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards fcbb12a3694 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards aef00226385 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards db44bb5f8e3 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 4d03e88aca2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 22b0d73d160 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 21abe7be7d7 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards a0a0019e0fa 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 24828ffd5bb 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards b15534157d1 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 49fda707e77 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 2b2aeda359e 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards cbb706427af 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 285e58c05b6 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 56dbeda40cd 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards b5c3a61cfda 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 0a0094a6174 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 7ff981906c1 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards ac69b929e22 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 6dafadc4401 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 39eda2a001f 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 71216640ff6 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards a07cff8ae43 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards ce63803d666 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 6e0833ee1ed 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 2d7aa0a99fe 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 195e878068e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards e3aacf3ce71 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 1c75bd0ab13 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards f469f13ab92 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards ba21419a314 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards c00b40ff0af 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards a5e8157810a 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards ccda2538e8d 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards e617f8a6881 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 8d4f5e9054a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 06dd3881291 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards c4e3e072b8c 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 20492bb9d52 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards fbb3581703e 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 71fbf073269 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 5f666c986ae 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 5d888b7185e 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards fab754a3726 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 7a4b6463ebd 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards 2c600e408a5 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 55872510524 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new eb8ce745967 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 36f80a3ddba 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 60c161eb042 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 80897cd1f1d 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 097ce42a209 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new a35670f4bd9 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new cf9adaa5b57 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 4c91566ad06 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 23cae5747b8 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 0bd7368b627 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 2a0953685fa 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new c27699b6a0a 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 9f775600054 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new fbb1f41616b 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 094e25facb6 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new cbfe0b49990 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new b247a1518fb 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new fae4ed6c8da 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 05148eb7956 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 26963704a92 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 5f5fa5a4960 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new febf286b901 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 4e5c82ca55e 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 81910d1ea59 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new d184a1752b5 47: onsuccess: #556: 1: Success after binutils: 12 commits new d2d4f90899f 48: onsuccess: #559: 1: Success after binutils: 6 commits new 8e43677529a 49: onsuccess: #562: 1: Success after binutils: 9 commits new cf948a99981 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new abd5833e995 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new a8bda0dff99 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new b44406d94bd 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 4c05a69d209 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new 71b74bcf968 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 4bc62168469 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 621e58be2a4 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 6090598a904 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 2b0d9c25b8d 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 3e32f41a8a8 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new bec691f62e6 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new d9d8073852a 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 227112e9d91 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 550dedece15 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 18af4b32648 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new e9ed271a931 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 1cf0d393280 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 47f3607392f 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 498919013d0 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new b021c597435 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 7db02b2696a 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 9fc2f4960a7 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 7ebe25bb188 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new a77121ce2f5 74: onsuccess: #590: 1: Success after binutils: 16 commits new bf7bdaaf9b4 75: onsuccess: #591: 1: Success after gcc: 25 commits new 69694b78241 76: onsuccess: #592: 1: Success after linux: 63 commits new 4d9e6bc06a7 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 28b6d7783ea 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 9cae3801ab5 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 54cb1852248 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 6c7dd4e7119 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 0123b9d90f0 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 10b075349f2 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new c467da40604 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new f959c92cbd6 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 6cd672a9b58 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 43ee4053539 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new d8b57afbafb 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 5ecce8b8564 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 36e800ebc75 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 0fdeb9db46d 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 549a26d7375 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new a155247fd35 93: onsuccess: #613: 1: Success after binutils: 19 commits new b4e8450a0c7 94: onsuccess: #616: 1: Success after binutils: 2 commits new 22a30eb68d6 95: onsuccess: #619: 1: Success after binutils: 5 commits new 843e8c9e945 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 561368fd7d4 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 4b2ff870102 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 893d66c52ae 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new f245983f303 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 1c5cf0c79b3 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 34ae383d080 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new c5508bd7a32 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new f3404631584 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 606237b8030 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 0bc8816ca6e 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new b7c0a83f5e1 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new d70d191bc40 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 16c82c35a19 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new ef9509953bb 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new d5054c68df3 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 344e31b7ef2 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 8a1eb87367b 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 0a6e54501c4 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 23baae04a16 115: onsuccess: #645: 1: Success after binutils: 27 commits new d4b629f7187 116: onsuccess: #647: 1: Success after linux: 3 commits new 994b0b7e8d6 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new bebbc1b0bf4 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new a63858cf02b 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 3a0f17a0289 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 3f4a3abe95b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 300eeb13560 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new d7f050920d7 123: onsuccess: #655: 1: Success after binutils: 22 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 (0148f140f86) \ 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 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 40028 -> 39732 bytes 04-build_abe-gcc/console.log.xz | Bin 214504 -> 214128 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8304 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 243516 -> 245860 bytes 08-build_abe-gdb/console.log.xz | Bin 38900 -> 40232 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3908 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2144 -> 2568 bytes 11-check_regression/console.log.xz | Bin 5696 -> 4744 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 62 +++--- 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 62996 -> 63176 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81864 -> 83780 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121728 -> 121932 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 26 files changed, 394 insertions(+), 398 deletions(-)