D6940: Fix GDB/LLDB unittests.

Aetf noreply at phabricator.kde.org
Mon Jul 31 18:20:53 UTC 2017


qi437103 added a comment.


  @kfunk 
  Hmm, it seems kdevelop tries to popup an error or something for lldb tests. Maybe due to unsupported lldb version?
  
  For gdb things is more interesting... For some reason the debuggee stopped right after starting, thus the timeout:
  
    QWARN  : KDevMI::GDB::GdbTest::testStdOut() current state 5 waiting for 6
    QWARN  : KDevMI::GDB::GdbTest::testBreakpoint() current state 5 waiting for 3
  
  (state 5 is `StoppedState`)
  
  gdb printer tests are also failed for the same reason:
  
    QDEBUG : QtPrintersTest::testQString() "run"  =  "Starting program: /home/jenkins/workspace/KDevelop kdevelop kf5-qt5 XenialQt5.7/build/debuggers/common/tests/debuggees/debuggee_qstring \nDuring startup program exited normally."
  
  I'll look into this. BTW, do you know how I can get a shell into the CI environment? Or otherwise anyway I can easily test code changes on CI like making it build another branch?

REPOSITORY
  R32 KDevelop

REVISION DETAIL
  https://phabricator.kde.org/D6940

To: qi437103, kfunk, #kdevelop
Cc: kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170731/ef43e976/attachment.html>


More information about the KDevelop-devel mailing list