- User Since
- Feb 7 2018, 7:04 PM (63 w, 6 h)
Tue, Apr 23
Mon, Apr 22
Tue, Apr 16
I ran local tests with this and a couple of the tests from the lldb suite failed:
Wed, Apr 10
Tue, Apr 9
Fri, Apr 5
Wed, Apr 3
This broke the LLDB tests on the Windows Bot:
Thu, Mar 28
This is causing failures on the windows bot. Please fix it or revert it.
Mar 13 2019
Mar 7 2019
This broke the Windows bot because now one of the TestPaths tests passes on Windows:
Mar 6 2019
This caused a failure on the Windows bot:
Mar 5 2019
This introduced a build break on Windows (which happened to coincide with another build break).
This is causing a failure on the Windows Bot:
Feb 28 2019
This broke the windows LLDB bot:
Feb 20 2019
This broke the windows bot:
Feb 15 2019
LGTM. Now might not be the best time to commit it though because the LLDB build is broken on Windows.
Feb 14 2019
Feb 13 2019
This looks to have broken the windows build:
Feb 7 2019
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.
Feb 5 2019
This is failing on the windows bot:
Jan 29 2019
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:
Jan 28 2019
@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.
Jan 26 2019
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:
Jan 25 2019
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.
Jan 24 2019
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
Jan 23 2019
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: