[Lldb-commits] TestFormattersBoolRefPtr.py on OSX

Tamas Berghammer via lldb-commits lldb-commits at lists.llvm.org
Thu Sep 10 03:05:14 PDT 2015


I don't know about any recent compiler update, about the build bot, but
will try to figure it out.

The current versions:
Darwin Yings-Mac-Pro.local 14.4.0 Darwin Kernel Version 14.4.0: Thu May 28
11:35:04 PDT 2015; root:xnu-2782.30.5~1/RELEASE_X86_64 x86_64
Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn)
Target: x86_64-apple-darwin14.4.0
Thread model: posix

The strange thing is that it fails only in about 95% of the times. If it
would be a compiler issue, I would expect it to fail every time.

On Wed, Sep 9, 2015 at 7:21 PM Enrico Granata <egranata at apple.com> wrote:

> On Sep 9, 2015, at 11:19 AM, Tamas Berghammer <tberghammer at google.com>
> wrote:
>
> I attached the log for the failure (come from the build bot).
>
> About the double reporting, I seen it on one of the build bot, but we have
> some case when 2 different test have the same name what can explain the
> issue (e.g. TestFormattersBoolRefPtr)
>
> Tamas
>
> On Wed, Sep 9, 2015 at 6:54 PM Zachary Turner <zturner at google.com> wrote:
>
>> +Todd just in case this is related to his changes.  We were seeing 1 or 2
>> test failures double reporting on Windows after the patch, so I'm not sure
>> if it could be related.
>>
>> On Wed, Sep 9, 2015 at 10:37 AM Enrico Granata via lldb-commits <
>> lldb-commits at lists.llvm.org> wrote:
>>
>>>
>>> On Sep 9, 2015, at 5:10 AM, Tamas Berghammer <tberghammer at google.com>
>>> wrote:
>>>
>>> Hi Enrico,
>>>
>>> TestFormattersBoolRefPtr.py started to fail on the OSX buildbot. I think
>>> the first build where it is failed is
>>> http://lab.llvm.org:8011/builders/lldb-x86_64-darwin-13.4/builds/5522,
>>> but I am not sure as the bot is a bit unreliable. Can you take a look for
>>> it, or if not, then are you fine with XFAIL-ing it until it get fixed?
>>>
>>> Thanks,
>>> Tamas
>>>
>>>
>>> This test seems to pass fine on a ToT checkout for me, and the bot seems
>>> to just say the test failed with no log of the issue. Do you mind providing
>>> a log if you have one available?
>>>
>>> Thanks,
>>> *- Enrico*
>>> 📩 egranata@.com ☎️ 27683
>>>
>>> _______________________________________________
>>> lldb-commits mailing list
>>> lldb-commits at lists.llvm.org
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
>>>
>> <log>
>
>
> We failed to set the breakpoint:
> Traceback (most recent call last):
>   File "/Users/lldb_build/lldbSlave/buildDir/lldb/test/lldbtest.py", line
> 551, in wrapper
>     return func(self, *args, **kwargs)
>   File
> "/Users/lldb_build/lldbSlave/buildDir/lldb/test/functionalities/data-formatter/boolreference/TestFormattersBoolRefPtr.py",
> line 28, in test_boolrefptr_with_dwarf_and_run_command
>     self.boolrefptr_data_formatter_commands()
>   File
> "/Users/lldb_build/lldbSlave/buildDir/lldb/test/functionalities/data-formatter/boolreference/TestFormattersBoolRefPtr.py",
> line 40, in boolrefptr_data_formatter_commands
>     lldbutil.run_break_set_by_file_and_line (self, "main.mm", self.line,
> num_expected_locations=1, loc_exact=True)
>   File "/Users/lldb_build/lldbSlave/buildDir/lldb/test/lldbutil.py", line
> 326, in run_break_set_by_file_and_line
>     check_breakpoint_result (test, break_results,
> num_locations=num_expected_locations, file_name = file_name, line_number =
> line_number, module_name=module_name)
>   File "/Users/lldb_build/lldbSlave/buildDir/lldb/test/lldbutil.py", line
> 460, in check_breakpoint_result
> *    test.assertTrue (num_locations == out_num_locations, "Expecting %d
> locations, got %d."%(num_locations, out_num_locations))*
> *AssertionError: False is not True : Expecting 1 locations, got 0.*
> Config=x86_64-clang
> Session info generated @ Wed Sep  9 10:52:45 2015
> To rerun this test, issue the following command from the 'test' directory:
>
> Was the compiler on the buildbot updated around when this started
> happening?
>
> Thanks,
> *- Enrico*
> 📩 egranata@.com ☎️ 27683
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150910/c2268c81/attachment.html>


More information about the lldb-commits mailing list