bcooksley added a comment.
In regards to Python, that is not enabled as the bindings generation is not reliable and can easily fail on a highly parallel system (which the CI is, depending on the node it could be a Hexa Core with HT, so run using make -j13) The generation also had a nasty tendency to fail for certain Frameworks more often than not due to various generation failures which would disappear on subsequent runs. In terms of various platforms, subscribing the appropriate Phabricator group when issues turn up is probably the best thing to do, we have #windows <https://phabricator.kde.org/tag/windows/>, #freebsd <https://phabricator.kde.org/tag/freebsd/> and #android <https://phabricator.kde.org/tag/android/> for this. We don't have anything for macOS at the moment although interest in that platform is very minimal. In terms of people who support those platforms, tests haven't been addressed as there are only a few people who work on keeping quite a large amount of software working, which makes getting around to looking at the tests a bit difficult. I've found that the app developers do care about current versions, the problem arises here as they generally only use released versions rather than master, so any issues they find will be much later down the road when they try to upgrade. The CI does try to keep an eye on this fortunately and pre-review CI should hopefully stop breakages from being fixed after the fact. REPOSITORY R244 KCoreAddons REVISION DETAIL https://phabricator.kde.org/D13583 To: bruns, #frameworks, astippich Cc: siddharthasahu, bcooksley, kossebau, kde-frameworks-devel, astippich, michaelh, ngraham, bruns
