diff options
| author | Simon Marchi <simon.marchi@ericsson.com> | 2015-07-27 15:02:10 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@ericsson.com> | 2015-07-27 15:02:37 -0400 |
| commit | da33c9a7bff093e772a381bf9ab42d876089cdcf (patch) | |
| tree | ba516543544a84063f48dc7fbeaf500db508c362 /gdb/testsuite/gdb.mi/mi-watch.exp | |
| parent | 0c87c0bfdfe19d5e2b8938d1db42c43e7b19e53f (diff) | |
| download | gdb-da33c9a7bff093e772a381bf9ab42d876089cdcf.zip gdb-da33c9a7bff093e772a381bf9ab42d876089cdcf.tar.gz gdb-da33c9a7bff093e772a381bf9ab42d876089cdcf.tar.bz2 | |
Remove xfail in gdb.mi/mi-watch.exp
I noticed there was an unexpected pass in mi-watch.exp when running on
x86_64. Doing a bit of archeology shows that the xfail was added by
4a543da. This particular test failed on the MIPS architecture, which
the original contributor was working with. Here is the thread:
https://www.sourceware.org/ml/gdb-patches/2007-09/msg00151.html
Looking at the latest buildbot results for MIPS, it seems that it's also
an unexpected pass on that architecture. Therefore, I see no reason to
leave the xfail in place.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-watch.exp (test_watchpoint_triggering): Remove xfail.
Diffstat (limited to 'gdb/testsuite/gdb.mi/mi-watch.exp')
| -rw-r--r-- | gdb/testsuite/gdb.mi/mi-watch.exp | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/gdb/testsuite/gdb.mi/mi-watch.exp b/gdb/testsuite/gdb.mi/mi-watch.exp index 2551d42..4f87a5a 100644 --- a/gdb/testsuite/gdb.mi/mi-watch.exp +++ b/gdb/testsuite/gdb.mi/mi-watch.exp @@ -131,14 +131,10 @@ proc test_watchpoint_triggering {type} { {"" "wpt=\{number=\"2\",exp=\"C\"\},value=\{old=\".*\",new=\"3\"\}"} \ "watchpoint trigger" - if { $type == "sw" } { - setup_xfail *-*-* - } mi_execute_to "exec-continue" "watchpoint-scope" "callee3" ".*" \ ".*basics.c" $line_callee3_close_brace \ {"" "wpnum=\"2\""} \ "watchpoint trigger" - clear_xfail *-*-* } proc test_watchpoint_all {type} { |