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 f7f389aa898 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 7b9e3c30903 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 923b1da7bf8 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 843dd2cabac 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 5b28c7922f3 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 3051ab80736 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 42b5dd8e9e1 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards c89f7660bc5 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards c6af5291e89 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards f2dba96df14 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 14e8b2a9b58 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 1303874afda 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards c757cef8aec 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 047460e1602 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 72997f35f8d 95: onsuccess: #619: 1: Success after binutils: 5 commits discards bd52b3592a1 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 5bf5fc2d82f 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 79c59142627 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards d1b1aafece0 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards e6c5947e048 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 0f83788fc50 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards b943a2bbec5 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards 55f0cf89881 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 372ba88ddcd 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 3cf98459317 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards 546a437ec78 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards cc33c5c33fa 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards b905fd46ce6 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards f9ba64ba6a6 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 4d2dd8edd48 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 568fb93cb49 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 4623cd6818d 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 154d79d53db 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 33e2bed0028 76: onsuccess: #592: 1: Success after linux: 63 commits discards 033a1b7a8f5 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 5a04b576e9a 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 2e5b61b968b 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 655afe9ff1a 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 8cb18fccfec 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 991c43da461 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards e3b02a12fd2 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 1200e874b55 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards e8fe385a0ce 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards fae0b5ccdfa 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards d9f07d25b1a 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 9c588a585b3 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 276217c1620 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 89d78d2d3dc 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 72eb2661bf0 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 83698f58299 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 2a82dba768f 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards 109601c83d6 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 16b080a5b9c 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 83878361255 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards 51999e34786 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards cde26f47c61 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards e0e034fba13 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards c99807ddf4a 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards b1acd27af89 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 16501fa5cca 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 3e696654e0e 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 812501e0e42 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 583ea5a919c 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 4d9e522b05d 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards af04c16ce16 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 73faef88872 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards e618ba4b502 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 289077a14a8 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 962f0d983be 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 43bd0dc61a2 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards f5825ce3e58 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 8c49dfdf42f 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards e6eaf1fdd0f 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 1cfd301400b 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 7197efb69a7 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards a9aa78956b1 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards f434649110c 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 005fd9b687f 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards b228bc4eff8 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 9b2c4f1e681 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards d2ca098f41d 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards e09dd5f5f73 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards e2453aeb827 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards b0a970c1373 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 8ba4eb916ff 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards d24706259f8 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 7db4efb9c3e 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards 9e5eafc7f34 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 8cf11dd8ff3 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 2e438edbb3a 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards b2d19c5f301 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards e6f738f6abd 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards b3f6229bbf6 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards ce01c8c6d63 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 772dcd4c52f 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 43f07e96114 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards be7d1daf8c2 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 92fe7e95772 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 59784495339 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 2816bc8c764 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 4f53ec6e869 9: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5b9fd8254a1 9: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f12173495cf 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 34569233b49 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 84e7defddd0 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new b2313a57ad0 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 62435199bb7 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a026f4b68a5 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 7c5b9e5cf0a 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 33d64ecaf6e 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 674bf6c029b 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 7e711b34604 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 3ad63201f56 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new e0eb6ac4bf0 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 06fe632da1c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 13bb3bfeb62 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 4d02b9b9a60 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new c039cf81ec4 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new ac12cc61e8b 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 97eed4d6258 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 25ae1064516 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 7b87f08e4ee 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 888ca257f72 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new ae61a076f26 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 4a6d8e9022a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new d2d31062436 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 554dd6b9884 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 235de73e43f 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 0ae47ff8fa0 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new cc4841aa95b 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new d005fc8b603 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 7ba9f26c2cd 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 2eb983d95fe 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 64699f1aa3b 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new c67f7f48bd7 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new fce3976dec8 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 5e4e4ed54c8 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new fc08f2520d4 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new c7c4daea9fb 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 60ffa4e33d5 47: onsuccess: #556: 1: Success after binutils: 12 commits new b32e2091505 48: onsuccess: #559: 1: Success after binutils: 6 commits new 57de4f50ac9 49: onsuccess: #562: 1: Success after binutils: 9 commits new 30a87fd4284 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new b3cd2cba31a 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 4909722f640 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 20fc6fb152d 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 2ef6f6e6b9a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new 812ab537545 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new df630f77353 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new b7c1de371a9 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new c9c26dd72e1 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new ea2944148bd 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 56bb6550d78 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 053b5207260 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new 56948fefb3b 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 6f26c5f4ab2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new c63d61e93d6 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 922901501da 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 6500b51db02 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 1c7c69b36ce 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 4ffd44c97e9 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new fb5fc82e799 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new fc364565a72 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 0d4ea2663fd 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new c4d26a572af 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new b2c27c36180 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 77727d2b85a 74: onsuccess: #590: 1: Success after binutils: 16 commits new 0105dca07af 75: onsuccess: #591: 1: Success after gcc: 25 commits new e1b606c8be5 76: onsuccess: #592: 1: Success after linux: 63 commits new d0dfc8b7518 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new b2bd531bfd0 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 0e50ed3d201 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new e22f8f29e55 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 01ecc9d7ff4 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 8eac4185e43 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 6595894fc70 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 9af929f66e5 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 0aaa5593863 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 396d1d961b9 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 17e0dcc3131 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 401d20f43c2 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new bceb4f58f93 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 06437a09795 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 1192d7548f9 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 989579466fb 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 9c6b26e3dbd 93: onsuccess: #613: 1: Success after binutils: 19 commits new 237bf2bf24d 94: onsuccess: #616: 1: Success after binutils: 2 commits new 288c0d67cd2 95: onsuccess: #619: 1: Success after binutils: 5 commits new e769cd8eb01 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 7172c5e6f69 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 2378e8e5936 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 3b3ba9ba508 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new faeaa37e890 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 951a2c67659 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 96a0e4067d5 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new b6e44f1d87f 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new c213fdf097c 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new b28b78a52ff 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 6ee3c35d541 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 68580d56073 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new b7c072969a2 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f8e9d9cb653 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 4ea433ee929 110: onsuccess: #639: 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 (f7f389aa898) \ 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 1712 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39988 -> 39980 bytes 04-build_abe-gcc/console.log.xz | Bin 216420 -> 214812 bytes 06-build_abe-linux/console.log.xz | Bin 9524 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 245160 -> 245228 bytes 08-build_abe-gdb/console.log.xz | Bin 38936 -> 38940 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3880 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2108 -> 2396 bytes 11-check_regression/console.log.xz | Bin 6192 -> 5780 bytes 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 60 ++++++++++++++--------------- 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 62880 -> 63020 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 81792 -> 81724 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 121768 -> 121768 bytes sumfiles/ld.sum | 4 +- 27 files changed, 61 insertions(+), 61 deletions(-)