[lldb-dev] bug in TestMiGdbSetShow.test_lldbmi_gdb_set_target_async_off?

[Ilia K via lldb-dev]

Hi Ted!

As noted in the copied code, *running is async notification and it only
must be shown in async mode. The test checks that it's not being shown in
sync mode. So the test is correct.

On Thu, May 19, 2016 at 12:56 AM, Ted Woodward via lldb-dev <
lldb-dev at lists.llvm.org> wrote:

> Packages/Python/lldbsuite/test/tools/lldb-mi/TestMiGdbSetShow.py, in
> test_lldbmi_gdb_set_target_async_off we have this code:
>
>
>
>         self.runCmd("-gdb-set target-async off")
>
>
>
> …
>
>
>
>         self.runCmd("-exec-run")
>
>         unexpected = [ "\*running" ] # "\*running" is async notification
>
>         it = self.expect(unexpected + [ "@\"argc=1\\\\r\\\\n" ])
>
>         if it < len(unexpected):
>
>             self.fail("unexpected found: %s" % unexpected[it])
>
>
>
> But lldb-mi does the right thing, expect won’t match “running”, so the
> self.expect command fails, which causes the test to error out. Shouldn’t
> the self.expect be in a try, with an except being a pass?
>
>
>
> --
>
> Qualcomm Innovation Center, Inc.
>
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
>


-- 
- Ilia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20160710/c796fd08/attachment.html>