Author: stella.stamenova Date: Thu Dec 20 10:23:08 2018 New Revision: 349784
URL: http://llvm.org/viewvc/llvm-project?rev=349784&view=rev Log: [lit] Skip stop-hook test on Windows This test is now marked as unsupported on Windows - it is not technically "unsupported" on Windows, but it fails because "expr ptr" does not evaluate correctly. However, the error message contains the expected string, so the test "passes" despite the fact that the commands failed The following bug has been opened for it: llvm.org/pr40119 Modified: lldb/trunk/lit/ExecControl/StopHook/stop-hook.test Modified: lldb/trunk/lit/ExecControl/StopHook/stop-hook.test URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/lit/ExecControl/StopHook/stop-hook.test?rev=349784&r1=349783&r2=349784&view=diff ============================================================================== --- lldb/trunk/lit/ExecControl/StopHook/stop-hook.test (original) +++ lldb/trunk/lit/ExecControl/StopHook/stop-hook.test Thu Dec 20 10:23:08 2018 @@ -6,7 +6,11 @@ # RUN: %lldb -b -s %p/Inputs/stop-hook-2.lldbinit -s %s -f %t | FileCheck %s # Test setting stop-hook with multi-line expression # RUN: %lldb -b -s %p/Inputs/stop-hook-3.lldbinit -s %s -f %t | FileCheck %s -# XFAIL: system-windows +# This test is not "unsupported" on Windows, but it fails because "expr ptr" +# does not evaluate correctly. However, the error message contains the expected +# string, so the test "passes" despite the fact that the commands failed +# llvm.org/pr40119 +# UNSUPPORTED: system-windows break set -f stop-hook.c -p "// Set breakpoint here to test target stop-hook" break set -f stop-hook.c -p "// Another breakpoint which is outside of the stop-hook range" _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
