<div dir="ltr">Also, once it's working, I plan to set up a Windows build bot that's connected to the main llvm waterfall, and have it run automatically each time a new patch is submitted, similar to how the build bots work for the other platform. That's my ultimate goal, just making sure that if the build breaks (either compilation or with test regressions) we know about it :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 21, 2014 at 1:49 PM, Zachary Turner <span dir="ltr"><<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">It's getting there. I know of only 4 issues with the test suite currently that I'm working on fixing. There might be more, but when I run "ninja check-lldb" these are the only ones that happen. They are, in no particular order:<div><br></div><div><div>PutSTDIN doesn't work right (may have been fixed due to a recent patch by Greg Clayton, need to re-verify)</div><div>dotest.py -q --arch=i686 --executable D:/src/llvm/build/ninja/bin/lldb.exe -s D:/src/llvm/build/ninja/lldb-test-traces -u CXXFLAGS -u CFLAGS -C D:\src\llvm\build\ninja\bin\clang.exe -p TestProcessIO.py D:\src\llvm\tools\lldb\test\python_api\process\io</div><div><br></div><div>ProcessWindows doesn't know how to signal when process ends, hangs in Process::WaitForProcessToStop (Working on this one currently, should be the next one I fix)</div><div>dotest.py -q --arch=i686 --executable D:/src/llvm/build/ninja/bin/lldb.exe -s D:/src/llvm/build/ninja/lldb-test-traces -u CXXFLAGS -u CFLAGS -C D:\src\llvm\build\ninja\bin\clang.exe -p TestCallWithTimeout.py D:\src\llvm\tools\lldb\test\expression_command\timeout</div><div><br></div><div>Test suite generates python errors, not clear why.</div><div>dotest.py -q --arch=i686 --executable D:/src/llvm/build/ninja/bin/lldb.exe -s D:/src/llvm/build/ninja/lldb-test-traces -u CXXFLAGS -u CFLAGS -C D:\src\llvm\build\ninja\bin\clang.exe -p TestPlatformCommand.py D:\src\llvm\tools\lldb\test\functionalities\platform</div><div><br></div><div>RunShellCommand doesn't work, can't resolve cmd.exe correctly. (Already submitted r220217 that partially fixes this, there may or may not be more to do)</div><div>D:\src\llvm\tools\lldb\test/dotest.py -q --arch=i686 --executable D:/src/llvm/build/ninja/bin/lldb.exe -s D:/src/llvm/build/ninja/lldb-test-traces -u CXXFLAGS -u CFLAGS -C D:\src\llvm\build\ninja\bin\clang.exe -p TestPlatformCommand.py D:\src\llvm\tools\lldb\test\functionalities\platform</div></div><div><br></div><div><br></div><div>Alongside each test I've given the exact command line you can use to reproduce the error. Feel free to take a look if you want :) The way I found all these was to just run "ninja check-lldb" on Windows, then attach a debugger to crashed or deadlocked processes.</div><div><br></div><div>I recently hit a new error which has blocked everything, and has to do with the way clang finds cl to fallback to. I'm working on a few patches to clang to make its fallback logic smarter, and once I get all that worked out I'll get back to this.</div><div><br></div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 21, 2014 at 1:16 PM, Carlo Kok <span dir="ltr"><<a href="mailto:ck@remobjects.com" target="_blank">ck@remobjects.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Zachary Turner schreef op 21-10-2014 om 21:24:<span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for the response. I definitely think it would be great to have<br>
this functionality in. Originally when I started working on LLDB my<br>
goal was just to get the test suite up and running 100% (even if all the<br>
tests don't pass, at least the test infrastructure would run tests and<br>
correctly report pass/fail). So in hindsight now I'm glad I took this<br>
approach instead of working on getting some basic debugging<br>
functionality implemented, because then our work would have overlapped. :)<br>
</blockquote>
<br></span>
Does that work now? The testing? I have an SBFunction related patch that pretty much depends on testability :)<br>
<br>
--<br>
Carlo Kok<div><div><br>
______________________________<u></u>_________________<br>
lldb-dev mailing list<br>
<a href="mailto:lldb-dev@cs.uiuc.edu" target="_blank">lldb-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev" target="_blank">http://lists.cs.uiuc.edu/<u></u>mailman/listinfo/lldb-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>