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 4ea433ee929 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards f8e9d9cb653 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards b7c072969a2 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 68580d56073 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 6ee3c35d541 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards b28b78a52ff 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards c213fdf097c 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards b6e44f1d87f 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 96a0e4067d5 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 951a2c67659 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards faeaa37e890 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 3b3ba9ba508 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 2378e8e5936 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 7172c5e6f69 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards e769cd8eb01 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 288c0d67cd2 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 237bf2bf24d 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 9c6b26e3dbd 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 989579466fb 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 1192d7548f9 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 06437a09795 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards bceb4f58f93 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 401d20f43c2 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards 17e0dcc3131 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 396d1d961b9 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 0aaa5593863 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards 9af929f66e5 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 6595894fc70 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 8eac4185e43 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 01ecc9d7ff4 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards e22f8f29e55 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 0e50ed3d201 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards b2bd531bfd0 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards d0dfc8b7518 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards e1b606c8be5 76: onsuccess: #592: 1: Success after linux: 63 commits discards 0105dca07af 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 77727d2b85a 74: onsuccess: #590: 1: Success after binutils: 16 commits discards b2c27c36180 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards c4d26a572af 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 0d4ea2663fd 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards fc364565a72 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards fb5fc82e799 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 4ffd44c97e9 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 1c7c69b36ce 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 6500b51db02 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 922901501da 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards c63d61e93d6 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 6f26c5f4ab2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 56948fefb3b 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 053b5207260 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 56bb6550d78 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards ea2944148bd 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards c9c26dd72e1 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards b7c1de371a9 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards df630f77353 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards 812ab537545 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 2ef6f6e6b9a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 20fc6fb152d 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards 4909722f640 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards b3cd2cba31a 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 30a87fd4284 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 57de4f50ac9 49: onsuccess: #562: 1: Success after binutils: 9 commits discards b32e2091505 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 60ffa4e33d5 47: onsuccess: #556: 1: Success after binutils: 12 commits discards c7c4daea9fb 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards fc08f2520d4 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 5e4e4ed54c8 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards fce3976dec8 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards c67f7f48bd7 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 64699f1aa3b 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 2eb983d95fe 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 7ba9f26c2cd 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards d005fc8b603 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards cc4841aa95b 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 0ae47ff8fa0 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 235de73e43f 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 554dd6b9884 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards d2d31062436 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 4a6d8e9022a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards ae61a076f26 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 888ca257f72 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 7b87f08e4ee 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 25ae1064516 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 97eed4d6258 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards ac12cc61e8b 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards c039cf81ec4 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 4d02b9b9a60 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 13bb3bfeb62 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards 06fe632da1c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards e0eb6ac4bf0 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 3ad63201f56 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 7e711b34604 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 674bf6c029b 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 33d64ecaf6e 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 7c5b9e5cf0a 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards a026f4b68a5 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 62435199bb7 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards b2313a57ad0 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 84e7defddd0 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 34569233b49 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f12173495cf 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 70f977b8936 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2ca866992f1 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 0e6943aa09f 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 0c5dc994dad 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f6e4a0649cc 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new afd6377e48b 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d5ca9440c0f 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new fef311d9519 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new f49404e82eb 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new df8b01eeb2a 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 434122f8f64 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 67376c66cdc 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new e15d5fc2f8c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 25ce6bfabd9 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new a41d23dc991 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 3ae454ef417 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new e47d19341cb 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new de991480684 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 576c19bbd3e 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 800a0143bb6 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new ad0a45737b9 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 5c953af2a19 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 3575c6f8a3a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 545530a500b 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new ecacee2839c 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new ec57862b063 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 8ee5cb8a9fa 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 8d634a2af90 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new 878c87b920f 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 62e677adf8f 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new c1ef1af5f1b 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new d8d2b2755dd 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 14611c51a0f 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new fe43447b353 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 261aa5f0167 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 8df0a0b92c1 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 1b4f63faf58 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new f7215f6f93f 47: onsuccess: #556: 1: Success after binutils: 12 commits new 9bca1a60abf 48: onsuccess: #559: 1: Success after binutils: 6 commits new 1a79b3a809f 49: onsuccess: #562: 1: Success after binutils: 9 commits new 596b5f8ee3e 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 52d62839c6a 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 0864933e204 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 590052979be 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 4adecfa508e 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new d8b50f816df 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new ed8485898ef 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new b7517b130ca 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 556f2145448 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 49dfc30fcbd 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 682167cff2e 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 0e4ed430610 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new a0b20dbab29 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 1895f1fbfc2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 04cb305ca9c 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 3b2da97be16 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new f92d9163804 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new e9f980bf174 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 638ac7bb139 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 85240dcc824 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 18bc1bc596c 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 470beabe7e6 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 44861170d15 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 63ceea6a67c 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 136d6071547 74: onsuccess: #590: 1: Success after binutils: 16 commits new 1617aa27c09 75: onsuccess: #591: 1: Success after gcc: 25 commits new 33ca4209d62 76: onsuccess: #592: 1: Success after linux: 63 commits new 44c69a79b20 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 8cd22419b98 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 19a4ef14468 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 5d98573c29d 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 0d542d97d78 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new e5bc8e15271 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new f58655c7caa 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 7e9437ae4b8 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new c441ed542e0 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 490b29612b8 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new ab773c50ffd 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new f26276cc38e 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 8bea2b753f0 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new e02f4dc37a6 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 1b427f3680b 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 27ade6b303f 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new d2420ebcc06 93: onsuccess: #613: 1: Success after binutils: 19 commits new e34c04d550b 94: onsuccess: #616: 1: Success after binutils: 2 commits new 88cd6fa6bea 95: onsuccess: #619: 1: Success after binutils: 5 commits new 1e934dbee64 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 00d77ef3b0d 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 6c7e791ccb8 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 1880152e978 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new b304eee0e72 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new d64f6822f85 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 6f3ea872d5c 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new 8b39d89042a 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 20d23a664c7 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 3f295bcf3b4 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 1fb0f4fd419 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 1e1c2d20ce4 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new ceb5d3eab59 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new ec8f1b228b6 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 6e50e49e767 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 9bda320d068 111: onsuccess: #640: 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 (4ea433ee929) \ 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 1720 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39980 -> 40180 bytes 04-build_abe-gcc/console.log.xz | Bin 214812 -> 213732 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 245228 -> 245104 bytes 08-build_abe-gdb/console.log.xz | Bin 38940 -> 39236 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3840 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2396 -> 2276 bytes 11-check_regression/console.log.xz | Bin 5780 -> 5968 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 64 +++--- 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 | 34 +-- sumfiles/binutils.log.xz | Bin 63020 -> 63012 bytes sumfiles/binutils.sum | 65 +++--- sumfiles/gas.log.xz | Bin 81724 -> 81800 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121768 -> 121704 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 417 insertions(+), 408 deletions(-)