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 772caeb290c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 59ab96293a9 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards ff41a8368a5 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 34d6ef495c7 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 5543dd5fb61 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 9e1daca0d2b 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 5056df45e7b 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 7dd91b1d793 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards f621ef2c7de 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 349c5584244 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 0e2a67de4e8 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards b0c565b846b 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards fcec0b2e4fa 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 0c4f80e8975 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards ae6bd66b529 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 12a4b2c0b4d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards e1566d79db6 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 20f474748aa 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 12a405a483b 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 8f3a619413a 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 9f24d7ee07a 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 6829413adb0 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 3ac73b2cbe7 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards fdf3c3ac361 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 8125b03f117 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards d9e552e2e6a 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 72fc8fd06f3 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 13a96117f04 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 4d0dc55c701 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards f1fcc3e9e33 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 4abfd9ea2a1 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 9055183d2a3 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards 7504a944e50 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 54c633eb851 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 05412882049 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 47cfa76d201 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 4d56b868a80 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards f2967a9c038 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards c5196f42340 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards a5eab01e5e2 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 876afd05f49 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards f6d849ffbec 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 8c063638779 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards e8d2501aab9 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards e63eba628e4 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 1a2dc9089c2 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 89b28d28210 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 1867c649fc7 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 7ac3d42a190 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards f9d0b292924 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards 819843fd455 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 9764bb2fe55 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 0ff0895c7a0 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 324c464097d 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 672c7c178e5 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 219f37bedbf 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 7b78b002c5a 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards e346c2b6e25 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards ac9a5b8f04a 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 801d08c69ab 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 70d0e9b8bcd 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards cf74a5acb57 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 26655ab0ef4 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards b85c1850ae4 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 4b496a956d0 45: onsuccess: #815: 1: Success after binutils: 6 commits discards a895fc5950d 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 21d78473a48 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards e7cb25af6dd 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 65ddaf392f7 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 978735e6ea2 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 3796b4f6394 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards c2e84626c39 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 952b05b3feb 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 4d6ae35afdd 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards d120c25dc8c 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 2e05204d4e5 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards fadde1a68b2 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 56afcf34a15 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 98c74b159a5 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards c590f09a003 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards e8ca8d9c92f 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 9963fcc4b45 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 142c96d413e 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards 9328338abab 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 93c17acb2e7 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 44f04e88816 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 3088a794acb 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards fdbd3bcac57 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards fa9975a84dc 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards 78711654ff0 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 65b33dfa8af 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 274e838d32a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 9141e299ebc 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards fd8d1f7a946 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 8c3dba16627 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 40d2a0a420a 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 120a8224ec0 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c9ea035bf80 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c69bdcb9fcd 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 23e580c6eef 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 04259bd116d 9: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8d7bc7dea9c 9: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c8cfff784eb 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 3f21b7fd7ee 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a4ce27473ca 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4117028f0aa 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 696a4bbbaa4 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 9ce9dccbf03 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c8f06f3a935 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 3d3e955140c 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 401e84af063 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 078591b90dc 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f5ccd3caf41 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new df8d28c499d 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 776904c17ad 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 0aecb34d5bd 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new e18930eaccf 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new f0df9440f66 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new eddb3de0600 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new d93d710a098 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 9e45c734acd 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 32637032785 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new 63cb993c607 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new e6fd7bef033 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new eabfe22392c 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new ec390f478c5 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 8b2dc023f2c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new e6a5496feba 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new b73367f8240 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 0bed511fb0a 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 7a19c0cbf0d 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 5ef7c223a14 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new dd60dbaa5a9 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 5a999ba8f0a 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 1b7c890e05a 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 05809978426 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new d98c0ad427c 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 6c6406045b6 45: onsuccess: #815: 1: Success after binutils: 6 commits new 0d8dd102b94 46: onsuccess: #818: 1: Success after binutils: 10 commits new 6e7563fd5cd 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new c330f5c223e 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 7829e61729c 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 4d79fe5a178 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new c0208c8a9e4 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new e1485d6f9bc 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new fe4889f97a5 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new d82db0a83ad 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 154fbd6a5fe 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new acaf6b9065e 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new fcbfe4f59d1 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new 42a2cb2dcbf 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new 2e3ceeac7cb 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new ee36ffc7fe9 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 2bf5f063af1 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new bde825ccf43 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 37dceff3f8c 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 75555a7ddaa 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new eabde38348e 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 3594c4723f4 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 0738a8190cc 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 5e4961eb6ab 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new d60ad100ed6 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new d00696a8a4a 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new c3ba0c87417 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 6a7a279251f 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new efe46673095 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 79ec8eb155b 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 8f003fb5859 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new 39afb42292c 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new 57df1f0b69a 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 2298e059c0f 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new 65fc7ba5d5c 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 09ed55bec38 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 91c1a5f17f0 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 96476a5cec7 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new e2f24c990b9 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new a4965c10bae 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 7b507ad01b8 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new d69ca859dd1 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 54602e26633 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new 9f8c29c6675 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 95607166576 89: onsuccess: #864: 1: Success after binutils: 25 commits new a21ef7424aa 90: onsuccess: #867: 1: Success after binutils: 4 commits new fa3b7e7559b 91: onsuccess: #870: 1: Success after binutils: 5 commits new c871fb11a3d 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 00243be559f 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 7d6e08a8bf5 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new ad6dcbdd3f7 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new 97cf22c149f 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new ae4b5a9bd78 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 936ab178866 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new fdb420485c0 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new d0ff7320aae 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 77348ac11be 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new ab4e7bdf668 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 7921dbd7991 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 0c821a1e013 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new ac1d90cb2c1 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new c5fc8d2731a 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 11951eba6da 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new acb58061d10 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 8aa9d136166 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 13b97cab43d 110: onsuccess: #891: 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 (772caeb290c) \ 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 1744 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39152 -> 39716 bytes 04-build_abe-gcc/console.log.xz | Bin 213636 -> 213244 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8512 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 244732 -> 244156 bytes 08-build_abe-gdb/console.log.xz | Bin 38788 -> 39068 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2024 -> 2036 bytes 11-check_regression/console.log.xz | Bin 16092 -> 11596 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 20 +- 11-check_regression/mail-body.txt | 142 +- 11-check_regression/results.compare | 55 +- 11-check_regression/results.compare2 | 6266 +++++++++++---------------- 11-check_regression/results.regressions | 55 +- 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 | 144 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 55 +- sumfiles/gdb.log.xz | Bin 1934320 -> 1906352 bytes sumfiles/gdb.sum | 6993 +++++++++++-------------------- 30 files changed, 5144 insertions(+), 8668 deletions(-)