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 287d24cd7e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards f1d7b97510 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 26c660248a 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 59b40686fd 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 370db0ee56 104: onsuccess: #530: 1: Success after gcc: 7 commits discards bf9f64fb37 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards eb30ce9272 102: onsuccess: #527: 1: Success after binutils: 5 commits discards d78966e50c 101: onsuccess: #524: 1: Success after binutils: 2 commits discards d90554b8e7 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 9c21c39d43 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 50fed4b674 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 214702f103 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 5560d4cc03 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 3a4c88379f 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 71dfedcefc 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 19ac391f01 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 7baacf52cf 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards e57c2f5afa 91: onsuccess: #511: 1: Success after linux: 27 commits discards fff4b3d43d 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 6e5f96a177 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 6686f09b75 88: onsuccess: #506: 1: Success after linux: 34 commits discards 3a749c6a74 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 71f9f61d06 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 1d61ba6852 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 0ec6734b0b 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 98618ebe2a 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 1c0b6dce3a 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 9e93a01e23 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards cd6e38183b 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 2414597e40 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards df212774d1 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards ad7df2737a 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 7e0f2fd461 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 9156f27712 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 8afedc8d02 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards f4e76bb40d 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards c13645a571 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 6e21e94885 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 2bf0af7e27 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 7deb6205c9 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards c93ad7c136 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards c7f90274ff 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 0525592848 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 63fd3a8e64 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 28dc3ddd3c 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 3eb8e986e5 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards b332fdc428 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 3988c9bb04 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 3c390720b7 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards 958494b2fe 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards a8524fbbe6 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards a64183f579 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards dcf2974fe0 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 4ca40f1cd4 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 57ff576f44 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 6ae7c3d6dc 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 01c30d8e2f 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 26eac894f8 51: onsuccess: #464: 1: Success after binutils: 6 commits discards d6fd713975 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 16050d88f0 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 3fcc7e4e4e 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 52d12507a5 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 2c23d659ef 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 9d94b7f1da 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 7577d160c4 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 34deba5245 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 50be5d34ff 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 7a48c9617e 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 10da263f03 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 8034782a08 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 1c33231e7e 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 8c7efea0c7 37: onsuccess: #443: 1: Success after binutils: 2 commits discards dbfccf4e62 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards bf34e3853e 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards dffb5c4480 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards b0a09bebf0 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 4ace75d870 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 76f26d6221 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 465c6b4b8c 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 45abf36478 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards b78111a888 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards e48c3bd1f5 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards 95b4a15e1c 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards dc3476ebdd 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards ba7b370050 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 4935a6c5d1 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 0c0cf289be 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c7bf4f8bb2 21: onsuccess: 1: Successful build after linux: 79 commits discards 60a0c8ff44 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bd484e013a 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc3f1bc356 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aaf5b29d53 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c7456afd1c 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 204d8ec79c 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aead8508b9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb3cec6ec9 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2146e2534 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards db51a45ce2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ef293c957a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 65a6a16765 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 94c3842a24 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b7762eeba7 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8bedb56ecf 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7cd391f436 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6cb6e3d19b 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fde594219f 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2257e45d1e 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e4491fb113 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 03535c8028 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad74332b24 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 77d3431ca2 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1edb5cdf69 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 599b3c005e 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5c8f95f59 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c81758a874 21: onsuccess: 1: Successful build after linux: 79 commits new f188f244b2 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ad2cb73833 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new f44293ef31 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 3d928bdedc 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 57b8b04bdd 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 01db5635c0 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 03a6ddfea5 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 75d8da61b6 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 7bb7f6a6b8 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new b97904859c 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 9f4a2dcced 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new c4a64dceef 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new c4c91c37a3 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 0814d7566f 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new c2f68f4e60 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 5b24468310 37: onsuccess: #443: 1: Success after binutils: 2 commits new 833906f841 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 102b5cbac5 39: onsuccess: #447: 1: Success after binutils: 5 commits new 1f6bcdbef8 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new b0e7326c52 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new fb0ec9e5a3 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 9e3a2e9e8f 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new e7c3612ae6 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 11f932f57d 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 0fb469a26b 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 25ed65debf 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 22892e9d5f 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new c867df8c64 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 82e3d9b317 50: onsuccess: #461: 1: Success after binutils: 12 commits new 62c897e8bf 51: onsuccess: #464: 1: Success after binutils: 6 commits new 176f3613cc 52: onsuccess: #467: 1: Success after binutils: 9 commits new 6773cc4ec4 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 779b6f81e1 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 1d955f99df 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 3c6f8083d4 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new ed6cc3d1b8 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new aede2b8a8a 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new b62faa5ea8 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 60de58428e 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 66e1f2c276 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 0f79e8bc08 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new b9e1ada0ce 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new dbc7b97132 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 531b79c34a 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new eb155e4b0a 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 1a941cc0f0 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new e9688ab0ed 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 57466b732e 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 7bd02f3eeb 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 87da74b40f 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 37a80a5487 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new c53e7d8658 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 732b0f0343 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 83edea58d0 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 8d3907205a 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new af8602111e 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 92e2328345 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 976d6ed284 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 875d29db23 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 96bd98cc9c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new e894bc99ff 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new df234bb994 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 1bf61e6634 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 0a3900adb5 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 7db2e4791c 86: onsuccess: #503: 1: Success after binutils: 12 commits new a01032d3a0 87: onsuccess: #505: 1: Success after glibc: 7 commits new 008df7d471 88: onsuccess: #506: 1: Success after linux: 34 commits new fd10c3aea5 89: onsuccess: #508: 1: Success after binutils: 12 commits new 74cd6be632 90: onsuccess: #510: 1: Success after glibc: 5 commits new 148e4f7e78 91: onsuccess: #511: 1: Success after linux: 27 commits new fe1a5c1703 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new fbfa707a15 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new ec009382e6 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 95331711cb 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 226172bbbf 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 9e008956a0 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 1012184d7d 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 8d346792cb 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 0769724829 100: onsuccess: #521: 1: Success after binutils: 10 commits new 6e99a01556 101: onsuccess: #524: 1: Success after binutils: 2 commits new 83c3c31759 102: onsuccess: #527: 1: Success after binutils: 5 commits new 4673605634 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new be46af1ddd 104: onsuccess: #530: 1: Success after gcc: 7 commits new 71939dc98a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new f5ce690a54 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new b8056990a5 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new a5c9ca67f6 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new d0af5deb57 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...]

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 (287d24cd7e) \ 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 1676 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52144 -> 52176 bytes 04-build_abe-gcc/console.log.xz | Bin 235608 -> 234268 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8320 bytes 07-build_abe-glibc/console.log.xz | Bin 235804 -> 235268 bytes 08-build_abe-gdb/console.log.xz | Bin 51356 -> 51592 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3868 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2072 -> 2216 bytes 11-check_regression/console.log.xz | Bin 5796 -> 5760 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 +- 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 62792 -> 62300 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98148 -> 98144 bytes sumfiles/gas.sum | 270 +++++++++++----------- sumfiles/ld.log.xz | Bin 131628 -> 131520 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 389 insertions(+), 389 deletions(-)