This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Ubuntu-Aarch64-native-gdbserver-m64, branch master
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Wed, 09 Jan 2019 04:14:28 -0500
- Subject: Failures on Ubuntu-Aarch64-native-gdbserver-m64, branch master
Buildslave:
ubuntu16-aarch64
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Ubuntu-Aarch64-native-gdbserver-m64/builds/4777>
Commit(s) tested:
3107326d3df950b0578a895bb835b2a8dfa8fab7
Author(s) (in the same order as the commits):
Andrew Paprocki <andrew@ishiboo.com>
Subject:
Adjust bfd/warning.m4 egrep patterns
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Ubuntu-Aarch64-native-gdbserver-m64/31/3107326d3df950b0578a895bb835b2a8dfa8fab7/>
*** Diff to previous build ***
============================
FAIL -> KFAIL: gdb.ada/bad-task-bp-keyword.exp: break *break_me'address TASK Task TaSK 2
PASS -> FAIL: gdb.ada/enum_idx_packed.exp: print full'first
PASS -> FAIL: gdb.base/break.exp: run until breakpoint set at a line number
PASS -> FAIL: gdb.base/ena-dis-br.exp: prepare to continue with ignore count
new FAIL: gdb.base/hbreak2.exp: continue to factorial
new FAIL: gdb.base/hbreak2.exp: info breakpoints
new FAIL: gdb.base/hbreak2.exp: run to factorial
new FAIL: gdb.base/hbreak2.exp: run until hardware function breakpoint, optimized file
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 11
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 9
PASS -> FAIL: gdb.base/sigstep.exp: displaced=on: continue on breakpoint, to handler entry: set itimer = itimer_real
PASS -> FAIL: gdb.base/sigstep.exp: displaced=on: nexti on breakpoint, skip handler, with sw-watchpoint, no handler: set itimer = itimer_real
PASS -> FAIL: gdb.base/vdso-warning.exp: run: no vdso without symbols is listed
PASS -> FAIL: gdb.cp/ref-params.exp: print value of a Child in main
PASS -> FAIL: gdb.cp/templates.exp: ptype T5<int>
PASS -> FAIL: gdb.mi/mi-pending.exp: MI pending breakpoint on pendfunc3
new FAIL: gdb.mi/mi-pending.exp: continuing execution to thread condition
PASS -> FAIL: gdb.mi/mi-until.exp: until line number
PASS -> FAIL: gdb.mi/mi-until.exp: until line number:file
new UNRESOLVED: gdb.python/py-type.exp: lang_cpp: setting breakpoint at 117
new UNRESOLVED: gdb.threads/continue-pending-after-query.exp: iter 4: info breakpoints
new UNRESOLVED: gdb.trace/report.exp: current target does not support trace
new UNRESOLVED: gdb.trace/tsv.exp: current target does not support trace
new UNRESOLVED: gdb.trace/while-dyn.exp: current target does not support trace
============================
*** Complete list of XFAILs for this builder ***
To obtain the list of XFAIL tests for this builder, go to:
<https://git.sergiodj.net/gdb-xfails.git/tree/xfails/Ubuntu-Aarch64-native-gdbserver-m64/xfails/master/xfail?id=22175446>
You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:
<https://git.sergiodj.net/gdb-xfails.git/tree/xfails/Ubuntu-Aarch64-native-gdbserver-m64/xfails/master/xfail.table?id=22175446>