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_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards d82579061c 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 3a67c18e2e 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards e6fe0667e0 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 0e4700b9e1 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 00edbea260 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 4b083c88f7 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 27409766c6 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 761dbd91df 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 08c5466d25 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 3a5aa0c0d0 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards c4ea5c3b1d 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards bad5552b53 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 0149107f87 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 1fce4582f3 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 4540494c4c 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards a1e5de619e 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 193ad967e3 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards aa8d93ede5 93: onsuccess: #544: 1: Success after linux: 34 commits discards 8ee522c736 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 10a2efdc8c 91: onsuccess: #539: 1: Success after linux: 27 commits discards c91bc3e154 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 0b7c3167c6 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 990c7efcac 88: onsuccess: #534: 1: Success after linux: 12 commits discards ae7612f3e5 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards ce70c81b98 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 100c01f8b6 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 3c39900626 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards ff86f4780b 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards cc71454d97 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 02f9ab0776 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards e047c39f50 80: onsuccess: #524: 1: Success after linux: 9 commits discards 206bef74f1 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 54ae1034b5 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 4d9d5f2bf2 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 88bec58af7 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 7c1d3b28e2 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 0518a37df3 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 6a11d88fa9 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards ef7e88bd1a 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 2826f1160c 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 0d8b579f02 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 9c93d069be 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 5bcdd909fd 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 4d953590e2 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 6c8b3f3067 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards a738248326 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards cb1f463a64 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 52bf7a6642 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards f225baf55b 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards ca77644a6e 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 8db53363a5 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards c1b74543b9 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 91b936ec0b 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 84a2fb3b8f 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 39054b7b3c 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 817ab8248d 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 9f8626c545 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 4f0972e0f0 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards d1beb46b04 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards f87f536e73 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 6a4e60fd9a 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 07ebc99f7f 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 368169fc38 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 2bd1c7be06 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 856120e74d 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 9b58173b2a 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 1cbc183eb5 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 4ec82faae3 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards c603d8f809 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 3e56003f4d 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards b1a82fd42d 40: onsuccess: #476: 1: Success after linux: 69 commits discards 4125b7aed5 39: onsuccess: #474: 1: Success after binutils: 8 commits discards c55fa27901 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards abb28e5e89 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 48f91dcd43 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards edf8287508 35: onsuccess: #467: 1: Success after glibc: 2 commits discards eed9ad45b6 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 1a9ebad3a9 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 545b2a5eef 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards f912a7402c 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 11be870bcc 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards ee6378694a 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards bfadcb5e1b 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 0f68e1e232 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards de3570907d 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 1379caeb8f 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 3000873a13 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 413621977d 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 3197065cf9 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 2bde71c5a1 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards e1e9e63710 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c56dc3a8a 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c6db424d72 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cc6db62108 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6fc55176cf 16: onsuccess: 1: Successful build after binutils: 5 commits discards 11c9b5921b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7151f18e78 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c1e282e191 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 88fb141cdf 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9bf1e74ad5 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9457578788 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f71afc7af7 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 488556dce1 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a93bdf849f 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3f19f371cd 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new be945bba4a 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4040019f9f 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1877c443b1 16: onsuccess: 1: Successful build after binutils: 5 commits new 889a352541 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74204ada5f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b533208c7e 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 28d8f12663 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d0a278cb03 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new a9409c9c2f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 46e44123e1 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new bbd9a1ef61 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new a0ce029cce 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 48c74a4ff4 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new fcbebc5d0d 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new d669c85923 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 064143a160 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 7d01a85af6 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 0bac764b90 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 4c3c92bc38 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new b5f7c9ab79 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 34e2a6037b 34: onsuccess: #465: 1: Success after binutils: 11 commits new e9f92bfc5f 35: onsuccess: #467: 1: Success after glibc: 2 commits new aabaf7f8eb 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 91cd65a0a4 37: onsuccess: #470: 1: Success after binutils: 3 commits new dd489baaec 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 4186333b81 39: onsuccess: #474: 1: Success after binutils: 8 commits new 53e9e3a449 40: onsuccess: #476: 1: Success after linux: 69 commits new c606a60186 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 551d79fb3f 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 725e71d92e 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new c5352c96ff 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 72e34c08ab 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 18e875e286 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 32852ccfe8 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 0c32951b95 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new aff05c8530 49: onsuccess: #487: 1: Success after binutils: 11 commits new 3d314a3d8d 50: onsuccess: #490: 1: Success after binutils: 6 commits new be903f8dd6 51: onsuccess: #493: 1: Success after binutils: 13 commits new 2f596b5520 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new c052246116 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new a2a9028091 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new e6ffb15d73 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new bf3c946560 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 8d8ab501cf 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 32a3c84912 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new a8c91648df 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new fa2f03a735 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new f598cfa19e 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 42042388e0 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new ffd57455f5 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 5b7b83996c 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new a460bebc79 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new ee1b98a2ea 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new ed94699f17 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 14adfc6278 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new b14e34c1a1 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 0111a690ca 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 42c561c114 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 615a5ba163 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 02328ab382 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 952124edb5 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 25a4dda3cd 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 6657fd0c85 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new c1f591dacd 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 1b551d08b1 78: onsuccess: #522: 1: Success after binutils: 10 commits new ce4ca8b7d1 79: onsuccess: #523: 1: Success after gcc: 25 commits new 603afbfb05 80: onsuccess: #524: 1: Success after linux: 9 commits new 85f69e4417 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 786b615ae4 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new b428878974 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 7939183964 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 560fe786f0 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 1d073c442e 86: onsuccess: #532: 1: Success after gcc: 16 commits new 6beaf6ad9f 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 7dadfff316 88: onsuccess: #534: 1: Success after linux: 12 commits new 1ef569f559 89: onsuccess: #536: 1: Success after binutils: 27 commits new 81834205b5 90: onsuccess: #538: 1: Success after glibc: 10 commits new fcf73b3246 91: onsuccess: #539: 1: Success after linux: 27 commits new 726ec37c47 92: onsuccess: #543: 1: Success after glibc: 4 commits new 880733cc16 93: onsuccess: #544: 1: Success after linux: 34 commits new e9129b30d6 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 6eb8632d15 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 3882865984 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 01c6f43a85 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 41095286cb 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 362ba0578f 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new a958132909 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 534f002b83 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 1ddfdeb5c8 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 1f753c950b 103: onsuccess: #555: 1: Success after binutils: 4 commits new eb3d3aa359 104: onsuccess: #558: 1: Success after binutils: 3 commits new 640e2ada37 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 27461a4d08 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 0e9a49ec1e 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 0ee117d8c5 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 786a47f7dd 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 718c7cd12e 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new fc70488a51 111: onsuccess: #566: 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 (d82579061c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 1700 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 53944 -> 52440 bytes 04-build_abe-gcc/console.log.xz | Bin 234804 -> 235860 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 235768 -> 235704 bytes 08-build_abe-gdb/console.log.xz | Bin 51752 -> 51240 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3824 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2708 -> 2528 bytes 11-check_regression/console.log.xz | Bin 9072 -> 6776 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 13 +- 11-check_regression/mail-body.txt | 77 +- 11-check_regression/results.compare | 37 +- 11-check_regression/results.compare2 | 559 +--- 11-check_regression/results.regressions | 37 +- 12-update_baseline/console.log | 46 +- 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 | 79 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 37 +- sumfiles/g++.log.xz | Bin 2904944 -> 2908704 bytes sumfiles/g++.sum | 154 +- sumfiles/gcc.log.xz | Bin 2512996 -> 2518308 bytes sumfiles/gcc.sum | 4645 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 952276 -> 950476 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229092 -> 227924 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465504 -> 465820 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2664 insertions(+), 3146 deletions(-)