https://llvm.org/bugs/show_bug.cgi?id=26437
Bug ID: 26437
Summary: TestProcessIO.test_stdin_redirection is flaky on
android
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
https://llvm.org/bugs/show_bug.cgi?id=26439
Bug ID: 26439
Summary: android adb connection can sometimes fail
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Hi all,
I don't have this perfectly configured yet. It is happily running builds
and running test suites. However, while it reports test failures just
fine, it doesn't fail the build on a test failure. I'm tracking down why
now. I have just adjusted something so that we get an email on test
fa
I have the OS X testbot fail nag emails going out properly now.
Thanks!
-Todd
On Tue, Feb 2, 2016 at 7:58 AM, Todd Fiala wrote:
> Hi all,
>
> I don't have this perfectly configured yet. It is happily running builds
> and running test suites. However, while it reports test failures just
> fin
https://llvm.org/bugs/show_bug.cgi?id=26441
Bug ID: 26441
Summary: TestConsecutiveBreakpoints.test_single_step_thread_spe
cific fails on OSX
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
i found reson of hang. im used https://github.com/adoxa/ansicon for color
console.
after uninstall it is now work as expected.
2016-01-23 22:59 GMT+03:00 Red Skotina :
> im rebuild lldb as x64 application and reabuild my test application with
> x64 llvm.
> at first look same.
> But when my inter
As of this week, we have the test suite running clean under MSVC 2015 using
Python 3.5. I'm sure new things will pop up, but I'm considering the
transition "done" as of now.
What this means for MSVC 2013 is that we dont' want to support it anymore.
Reasons:
* C++ language support is poor
* Compi
Hi Zachary,
We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for
Android Studio and we also have a buildbot what is testing this
configuration (without sending e-mail at the moment) here:
http://lab.llvm.org:8011/builders/lldb-windows7-android
We are in the discussion to dec
On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer
wrote:
> Hi Zachary,
>
> We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for
> Android Studio and we also have a buildbot what is testing this
> configuration (without sending e-mail at the moment) here:
> http://lab.llvm.org
It looks like our bot, http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc ,
has tried to update to Python 3.5 and MSVC 2015, but it can’t find python or
VC. I’ll talk to our buildmiester about it.
Should we run this guy with 2013/py2.7 or 2015/py3.5?
--
Qualcomm Innovation Center, Inc.
If I remember correctly your bot isn't actually doing anything differently
than my bot [http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015].
If you want you could just remove your bot. If you want to keep it, then
yea getting it on VS2015 and Python 3 would be the best idea.
On Tue, Feb
Dear testers,
Release Candidate 2 has just been tagged [1]. Please build, test, and
upload to the sftp.
I know there are still outstanding issues from RC1, but there have
been a lot of merges going into the branch and I think it's time for
another round of RC testing.
This RC comes a little behi
Yours is Win Server 2008; ours is Win 7. I don’t know if that matters.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
From: Zachary Turner [mailto:ztur...@google.com]
Sent: Tuesday, Febr
It's Server 2008 R2 technically, which is the server version of Win 7 (same
API set, same OS features, etc). So yea, I'm pretty confident that test
coverage is going to be 100% the same across both. It's just a matter of
if you want to have something that you maintain / have control over, or if
y
Then maybe we should keep it 2013/py2.7, until llvm requires 2015.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
From: Zachary Turner [mailto:ztur...@google.com]
Sent: Tuesday, February
You may have to make some changes to the zorg scripts to keep that
working. I didn't realize there were any other bots building LLDB, so I
made some changes that will default everything to VS2015 and Py3.
BTW, is your builder doing a debug build or a release build? When doing a
debug build clang
BTW, I expect that your buildbot has been experiencing the problems with
the x86 / x64 toolchain for quite some time, because it's not really
relevant to how much memory your machine has, but just that it was using an
x86 toolchain at all. Has it been red for a long time?
On Tue, Feb 2, 2016 at 1
No, it turned red Friday night/Saturday morning.
Last good build:
http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc/builds/15167
First bad build:
http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc/builds/15168
It went red because of the change to VS2015/Python 3.5.
--
Qualco
18 matches
Mail list logo
