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 a18ac070a7 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 9e92628079 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards ac24f17f07 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 6d90e00691 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 26eeeaeae3 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 4cfdb91aa3 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 07b51ce88e 101: onsuccess: #524: 1: Success after binutils: 2 commits discards f28ed7c349 100: onsuccess: #521: 1: Success after binutils: 10 commits discards a47b67aa1e 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards a78be87388 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards b0e9c9403d 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards c65ed26f36 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards dd7da8dc2b 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards a855e12485 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards dcd0453d30 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards ff97ff0824 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards c006427254 91: onsuccess: #511: 1: Success after linux: 27 commits discards 130fd0ee5d 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 99fd9a5693 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 8392925f11 88: onsuccess: #506: 1: Success after linux: 34 commits discards d0be164842 87: onsuccess: #505: 1: Success after glibc: 7 commits discards d10bed8e08 86: onsuccess: #503: 1: Success after binutils: 12 commits discards a7873ae292 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards ca41b62715 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards fa0b743c16 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 279d9b6442 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 7ccbf1a67c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards a358aed9e8 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards feb60d39e5 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards f91954c1d2 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 4f8df9e802 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards ee06eabf14 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 5ff77300b4 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 1030ccc9d3 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards f5bab20e6b 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 3e8d3d04a5 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 8f403eb361 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards f8874a7210 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 432ac797ac 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 851eb7b42d 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards aa1484717a 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards b7074b8a90 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 27a8a3d9fb 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards b8be950d07 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 01ca5d0e2c 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards e79af8eaf8 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 94e151e97e 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards b88392b543 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards 26cac471ae 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 943e096804 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards a20a2067d9 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 9573690a53 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 6448498e74 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 45f3090000 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 295b6865f0 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 07d9c7a4c8 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 53e0dc23e6 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 209b68dcbd 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 991dc377f2 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 225867be73 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 2e58ca81d1 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 1ecbe348dc 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards ff9e5cf7a3 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 531c6acbd9 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards e891468256 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards c7b8ac1c89 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards b7da731790 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 26cba36e6a 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 59b0d433fd 39: onsuccess: #447: 1: Success after binutils: 5 commits discards c9b8bb79ee 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 8b3525a8a7 37: onsuccess: #443: 1: Success after binutils: 2 commits discards edab435d67 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 32dfa29de7 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards 4d63f69de1 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 1cd31589bc 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 0ebd320ee6 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards e910a6afa8 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards b3d595f402 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 44b01af75a 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 1af6e63770 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards a6bdffc719 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards 6d0fac6b56 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards fb394fdc00 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards edfb29cfa0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 679e7a59c4 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 24769a25a0 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 46ae7aebf0 21: onsuccess: 1: Successful build after linux: 79 commits discards 2fc1ac6c11 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ee97a9b078 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 505ffa5caf 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 35a0de10f3 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f2ae372c9f 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 50441c7600 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 46d45f63aa 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eed59c8cdc 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 25ed278907 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4a3a43f97e 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fa5dd1220d 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c387c10664 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 01a7de5ad6 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 4edc5edbb5 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cca8ac126f 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 94c3842a24 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 65a6a16765 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ef293c957a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new db51a45ce2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2146e2534 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fb3cec6ec9 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aead8508b9 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 204d8ec79c 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c7456afd1c 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aaf5b29d53 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new dc3f1bc356 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bd484e013a 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 60a0c8ff44 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c7bf4f8bb2 21: onsuccess: 1: Successful build after linux: 79 commits new 0c0cf289be 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4935a6c5d1 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new ba7b370050 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new dc3476ebdd 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 95b4a15e1c 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new e48c3bd1f5 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new b78111a888 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 45abf36478 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 465c6b4b8c 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new 76f26d6221 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 4ace75d870 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new b0a09bebf0 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new dffb5c4480 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new bf34e3853e 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new dbfccf4e62 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 8c7efea0c7 37: onsuccess: #443: 1: Success after binutils: 2 commits new 1c33231e7e 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 8034782a08 39: onsuccess: #447: 1: Success after binutils: 5 commits new 10da263f03 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 7a48c9617e 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 50be5d34ff 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 34deba5245 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 7577d160c4 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 9d94b7f1da 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 2c23d659ef 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 52d12507a5 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 3fcc7e4e4e 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 16050d88f0 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new d6fd713975 50: onsuccess: #461: 1: Success after binutils: 12 commits new 26eac894f8 51: onsuccess: #464: 1: Success after binutils: 6 commits new 01c30d8e2f 52: onsuccess: #467: 1: Success after binutils: 9 commits new 6ae7c3d6dc 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 57ff576f44 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 4ca40f1cd4 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new dcf2974fe0 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new a64183f579 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new a8524fbbe6 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new 958494b2fe 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 3c390720b7 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 3988c9bb04 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new b332fdc428 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 3eb8e986e5 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 28dc3ddd3c 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 63fd3a8e64 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 0525592848 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new c7f90274ff 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new c93ad7c136 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 7deb6205c9 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 2bf0af7e27 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 6e21e94885 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new c13645a571 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new f4e76bb40d 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 8afedc8d02 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 9156f27712 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 7e0f2fd461 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new ad7df2737a 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new df212774d1 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 2414597e40 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new cd6e38183b 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 9e93a01e23 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 1c0b6dce3a 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 98618ebe2a 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 0ec6734b0b 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 1d61ba6852 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 71f9f61d06 86: onsuccess: #503: 1: Success after binutils: 12 commits new 3a749c6a74 87: onsuccess: #505: 1: Success after glibc: 7 commits new 6686f09b75 88: onsuccess: #506: 1: Success after linux: 34 commits new 6e5f96a177 89: onsuccess: #508: 1: Success after binutils: 12 commits new fff4b3d43d 90: onsuccess: #510: 1: Success after glibc: 5 commits new e57c2f5afa 91: onsuccess: #511: 1: Success after linux: 27 commits new 7baacf52cf 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 19ac391f01 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 71dfedcefc 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 3a4c88379f 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 5560d4cc03 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 214702f103 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 50fed4b674 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 9c21c39d43 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new d90554b8e7 100: onsuccess: #521: 1: Success after binutils: 10 commits new d78966e50c 101: onsuccess: #524: 1: Success after binutils: 2 commits new eb30ce9272 102: onsuccess: #527: 1: Success after binutils: 5 commits new bf9f64fb37 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 370db0ee56 104: onsuccess: #530: 1: Success after gcc: 7 commits new 59b40686fd 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 26c660248a 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new f1d7b97510 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 287d24cd7e 108: onsuccess: #534: 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 (a18ac070a7) \ 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 1732 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 53568 -> 52144 bytes 04-build_abe-gcc/console.log.xz | Bin 234656 -> 235608 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8864 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 235380 -> 235804 bytes 08-build_abe-gdb/console.log.xz | Bin 52208 -> 51356 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3808 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2772 -> 2072 bytes 11-check_regression/console.log.xz | Bin 5964 -> 5796 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 34 +-- 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 62592 -> 62792 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 97980 -> 98148 bytes sumfiles/gas.sum | 270 +++++++++++----------- sumfiles/ld.log.xz | Bin 131500 -> 131628 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 387 insertions(+), 387 deletions(-)