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-arm in repository toolchain/ci/base-artifacts.

discards 37bc5dc66e 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards b0914f6421 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards fa769a2acc 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards 681a6f4af5 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 120ecf07b2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards ddd2861d2a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards bd46a610d9 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 91ce07dbf8 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards d0c64af967 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 58cdf877d9 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 82c8bb0258 100: onsuccess: #521: 1: Success after binutils: 10 commits discards d18e0df2b5 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 274e5aeb4c 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 4ef55c11d8 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 7e23e51f76 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards e5418c9777 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards d75043b229 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 850c3dd742 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards cc57cc19be 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 7420d1881b 91: onsuccess: #511: 1: Success after linux: 27 commits discards 62625c11b7 90: onsuccess: #510: 1: Success after glibc: 5 commits discards c690305bc3 89: onsuccess: #508: 1: Success after binutils: 12 commits discards f33e2b7032 88: onsuccess: #506: 1: Success after linux: 34 commits discards 630d27f0df 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 1684b7b4f7 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 5c3c926026 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards ade150a175 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 2edd0dbd35 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards e4910cbf54 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards a56dae8f3e 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 3801a43188 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 7a0f04ccc8 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 1ceff7bfe2 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards fe6878b509 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 249ab0fd8b 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 943ac455ad 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 0b41ebdb4f 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 2c7bb17a69 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 58634318d5 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 93f5a2cdd4 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards bdd6cbe3a9 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards e2dc25f36b 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 5eea50c266 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 825b1a844e 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 5d0b7a84d5 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 542f0c0036 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards abb2555019 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 7cbf3c9f85 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 8cf0820d6c 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 9c57f9edc5 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 9c371b3ea1 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards c389d5db82 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards cbb2e1c8c6 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 533deedda6 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 3bf4ded5d0 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards ae7b74d944 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards b7fbb6e4c7 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards feeb12e415 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 891db5f263 52: onsuccess: #467: 1: Success after binutils: 9 commits discards d6f07cca46 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 242f6edc73 50: onsuccess: #461: 1: Success after binutils: 12 commits discards bbd37f04af 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 70187b7e33 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 5a9a959017 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 16798529fb 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 7e7031fd16 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 7f6cb1bacd 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 96419428a7 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards a37b157081 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 6d1b248cc0 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 25a7e8dd39 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 678a024f72 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 98866b0cda 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 8fc7748dc8 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 833be0e97d 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards d5d96b303d 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards 439b5b2919 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 76173ae81b 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards bbacd50232 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 89a98f4180 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards ff953c670c 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 713a1beb83 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 65e2842fc8 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards fdd87720b5 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards c7a5ef1e2d 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards ed8d9c6534 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards 9b20bc7c11 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 8d47c5511e 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards a03c5cde71 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7a64117b45 21: onsuccess: 1: Successful build after linux: 79 commits discards d384945dcb 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 43e067debb 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6ea1b6e2b1 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f87634f3ec 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9248d81b07 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 580bddb62e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32d1a43af6 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0642f48c64 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6dae99d77d 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f5be402a85 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fcd760faf4 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d5a0d2afb6 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e9e9444ac4 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a242f7388b 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab52e511d5 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 29de8be289 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ddc606dc02 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 61f9649da2 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5f7df094b5 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a29851e8ca 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ccb1ac632f 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 41d78427de 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6714927818 21: onsuccess: 1: Successful build after linux: 79 commits new ca49bebf1f 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f68d09b28d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 3c2ff8a742 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new a9bceb4994 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 38d78bc72b 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new b5cc8935d1 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new ed05c40275 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 61f407622c 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 871cd4a1f6 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new 9aeaf9bbf0 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new f6f4893a3d 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new b904f7dfee 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 836e9f2d5b 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 8b671b1dbf 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 9c4ac7295b 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new dd0b2658e1 37: onsuccess: #443: 1: Success after binutils: 2 commits new 949fe3cd6e 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new be2da42a16 39: onsuccess: #447: 1: Success after binutils: 5 commits new 2e4869c759 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 3928780819 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 12c6db7900 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new d394abdcf0 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 89a53ac4cb 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 897c9c9cd9 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new ed7c99b955 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new e001246832 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new caabb1f1b1 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 51f9005075 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 63e14afae0 50: onsuccess: #461: 1: Success after binutils: 12 commits new 792cc50e83 51: onsuccess: #464: 1: Success after binutils: 6 commits new 768f17bcd2 52: onsuccess: #467: 1: Success after binutils: 9 commits new bf6004df9e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 2e48a313d0 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 8ba1c0d9a2 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 1674009158 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 0bac300b6b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 775e5b8e7e 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new 411e46d6a0 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 9e248c76d4 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new fc3a2d6ef5 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new ebca6863ba 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 9ad93e408a 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 2d7c8649f3 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 1102cbbd01 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 3ae7880cf6 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 9d07e3b010 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new a5d5a1adfc 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new b8a9c95080 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 04d18468a0 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 98c7b81463 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new feeba21157 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 724a2a7bec 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 7cba58307e 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 6f5a28d125 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 59123af4b3 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 7359f9cbde 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 5989ceef9d 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new f6f8a5f72f 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 87acea9894 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 0f0bc96326 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 1a21e5d3b0 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 4b70a89297 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new e125553eef 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new a42cf2a85a 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new d89772d26e 86: onsuccess: #503: 1: Success after binutils: 12 commits new cfc26b86f0 87: onsuccess: #505: 1: Success after glibc: 7 commits new ac6c6f36cf 88: onsuccess: #506: 1: Success after linux: 34 commits new 69b14a7336 89: onsuccess: #508: 1: Success after binutils: 12 commits new 6c0f9dd0cb 90: onsuccess: #510: 1: Success after glibc: 5 commits new 563d01d4ce 91: onsuccess: #511: 1: Success after linux: 27 commits new f8a708c5cb 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 743fc07f04 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 267cae23f9 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 0dd7affbb7 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 92f241539b 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 326e268b7f 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new cdb7199f3d 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new ee9e629d4f 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 83107ea0cc 100: onsuccess: #521: 1: Success after binutils: 10 commits new 294baba708 101: onsuccess: #524: 1: Success after binutils: 2 commits new f5ba2ed8b6 102: onsuccess: #527: 1: Success after binutils: 5 commits new ef9bf0196f 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 843a8fc553 104: onsuccess: #530: 1: Success after gcc: 7 commits new f2d26f3f4e 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 57a0e723a2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new fec17fbfe7 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new d70a1d1fe4 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new 7ec1a93f37 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new f721711b40 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 66476be9a5 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 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 (37bc5dc66e) \ 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 1684 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52976 -> 52008 bytes 04-build_abe-gcc/console.log.xz | Bin 233716 -> 236352 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8376 -> 8344 bytes 07-build_abe-glibc/console.log.xz | Bin 235516 -> 235976 bytes 08-build_abe-gdb/console.log.xz | Bin 50940 -> 51860 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3864 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2200 -> 2176 bytes 11-check_regression/console.log.xz | Bin 5692 -> 5268 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +-- sumfiles/binutils.log.xz | Bin 61984 -> 62760 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98056 -> 98092 bytes sumfiles/gas.sum | 271 +++++++++++----------- sumfiles/ld.log.xz | Bin 131532 -> 131516 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 28 files changed, 387 insertions(+), 386 deletions(-)