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 13b97cab43d 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 8aa9d136166 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards acb58061d10 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 11951eba6da 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards c5fc8d2731a 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards ac1d90cb2c1 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 0c821a1e013 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 7921dbd7991 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards ab4e7bdf668 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 77348ac11be 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards d0ff7320aae 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards fdb420485c0 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 936ab178866 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards ae4b5a9bd78 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 97cf22c149f 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards ad6dcbdd3f7 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 7d6e08a8bf5 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 00243be559f 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards c871fb11a3d 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards fa3b7e7559b 91: onsuccess: #870: 1: Success after binutils: 5 commits discards a21ef7424aa 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 95607166576 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 9f8c29c6675 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 54602e26633 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards d69ca859dd1 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 7b507ad01b8 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards a4965c10bae 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards e2f24c990b9 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 96476a5cec7 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 91c1a5f17f0 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 09ed55bec38 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 65fc7ba5d5c 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 2298e059c0f 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards 57df1f0b69a 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 39afb42292c 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 8f003fb5859 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 79ec8eb155b 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards efe46673095 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 6a7a279251f 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards c3ba0c87417 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards d00696a8a4a 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards d60ad100ed6 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 5e4961eb6ab 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 0738a8190cc 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 3594c4723f4 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards eabde38348e 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 75555a7ddaa 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 37dceff3f8c 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards bde825ccf43 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 2bf5f063af1 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards ee36ffc7fe9 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards 2e3ceeac7cb 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 42a2cb2dcbf 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards fcbfe4f59d1 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards acaf6b9065e 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 154fbd6a5fe 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards d82db0a83ad 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards fe4889f97a5 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards e1485d6f9bc 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards c0208c8a9e4 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 4d79fe5a178 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 7829e61729c 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards c330f5c223e 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 6e7563fd5cd 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 0d8dd102b94 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 6c6406045b6 45: onsuccess: #815: 1: Success after binutils: 6 commits discards d98c0ad427c 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 05809978426 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 1b7c890e05a 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 5a999ba8f0a 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards dd60dbaa5a9 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 5ef7c223a14 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 7a19c0cbf0d 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 0bed511fb0a 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards b73367f8240 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards e6a5496feba 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 8b2dc023f2c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards ec390f478c5 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards eabfe22392c 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards e6fd7bef033 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards 63cb993c607 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 32637032785 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 9e45c734acd 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards d93d710a098 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards eddb3de0600 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards f0df9440f66 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards e18930eaccf 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 0aecb34d5bd 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards 776904c17ad 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards df8d28c499d 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards f5ccd3caf41 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 078591b90dc 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 401e84af063 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 3d3e955140c 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c8f06f3a935 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 9ce9dccbf03 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 696a4bbbaa4 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 4117028f0aa 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards a4ce27473ca 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 3f21b7fd7ee 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c8cfff784eb 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f504579ee64 10: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 40a3f73e05e 11: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 94c9f2cc465 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 76067262178 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 18beb837f83 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 3f48ab81aa3 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new dfb45b6f753 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 987df348724 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 54bed41d8f1 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 9c83288dc2a 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c6e8d310bfa 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 8a396e6f3e5 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 83198a077d1 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 21a63208676 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new bfcb9224df1 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 6d5b5c20519 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new f900b66233d 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 6d49a90e859 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new c8598fb2013 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 6710f6fd7f9 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new 7b040443cb8 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 8d003c6694f 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 6163f0ce31d 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 402a3ef3495 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 4fa38dfd8d5 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new aaed779b735 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 5ae208a30fb 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 02b441edd5e 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 4017238c4f5 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new c88721f460b 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 148c490e33f 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 7d250bdb0ad 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 82fe825d828 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 2dec686c908 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new a399adb19bf 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 0c5b2e2a74d 45: onsuccess: #815: 1: Success after binutils: 6 commits new 96e90c3fa80 46: onsuccess: #818: 1: Success after binutils: 10 commits new f93575f4476 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 1a92e0871cd 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new c29ce4352a1 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 6be735333d6 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 816f8c34cf3 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new e2dd316e6ea 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new e11c3446956 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 5eb2629b157 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 0ee6e773ef5 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new c7158072ab7 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 56071252e46 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new b4d1f3ef7ff 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new dadfe8df020 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 2037f20bb68 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 6d456f8d19a 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 775cd2c3313 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new fc8e705ad11 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new c14d0e4536d 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new f825bb71a9d 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 9b8dbbf5b53 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 1d18af96543 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new eaf8efc8138 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 8a063c4ab90 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 006b02bb56b 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 8e7b2001ad4 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 54ed2129e05 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new e884b169c5a 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 28c970321ea 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new df434d74ee3 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new 45f2e3dbdf8 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new dd768c203b2 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new de89dc65a4a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new b9d1c8d3d10 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new c95536c1743 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new c7648a99f59 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 05b64c5a168 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 4716e0e4263 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 9ebd935ae49 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 75686053dbc 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new 5854dfe4a10 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 006d95529dd 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new c8513994b54 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new a22ea1cb4d3 89: onsuccess: #864: 1: Success after binutils: 25 commits new 9a46b278190 90: onsuccess: #867: 1: Success after binutils: 4 commits new 60147f05423 91: onsuccess: #870: 1: Success after binutils: 5 commits new 3f34977503e 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new dab5c3479db 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new fa0587a1d44 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 6a87b09d06e 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new 8db70f05f56 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 8abc57f027a 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 1faad4c6196 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new c8c7d32ff05 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new e753b4beeb1 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 79706618f70 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 816a6574336 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 9cb89efb50c 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 94341bd892b 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 842dc065163 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new b313c628184 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 52d0ef85a95 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new fcc2398e9f4 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 672b1ea6cba 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new fe54bda4268 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 1482c80fe1b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...]

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 (13b97cab43d) \ 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 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 39716 -> 39092 bytes 04-build_abe-gcc/console.log.xz | Bin 213244 -> 212476 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8292 bytes 07-build_abe-glibc/console.log.xz | Bin 244156 -> 244344 bytes 08-build_abe-gdb/console.log.xz | Bin 39068 -> 38856 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2036 -> 2132 bytes 11-check_regression/console.log.xz | Bin 11596 -> 12936 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 26 +- 11-check_regression/mail-body.txt | 104 +- 11-check_regression/results.compare | 49 +- 11-check_regression/results.compare2 | 2503 ++++++---- 11-check_regression/results.regressions | 49 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 106 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 49 +- sumfiles/gdb.log.xz | Bin 1906352 -> 1867132 bytes sumfiles/gdb.sum | 7540 ++++++++++++++++++++++--------- 29 files changed, 7157 insertions(+), 3353 deletions(-)