T3689: Add abi compliance checker to CI

[Sandro Knauß]

knauss added a comment.


  In T3689#170284 <https://phabricator.kde.org/T3689#170284>, @bcooksley wrote:
  
  > In regards to `akonadi-mime` I have now re-run it, and it seems to work fine.
  >  As long as you're relying only on the master manifest.yaml, then it should be impossible for any publishing failure to cause issues.
  
  
  Well if if would be just `akonadi-mime`, I would not care. but it is actually a lot more failing with the same pattern.
  
  What I did for checking:
  *download this  consoleText: https://build.kde.org/job/Applications/job/kdav/job/kf5-qt5%20SUSEQt5.10/lastCompletedBuild/consoleText
  
  - than do some simple regex:
    - (Successfully created a dump (`^.*Dump path: abi_dumps/.*/ABI\.dump\s*$`)
    - search for  "Comparing ABIs"
  
  F6487824: ci-check.py <https://phabricator.kde.org/F6487824>
  
  And the outcome is overwhelming - a lot of is broken. I checked a lot locally via docker and could not reproduce this bug. That's why I think it is something with publishing the packages. Is it just one server, or is there any load balancing come into account so request are answered by a different sever, that isn't synced?
  
  for kde/pim/*:
  
  [ ] kblog
  [ ] mailcommon
  [ ] kmbox
  [ ] kontactinterface
  [ ] kpimtextedit
  [ ] akonadi-import-wizard
  [ ] kpkpass
  [ ] kldap
  [ ] kalarmcal
  [ ] libgravatar
  [ ] libkgapi
  [ ] libkleo
  [ ] grantleetheme
  [ ] kcontacts
  [ ] akonadi-notes
  [ ] kitinerary
  [ ] ktnef
  [ ] akonadi-mime
  [ ] kcalutils
  
  for frameworks:
  
  [ ] kcrash
  [ ] kwallet
  [ ] kpackage
  [ ] kholidays
  [ ] kparts
  [ ] syndication
  [ ] frameworkintegration
  [ ] khtml
  [ ] krunner
  [ ] knotifyconfig
  [ ] kidletime
  [ ] kitemviews
  [ ] kjobwidgets
  [ ] kmediaplayer
  [ ] kpeople
  [ ] prison
  [ ] kxmlrpcclient
  [ ] sonnet
  [ ] kcoreaddons
  [ ] kunitconversion
  [ ] kfilemetadata
  [ ] baloo
  [ ] kitemmodels
  [ ] kpty
  [ ] kconfig
  [ ] kxmlgui
  [ ] kconfigwidgets
  [ ] kdbusaddons
  [ ] kjsembed
  [ ] kplotting
  [ ] kactivities
  [ ] kdesu
  [ ] ki18n
  [ ] knotifications
  [ ] kactivities-stats
  [ ] attica
  [ ] ktexteditor
  [ ] solid
  [ ] kirigami
  [ ] syntax-highlighting
  [ ] kauth
  
  > In terms of the `akonadi-search` issue, using something like that YAML file should be fine yes and is historically how we've solved such issues.
  
  okay create D17672 <https://phabricator.kde.org/D17672> for this.

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/20181219/7f560f84/attachment.html>