[Lldb-commits] [lldb] r222163 - Complete rewrite of interactive editing support for single- and multi-line input.

[Ed Maste]

On 18 November 2014 14:03, Shawn Best <sbest at blueshiftinc.com> wrote:
> I can confirm the two issues you cite also started failing on linux around
> the time of this changes. Greg's checkin yesterday fixed TestCommandRegex,
> but TestGlobalVariables is still failing.

Thanks Shawn, it turns out I accidentally tested without Greg's fix. I
submitted PR 21599 for the TestGlobalVariables failure and added an
@expectedFailureFreeBSD decorator to the test.

FWIW I'm now down to one failure on FreeBSD in my local test run
without a PR. I believe the failure was introduced sometime after the
end of October.

FAIL: test_with_dwarf_and_process_launch_api
(TestValueVarUpdate.HelloWorldTestCase)
   Test SBValue::GetValueDidChange
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tank/emaste/src/llvm/tools/lldb/test/lldbtest.py", line 331, in wrapper
    return func(self, *args, **kwargs)
  File "/tank/emaste/src/llvm/tools/lldb/test/lldbtest.py", line 382, in wrapper
    return func(self, *args, **kwargs)
  File "/tank/emaste/src/llvm/tools/lldb/test/python_api/value_var_update/TestValueVarUpdate.py",
line 28, in test_with_dwarf_and_process_launch_api
    self.do_test()
  File "/tank/emaste/src/llvm/tools/lldb/test/python_api/value_var_update/TestValueVarUpdate.py",
line 61, in do_test
    self.assertTrue(i.GetValueDidChange(), "GetValueDidChange() is
saying a lie")
AssertionError: False is not True : GetValueDidChange() is saying a lie
Config=x86_64-/usr/bin/clang
----------------------------------------------------------------------
Ran 2 tests in 2.570s

FAILED (failures=1, skipped=1)