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 d3455e5b11 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards c60fed6392 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 417d880b4a 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards aed19d80e7 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards f02cf191fc 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 1d140d9062 104: onsuccess: #558: 1: Success after binutils: 3 commits discards e9aaa438ec 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 5f8886f3a5 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 0df0e067a8 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 5edf5109fb 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards a12a73e435 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 29612b3f0a 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards fba0c8b09e 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards cc6cc0de61 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards d10f9ddced 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 916ba53cf8 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards cd3928814c 93: onsuccess: #544: 1: Success after linux: 34 commits discards ab3b840a4c 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 3911fe1fb6 91: onsuccess: #539: 1: Success after linux: 27 commits discards 6af4a48abb 90: onsuccess: #538: 1: Success after glibc: 10 commits discards a9aa6b978e 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 9c6b3a6c5b 88: onsuccess: #534: 1: Success after linux: 12 commits discards 3b0aca9f68 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 96a4a5b63e 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 9d750797d9 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 590e86a1e6 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards b004a3802d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 8de3b0887f 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards afd22b2fd4 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards acde30875a 80: onsuccess: #524: 1: Success after linux: 9 commits discards 0ab860e3e6 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 90589bece8 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 76bc074316 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards cdd7aafd5a 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards fa7621b0fd 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards e3597d4b52 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards c927efb591 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 43441f1b45 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards e93642214a 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 08f99562f4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 1ade13129c 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 980872f183 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 6a431c1ac1 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards df759d6aa5 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards a5a1362429 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 46afd83ae1 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards cc5e6535a5 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards ee01549bc9 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 9733842e56 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 4a9914e550 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 7f047c6f3a 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 055a36ee09 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards c8ed8dd9d9 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards d0436df8b0 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 6379025f3c 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 39116f1ef2 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 97f7f196e5 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 51206f0110 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards d65f5ad4ae 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 81ee40229c 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 6a1da501d3 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 633b4e28bf 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 8abd0b050f 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards f4ee5c183e 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards a227d0aef4 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards cb2cc6a5a0 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 7f40d71055 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards a8b56e7e32 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 1cc11ac9be 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 471341300f 40: onsuccess: #476: 1: Success after linux: 69 commits discards 481bba00db 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 36b0983acd 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 779ad6a776 37: onsuccess: #470: 1: Success after binutils: 3 commits discards b5a616c6d9 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards f67c65e3c1 35: onsuccess: #467: 1: Success after glibc: 2 commits discards b67e8f821b 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 93664f5dcf 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards f47a05950c 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 82139aeb71 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 37bebfcdee 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards ac4f58efd8 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards e2c046aa08 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 7da8bd11f9 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards fff10839ca 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 19bf6bf752 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards bda273d793 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 9b721f83a8 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 81054bad64 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 9a5d0b8b82 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 1d3a94b13d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 29e96a7549 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards af296a20dc 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0d029ec653 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3a9083009b 16: onsuccess: 1: Successful build after binutils: 5 commits discards 75a1dd981b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f94fcbc0b6 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 408e49243d 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b544b7412f 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9c66a35998 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aa1e07ad02 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 74ec205a05 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fba7edfe84 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9457578788 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9bf1e74ad5 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 88fb141cdf 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c1e282e191 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7151f18e78 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 11c9b5921b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6fc55176cf 16: onsuccess: 1: Successful build after binutils: 5 commits new cc6db62108 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c6db424d72 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c56dc3a8a 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e1e9e63710 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2bde71c5a1 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 3197065cf9 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 413621977d 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new 3000873a13 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 1379caeb8f 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new de3570907d 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 0f68e1e232 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new bfadcb5e1b 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new ee6378694a 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 11be870bcc 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new f912a7402c 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 545b2a5eef 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 1a9ebad3a9 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new eed9ad45b6 34: onsuccess: #465: 1: Success after binutils: 11 commits new edf8287508 35: onsuccess: #467: 1: Success after glibc: 2 commits new 48f91dcd43 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new abb28e5e89 37: onsuccess: #470: 1: Success after binutils: 3 commits new c55fa27901 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 4125b7aed5 39: onsuccess: #474: 1: Success after binutils: 8 commits new b1a82fd42d 40: onsuccess: #476: 1: Success after linux: 69 commits new 3e56003f4d 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new c603d8f809 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 4ec82faae3 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 1cbc183eb5 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 9b58173b2a 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 856120e74d 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 2bd1c7be06 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 368169fc38 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 07ebc99f7f 49: onsuccess: #487: 1: Success after binutils: 11 commits new 6a4e60fd9a 50: onsuccess: #490: 1: Success after binutils: 6 commits new f87f536e73 51: onsuccess: #493: 1: Success after binutils: 13 commits new d1beb46b04 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 4f0972e0f0 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 9f8626c545 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 817ab8248d 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 39054b7b3c 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 84a2fb3b8f 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 91b936ec0b 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new c1b74543b9 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 8db53363a5 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new ca77644a6e 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new f225baf55b 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 52bf7a6642 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new cb1f463a64 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new a738248326 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 6c8b3f3067 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 4d953590e2 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 5bcdd909fd 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 9c93d069be 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 0d8b579f02 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 2826f1160c 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new ef7e88bd1a 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 6a11d88fa9 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 0518a37df3 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 7c1d3b28e2 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 88bec58af7 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 4d9d5f2bf2 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 54ae1034b5 78: onsuccess: #522: 1: Success after binutils: 10 commits new 206bef74f1 79: onsuccess: #523: 1: Success after gcc: 25 commits new e047c39f50 80: onsuccess: #524: 1: Success after linux: 9 commits new 02f9ab0776 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new cc71454d97 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new ff86f4780b 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 3c39900626 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 100c01f8b6 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new ce70c81b98 86: onsuccess: #532: 1: Success after gcc: 16 commits new ae7612f3e5 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 990c7efcac 88: onsuccess: #534: 1: Success after linux: 12 commits new 0b7c3167c6 89: onsuccess: #536: 1: Success after binutils: 27 commits new c91bc3e154 90: onsuccess: #538: 1: Success after glibc: 10 commits new 10a2efdc8c 91: onsuccess: #539: 1: Success after linux: 27 commits new 8ee522c736 92: onsuccess: #543: 1: Success after glibc: 4 commits new aa8d93ede5 93: onsuccess: #544: 1: Success after linux: 34 commits new 193ad967e3 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new a1e5de619e 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 4540494c4c 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 1fce4582f3 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 0149107f87 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new bad5552b53 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new c4ea5c3b1d 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 3a5aa0c0d0 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 08c5466d25 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 761dbd91df 103: onsuccess: #555: 1: Success after binutils: 4 commits new 27409766c6 104: onsuccess: #558: 1: Success after binutils: 3 commits new 4b083c88f7 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 00edbea260 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 0e4700b9e1 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new e6fe0667e0 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 3a67c18e2e 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new d82579061c 110: onsuccess: #565: 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 (d3455e5b11) \ 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 1688 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 54096 -> 53944 bytes 04-build_abe-gcc/console.log.xz | Bin 235040 -> 234804 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8820 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 236328 -> 235768 bytes 08-build_abe-gdb/console.log.xz | Bin 52256 -> 51752 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3816 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3584 -> 2708 bytes 11-check_regression/console.log.xz | Bin 7264 -> 9072 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 13 +- 11-check_regression/mail-body.txt | 67 +- 11-check_regression/results.compare | 40 +- 11-check_regression/results.compare2 | 645 +++- 11-check_regression/results.regressions | 40 +- 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 | 69 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 40 +- sumfiles/g++.log.xz | Bin 2863516 -> 2904944 bytes sumfiles/g++.sum | 608 +++- sumfiles/gcc.log.xz | Bin 2536520 -> 2512996 bytes sumfiles/gcc.sum | 5194 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 951896 -> 952276 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229060 -> 229092 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 469432 -> 465504 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 4001 insertions(+), 2905 deletions(-)