T3689: Add abi compliance checker to CI

Sandro Knauß noreply at phabricator.kde.org
Thu Dec 20 16:27:07 GMT 2018


knauss added a comment.


  In T3689#170601 <https://phabricator.kde.org/T3689#170601>, @bcooksley wrote:
  
  > I checked execution of KDav on all four build nodes, and the process ran fine when done manually.
  >  Given there is no output from check-abi.py, this is quite hard to diagnose.
  
  
  In the last `for l in libraries:` loop, we get output for every item in that list, etiher because there are candidates or there are not.
  That means the only way to produce no output at all is that libraries list must be empty. We do not remove any entry from that list, so the initial search do not find any matching entry.
  And the only way the list can be empty is that the `for key, entry in ourArchive.serverManifest.items()` don't find any matching entry.
  
  > Can you propose some debug output which might point out why it's doing nothing?
  
  I added D17710 <https://phabricator.kde.org/D17710> to retry to reload the serverManiphest file again after 5secs to sleep. The added output is hopefully enough to spot the issue.

TASK DETAIL
  https://phabricator.kde.org/T3689

To: knauss
Cc: dfaure, kde-frameworks-devel, bcooksley, sysadmin, scarlettclark, aacid, knauss, alexeymin, kaning, blazquez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20181220/531b378c/attachment-0001.html>


More information about the Kde-frameworks-devel mailing list