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_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 90ded0a9a29 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 52fc1919e7c 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 9773f9329c4 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards b52ca505526 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 82c0173921f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 479403ce7b1 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 58aff58d46d 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 5ec35146a95 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards a2233a0d33d 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 182ea5ec9fa 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 6ddb43a3413 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 54952b51d40 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 5f71a0c023e 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 9cb1c9dffe0 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards f3f7747bac7 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards e39ecbfa81e 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards e5bbd8971d4 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 2cd725acbfe 91: onsuccess: #870: 1: Success after binutils: 5 commits discards b957f7583d6 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 3234d0b01f4 89: onsuccess: #864: 1: Success after binutils: 25 commits discards bcd4926b3e1 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 30dfa599c35 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards f057e78ff06 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards fc974256542 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 12df62a6c84 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 71f4ef31f0e 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 24bf2a16896 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 345887f98b2 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards cdf3497171f 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 62ce0d0fc3f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards b90813fdd5a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards dacd5ac69bf 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 22215c4722e 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 652723c6116 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 94d201bafe7 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 61c195737d2 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 79f90493d26 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 3c2404e9fc5 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 7a400e26c0d 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 99fdd99a021 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 79f57d92e93 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 24eb8358cd0 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards c044e587eab 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards 76afea8bd1e 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 665b5280991 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards e69cd2f2e88 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards ed8bec921b4 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards ff20eb5abf5 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 998c525c029 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards b29b448e8ff 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 0a703d22b94 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 4e8e8f4ecb7 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 226e69ad3d4 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 8154077931c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 4257f166c70 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 9e28044c91d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards b94c70003ea 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 0ed2cc7f1bf 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 3b90dbc510d 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 7778b31f3ef 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards be1f6b9595e 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards cb59db10aa1 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 0c43d24b899 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 9d2228c03b8 45: onsuccess: #815: 1: Success after binutils: 6 commits discards ee7eb8bc489 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards fbb5c2408dc 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 035d3ff0cb1 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards fecefe96d2d 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 70aa9c04116 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards ebfd75fb6f3 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 4be997e57a5 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 035747ec9f8 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards b91738ae7af 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards ff30f395d59 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 0fa04323b8c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards ac81414b15c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 4d9b9c91cb9 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards cd4f354a888 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards bbde7e309c0 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 69ce0c7d33c 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 655eee17618 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards c28297bf811 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards 3e664e59fc2 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 3bc84502cc1 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards a87f289d142 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 506e3356611 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards 157b38aec53 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards d45d57129bc 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards dd39e607bd0 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards d9942448382 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 9047bfb392a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 4afdfc69e0a 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f01a1481290 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards f635cf163a1 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 2d3bc82a411 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 92febf28b36 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 875c0c9a1b4 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 25a98c17e31 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 669b43737de 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 05e36a3a7c6 9: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6adf561555d 8: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d013aa1e3d4 8: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 04259bd116d 9: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 23e580c6eef 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c69bdcb9fcd 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c9ea035bf80 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 120a8224ec0 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 40d2a0a420a 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 8c3dba16627 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new fd8d1f7a946 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 9141e299ebc 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 274e838d32a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 65b33dfa8af 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 78711654ff0 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new fa9975a84dc 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new fdbd3bcac57 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 3088a794acb 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 44f04e88816 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 93c17acb2e7 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 9328338abab 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 142c96d413e 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 9963fcc4b45 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new e8ca8d9c92f 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new c590f09a003 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 98c74b159a5 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 56afcf34a15 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new fadde1a68b2 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 2e05204d4e5 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new d120c25dc8c 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 4d6ae35afdd 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 952b05b3feb 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new c2e84626c39 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 3796b4f6394 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 978735e6ea2 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 65ddaf392f7 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new e7cb25af6dd 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 21d78473a48 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new a895fc5950d 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 4b496a956d0 45: onsuccess: #815: 1: Success after binutils: 6 commits new b85c1850ae4 46: onsuccess: #818: 1: Success after binutils: 10 commits new 26655ab0ef4 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new cf74a5acb57 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 70d0e9b8bcd 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 801d08c69ab 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new ac9a5b8f04a 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new e346c2b6e25 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 7b78b002c5a 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 219f37bedbf 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 672c7c178e5 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 324c464097d 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 0ff0895c7a0 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new 9764bb2fe55 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new 819843fd455 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new f9d0b292924 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 7ac3d42a190 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 1867c649fc7 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 89b28d28210 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 1a2dc9089c2 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new e63eba628e4 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new e8d2501aab9 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 8c063638779 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new f6d849ffbec 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 876afd05f49 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new a5eab01e5e2 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new c5196f42340 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new f2967a9c038 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 4d56b868a80 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 47cfa76d201 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 05412882049 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new 54c633eb851 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new 7504a944e50 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 9055183d2a3 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new 4abfd9ea2a1 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new f1fcc3e9e33 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 4d0dc55c701 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 13a96117f04 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 72fc8fd06f3 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new d9e552e2e6a 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 8125b03f117 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new fdf3c3ac361 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 3ac73b2cbe7 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new 6829413adb0 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 9f24d7ee07a 89: onsuccess: #864: 1: Success after binutils: 25 commits new 8f3a619413a 90: onsuccess: #867: 1: Success after binutils: 4 commits new 12a405a483b 91: onsuccess: #870: 1: Success after binutils: 5 commits new 20f474748aa 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new e1566d79db6 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 12a4b2c0b4d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new ae6bd66b529 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new 0c4f80e8975 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new fcec0b2e4fa 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new b0c565b846b 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 0e2a67de4e8 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 349c5584244 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new f621ef2c7de 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 7dd91b1d793 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 5056df45e7b 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 9e1daca0d2b 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 5543dd5fb61 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 34d6ef495c7 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new ff41a8368a5 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 59ab96293a9 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 772caeb290c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...]

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 (90ded0a9a29) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/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 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 38936 -> 39152 bytes 04-build_abe-gcc/console.log.xz | Bin 213400 -> 213636 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8768 -> 8512 bytes 07-build_abe-glibc/console.log.xz | Bin 244892 -> 244732 bytes 08-build_abe-gdb/console.log.xz | Bin 38708 -> 38788 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2020 -> 2024 bytes 11-check_regression/console.log.xz | Bin 13936 -> 16092 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 35 +- 11-check_regression/mail-body.txt | 181 +- 11-check_regression/results.compare | 87 +- 11-check_regression/results.compare2 | 7264 +++++++++++++++------------ 11-check_regression/results.regressions | 87 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 183 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 87 +- sumfiles/gdb.log.xz | Bin 1936228 -> 1934320 bytes sumfiles/gdb.sum | 8344 ++++++++----------------------- 31 files changed, 6404 insertions(+), 9984 deletions(-)