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 abac248e6e 103: onsuccess: #555: 1: Success after binutils: 4 commits discards d25e28e78c 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 377ca3b8ec 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 3e43b603ab 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards b0476152f7 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 676f0cf703 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 1f8bdae73b 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 8da300098a 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 0158f81c7e 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards a703e9eadb 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 38538dfb7c 93: onsuccess: #544: 1: Success after linux: 34 commits discards 8fd9e1573a 92: onsuccess: #543: 1: Success after glibc: 4 commits discards cb1893f49e 91: onsuccess: #539: 1: Success after linux: 27 commits discards b1b4db7e9a 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 56227a2c8d 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 4164ab25b5 88: onsuccess: #534: 1: Success after linux: 12 commits discards 321ec2af38 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards e474f66a45 86: onsuccess: #532: 1: Success after gcc: 16 commits discards cf28b35a30 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 353277f3a7 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards e7d1842a8d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards b249b1827b 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 18ed867908 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 6bef4de301 80: onsuccess: #524: 1: Success after linux: 9 commits discards 5ad94a5bb1 79: onsuccess: #523: 1: Success after gcc: 25 commits discards a99c3cfe9b 78: onsuccess: #522: 1: Success after binutils: 10 commits discards aa5986b8a6 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 5b3853ead3 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 3aa57de521 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 4d7c766bac 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards e738bac6be 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 2ebae2dde1 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards f3940c9788 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 7b37aa68f4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards c4b776ae07 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 5d33f19037 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards e29a27cbc1 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 4bac4ba508 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 9a56b93a85 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 76e92905a0 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 24eaeb2e16 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 6b6da1d5ae 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 85c979acfa 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 6eee749f74 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards f996607869 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 63e164d472 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards fc3866fac8 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards c97d494eac 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 7ef1f04f6d 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 5c435bef93 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards f61472b6a3 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards bd6d73f188 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards b770c01f47 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 8f3d4bfb56 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 798dd24f10 49: onsuccess: #487: 1: Success after binutils: 11 commits discards e76cc810fc 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 35a0819e3b 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 9e614b1def 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 8889e16117 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards a470f91ce7 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 834b73db9a 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 2860d9147f 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards c710d4686f 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 9682110c33 40: onsuccess: #476: 1: Success after linux: 69 commits discards fd5e75a450 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 98ee4a58f4 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 4cd8f72b6b 37: onsuccess: #470: 1: Success after binutils: 3 commits discards c63fb34cd3 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards afd3e6b7ea 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 95382712f4 34: onsuccess: #465: 1: Success after binutils: 11 commits discards eccf85e4e9 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards ce00ab3a4e 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 1330fb13cd 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards c78c5ee6f0 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards dc3c80ce62 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 53e6137957 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 1abb752f45 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 267b962014 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 763653fd3a 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 10fa88f42a 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 8dc97fbd7c 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 0eb4230afd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 5edceeaba6 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 0a11c48874 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9b15f5359 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 46090cb5ed 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9dd047d30d 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 483c58e246 16: onsuccess: 1: Successful build after binutils: 5 commits discards 844a965cf3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c471689c73 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2ac5eb0a25 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ed577d9c13 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f312467766 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dedd904304 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9fdba1ca27 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards df09d40bb5 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1afc964d02 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 174d623996 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards ee20f88198 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 2fd5282033 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 9a094198bb 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new e2f61870e3 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d9616b420f 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5be3ab8829 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8bb4daac16 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 762831da46 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 44fd82a0fe 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 11eff99f34 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c11806102f 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8dcbdfd84a 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 984009b898 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd9a171b99 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3c05391a94 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 438dc7e872 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 13e7358cf1 16: onsuccess: 1: Successful build after binutils: 5 commits new 5eddef3f42 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 61084de701 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 803aa5bca7 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 38d6e13550 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b81c379261 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new e856615b74 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5aa3c614cb 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new c364621be4 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 5ef36060a7 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new fe97f82950 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 14914a420b 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 31991e0427 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new fb6053133b 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 3e72ab1be9 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new e15f78aad8 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 9eae8cc223 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 2cdbe28df6 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 934e4c1a7e 34: onsuccess: #465: 1: Success after binutils: 11 commits new 6998f01bc3 35: onsuccess: #467: 1: Success after glibc: 2 commits new 41cf9735ec 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new dcad91bac5 37: onsuccess: #470: 1: Success after binutils: 3 commits new d976841f9b 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 06b816a10a 39: onsuccess: #474: 1: Success after binutils: 8 commits new a3e9f6a6b8 40: onsuccess: #476: 1: Success after linux: 69 commits new 11c178e9b2 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new a4e98fc0db 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 99cb4ed2e4 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 1fc970dbf0 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 2aff08adb0 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 7e376bb4a5 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 76f22fbc7d 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new ef7c1ff324 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 4a74c73eb5 49: onsuccess: #487: 1: Success after binutils: 11 commits new 3c2aab2933 50: onsuccess: #490: 1: Success after binutils: 6 commits new 63d389a618 51: onsuccess: #493: 1: Success after binutils: 13 commits new 7ab3b411fc 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 56e48daed8 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new a44562e554 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new d69d314ee6 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new ffc5fbc2d7 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new be4b70fe43 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new f9939e3f5e 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 8e3cf91481 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 4949b88d22 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new abca1e1451 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 84d587b222 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 0192d4bd68 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new f44aa68960 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 248c274a52 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 050f083766 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new b35fc42541 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new cbef4a3e9c 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 6dd95eaa93 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 9c9679bd2c 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 5f25f0fc79 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 09bf924f16 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 996016ba57 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 7207705ac5 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 71b317b8ee 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new a076cd77b6 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 7c53fe4dc6 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 2ac9c75839 78: onsuccess: #522: 1: Success after binutils: 10 commits new 2a0c2fccde 79: onsuccess: #523: 1: Success after gcc: 25 commits new a9b4161d11 80: onsuccess: #524: 1: Success after linux: 9 commits new 0c355f7876 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new c8533d588d 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new ae3a877778 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 31af0ac255 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new bf6273d268 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 3eee9430e9 86: onsuccess: #532: 1: Success after gcc: 16 commits new 00ee09fe65 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 79c11d7e1c 88: onsuccess: #534: 1: Success after linux: 12 commits new efa4725f6a 89: onsuccess: #536: 1: Success after binutils: 27 commits new f16deed73c 90: onsuccess: #538: 1: Success after glibc: 10 commits new 6874f66657 91: onsuccess: #539: 1: Success after linux: 27 commits new d37a6bdbef 92: onsuccess: #543: 1: Success after glibc: 4 commits new e0b97874e8 93: onsuccess: #544: 1: Success after linux: 34 commits new e1299785c3 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 0d21d25e38 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new e620f162cd 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new c8912460a7 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 2bb8d9553e 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new c73f427874 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 8ce6da6529 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 9e9bcf36c1 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 823cc4453d 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new cddb1ab3aa 103: onsuccess: #555: 1: Success after binutils: 4 commits new 9fd3a81154 104: onsuccess: #558: 1: Success after binutils: 3 commits

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 (abac248e6e) \ 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 1652 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 51372 -> 50660 bytes 04-build_abe-gcc/console.log.xz | Bin 234512 -> 232076 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8936 -> 8912 bytes 07-build_abe-glibc/console.log.xz | Bin 237040 -> 235548 bytes 08-build_abe-gdb/console.log.xz | Bin 50432 -> 49892 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3816 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2524 -> 2580 bytes 11-check_regression/console.log.xz | Bin 4832 -> 4596 bytes 11-check_regression/mail-body.txt | 26 - 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 2908048 -> 2906292 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2512744 -> 2509392 bytes sumfiles/gcc.sum | 4820 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 953052 -> 947536 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229264 -> 229136 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 473492 -> 473968 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2567 insertions(+), 2619 deletions(-)