- User Since
- Feb 7 2018, 7:04 PM (70 w, 6 d)
This test is extremely flaky on Windows - it looks like it passes on the bot less than 10% of the time: http://lab.llvm.org:8011/buildslaves/win-py3-buildbot.
Mon, Jun 17
It looks like this broke the Windows bot. I am no longer receiving emails when the bot fails (as bot owner I used to always get the failure emails), so I am assuming for some reason notifications aren't working correctly.
Tue, Jun 11
Tue, Jun 4
I don't think that this would apply very well to Visual Studio with the current change because it is likely that if you are using VS to build LLDB, you also used VS to build the dependencies. Even for xcode, I am sure that there are people who build the dependencies standalone with xcode and then are building LLDB standalone with xcode, so any change that absolutely treats the scenario as one or the other is going to break someone.
Wed, May 29
Tue, May 28
I am not very familiar with the lldb-mi tests specifically, but it looks like they require python to run (and are marked as unsupported otherwise):
This change broke one of the tests on the Windows LLDB bot:
This caused failures on the windows bot again:
Thu, May 23
This looks good - it is still not all though. Even after Jonas' change the build failed with the same error elsewhere.
It looks like this was not enough and the build is still broken. Please revert your change or fix it and then keep an eye on the Buildbot to make sure it turns to green again. Once it's broken, it won't continue sending failure emails, so you have to monitor it to make sure your change fixed it.
May 17 2019
May 10 2019
Either this change or your other APValue change broke the windows bot:
May 9 2019
Thanks, Pavel! I tested out the proposed change and all of our Ubuntu bots now work. I've committed it as well.
May 8 2019
A couple of the tests from TestVSCode_attach.py (test_by_pid and test_by_name) are failing for us on Ubuntu because they are failing to attach: AssertionError: False is not True : attach failed (Operation not permitted). It looks like attaching by pid or by name requires elevation - if I rerun the same tests with sudo, they pass reliably. How did you run the tests when they passed for you?
Apr 30 2019
Apr 25 2019
Yes, sorry. I hadn't gotten around to testing it to make sure the failures were gone. Do you still need someone to commit for you?
Apr 23 2019
Apr 22 2019
Apr 16 2019
I ran local tests with this and a couple of the tests from the lldb suite failed:
Apr 10 2019
Apr 9 2019
Apr 5 2019
Apr 3 2019
This broke the LLDB tests on the Windows Bot:
Mar 28 2019
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.