- User Since
- Feb 7 2018, 7:04 PM (53 w, 6 d)
This broke the windows bot:
Fri, Feb 15
LGTM. Now might not be the best time to commit it though because the LLDB build is broken on Windows.
Thu, Feb 14
Wed, Feb 13
This looks to have broken the windows build:
Thu, Feb 7
There's another patch (https://reviews.llvm.org/D54386/) which is fixing the fedora bot. You might want to leave that one.
This looks good. After it's checked in, it won't take effect until the master buildbot is updated though. You'd need @gkistanova to update it. She should also sign off on this.
Tue, Feb 5
This is failing on the windows bot:
Tue, Jan 29
This change broke one of the tests on Windows:
Build passes with VS now.
I am not sure if you saw this, but it looks like it broke one of the tests on the Windows bot:
Mon, Jan 28
@thakis Thanks for the information, I had actually missed that.
This change is causing build failures on Windows when using Visual Studio as the generator. It would also cause the same failure on for any other generator that supports multiple configurations.
Sat, Jan 26
I don't have a strong preference between using a separate module for interopability between python versions and implementing the functions as part of dotest if there are few of them, but I have to agree with @zturner that if we have more than a couple of functions, it makes sense to add them to an explicit module.
It looks like this change broke the windows bot:
Fri, Jan 25
I haven't had time to look into it in details but it looks like either this change or https://reviews.llvm.org/D57259 broke the windows LLDB bot.
I haven't had time to look into it in details but it looks like either this change or https://reviews.llvm.org/D57186 broke the windows bot.
Thu, Jan 24
One of the LLDB bots is still failing because of this change: http://lab.llvm.org:8011/builders/lldb-x64-windows-ninja/builds/978/steps/test/logs/stdio
Wed, Jan 23
Thanks. You have to change a couple of the locations to '%T' though - '%t' is a file and '%T' is a directory - and you're using '%t' as a directory in a couple of the places.
Jan 20 2019
It looks like this change broke a number of the LLDB tests:
Jan 16 2019
TestFunctionRefs is failing on the Windows bot: http://lab.llvm.org:8011/builders/lldb-x64-windows-ninja/builds/677
The Windows Buildbot is failing because of one of the tests (SymbolFile/DWARF/dir-separator-no-comp-dir-relative-name.s) added in this change. You can see the failure here: http://lab.llvm.org:8011/builders/lldb-x64-windows-ninja/builds/666. It looks like it is checking for the wrong path on Windows:
Jan 14 2019
Jan 11 2019
Jan 10 2019
Jan 9 2019
Dec 21 2018
Dec 20 2018
Dec 19 2018
I tracked this down - the failures are not due to this change (or any LLDB change). It's this change to the common CMake files in LLVM: https://reviews.llvm.org/D55056
This change caused a number of failures in the LLDB tests (as in 40+ failures) on Windows:
Dec 18 2018
It looks like this might not be specific to your change as a few other tests are failing with a similar error. I'm looking into it.
A bunch of the NativePDB tests are failing on Windows now.
Dec 17 2018
This change made the Windows test get stuck: http://lab.llvm.org:8014/builders/lldb-x64-windows-ninja/builds/2340
This does fix the issues. Thanks!
Dec 14 2018
I am trying to use the new builder to build the lldb-mi tests, so that they can start consistently passing on Windows, so they're now using the gcc builder on Linux and failing:
$ ":" "RUN: at line 5" $ "E:\build_slave\lldb-x64-windows-ninja\build\bin\lldb.EXE" "-S" "E:/build_slave/lldb-x64-windows-ninja/llvm/tools/lldb/lit\lit-lldb-init" "-f" "E:\build_slave\lldb-x64-windows-ninja\build\tools\lldb\lit\SymbolFile\NativePDB\Output\local-variables.cpp.tmp.exe" "-s" "E:\build_slave\lldb-x64-windows-ninja\llvm\tools\lldb\lit\SymbolFile\NativePDB/Inputs/local-variables.lldbinit" $ "E:\build_slave\lldb-x64-windows-ninja\build\bin\FileCheck.EXE" "E:\build_slave\lldb-x64-windows-ninja\llvm\tools\lldb\lit\SymbolFile\NativePDB\local-variables.cpp" # command stderr: E:\build_slave\lldb-x64-windows-ninja\llvm\tools\lldb\lit\SymbolFile\NativePDB\local-variables.cpp:154:16: error: CHECK-NEXT: expected string not found in input
local-variables.cpp is failing on the Buildbot:
Dec 11 2018
Let's use @labath's change instead.
A couple of small comments, but it looks good otherwise. Thanks!