KDE CI: Frameworks » kdelibs4support » kf5-qt5 FreeBSDQt5.13 - Build # 28 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdelibs4support/job/kf5-qt5%20FreeBSDQt5.13/28/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Fri, 20 Sep 2019 03:19:29 +
 Build duration:
3 min 29 sec and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 39 test(s)Failed: projectroot.autotests.kmimetypetestFailed: projectroot.autotests.kstandarddirstest

D12992: New elisa icon

[Matthieu Gallien]

mgallien added a comment.


  In D12992#533180 , @lshoravi wrote:
  
  > Bumping @abetts
  
  
  Thanks for keeping this on your todo list. This is very much appreciated.
  
  I am trying to move forward the process of having Elisa published on Windows 
Store. It would be nice to be able to have a more distinctive icon before doing 
that.
  
  I have noticed that the current icon is very close to the icon of the Gnome 
podcast application.
  
  Can I help this make progress ?

REPOSITORY
  R266 Breeze Icons

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

To: lshoravi, #vdg, ngraham, #elisa
Cc: ndavis, KonqiDragon, abetts, paullesur, januz, mgallien, alex-l, andreask, 
kde-frameworks-devel, mfraser, mnesbitt, LeGast00n, carneirogustavo, jguidon, 
ctakano, Tizon, oussemabouaneni, ashwind, fbampaloukas, GB_2, sourabhboss, 
aureliencouderc, tgraves, hantzv, lcmscheid, nhuisman, ursjoss, mykolak, 
jussiv, michaelh, astippich, James, ngraham, bruns, kmf, lemuel

D24060: Make KColorScheme compatible with QVariant

[Volker Krause]

vkrause added a dependent revision: D24094: Add support for KColorScheme.

REPOSITORY
  R265 KConfigWidgets

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

To: vkrause, dfaure
Cc: dfaure, kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

D24060: Make KColorScheme compatible with QVariant

[Volker Krause]

This revision was automatically updated to reflect the committed changes.
Closed by commit R265:d65940d8e882: Make KColorScheme compatible with QVariant 
(authored by vkrause).

REPOSITORY
  R265 KConfigWidgets

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D24060?vs=66401=66490

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

AFFECTED FILES
  src/kcolorscheme.h

To: vkrause, dfaure
Cc: dfaure, kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

D24091: Move "Full Screen Mode" item from Settings menu to View menu

[Nathaniel Graham]

ngraham added a comment.


  @cfeck can clarify, but I believe it specifies the location of locally-added 
actions that come from the app itself. It would be empty if the app has a View 
menu but doesn't add any of its own actions (which seems unlikely, but is 
theoretically possible).
  
  Alternatively we could remove the separator below redisplay, which would 
allow us to always have a separator above Full Screen Mode with no danger of 
ever having double separators.

REPOSITORY
  R263 KXmlGui

BRANCH
  move_fullscreen_to_view_menu (branched from master)

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

To: ngraham, #vdg, #frameworks, cfeck, ndavis
Cc: kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

D24091: Move "Full Screen Mode" item from Settings menu to View menu

[Noah Davis]

ndavis added a comment.


  In D24091#534786 , @ngraham wrote:
  
  > Do you think I should always have a separator above the Full Screen menu 
item? This should generally work fine, but it means that in case the 
`MergeLocal` content is empty, there will be two separators in a row. I don't 
know how likely this is to ever happen, but it could. Thoughts?
  
  
  I'm not sure what `MergeLocal` does or when it would be empty.

REPOSITORY
  R263 KXmlGui

BRANCH
  move_fullscreen_to_view_menu (branched from master)

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

To: ngraham, #vdg, #frameworks, cfeck, ndavis
Cc: kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

D24091: Move "Full Screen Mode" item from Settings menu to View menu

[Nathaniel Graham]

ngraham added a comment.


  Do you think I should always have a separator above the Full Screen menu 
item? This should generally work fine, but it means that in case the 
`MergeLocal` content is empty, there will be two separators in a row. I don't 
know how likely this is to ever happen, but it could. Thoughts?

REPOSITORY
  R263 KXmlGui

BRANCH
  move_fullscreen_to_view_menu (branched from master)

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

To: ngraham, #vdg, #frameworks, cfeck, ndavis
Cc: kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

D24091: Move "Full Screen Mode" item from Settings menu to View menu

[Nathaniel Graham]

ngraham edited the summary of this revision.

REPOSITORY
  R263 KXmlGui

BRANCH
  move_fullscreen_to_view_menu (branched from master)

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

To: ngraham, #vdg, #frameworks, cfeck, ndavis
Cc: kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

D24091: Move "Full Screen Mode" item from Settings menu to View menu

[Noah Davis]

ndavis accepted this revision.
This revision is now accepted and ready to land.

REPOSITORY
  R263 KXmlGui

BRANCH
  move_fullscreen_to_view_menu (branched from master)

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

To: ngraham, #vdg, #frameworks, cfeck, ndavis
Cc: kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

D24091: Move "Full Screen Mode" item from Settings menu to View menu

[Nathaniel Graham]

ngraham created this revision.
ngraham added reviewers: VDG, Frameworks, cfeck.
Herald added a project: Frameworks.
Herald added a subscriber: kde-frameworks-devel.
ngraham requested review of this revision.

REVISION SUMMARY
  This is a pretty longstanding feature request and all the HIG and VDG people 
polled
  were in favor. Since those were the people requested to sign off on it, it 
looks like
  we can make the necessary code change now.

TEST PLAN
  F7387185: In the view menu.png 

REPOSITORY
  R263 KXmlGui

BRANCH
  move_fullscreen_to_view_menu (branched from master)

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

AFFECTED FILES
  src/ui_standards.rc

To: ngraham, #vdg, #frameworks, cfeck
Cc: kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

Re: Heads-up: KContacts and KCalendarCore about to move to Frameworks

[Volker Krause]

On Sunday, 15 September 2019 12:19:14 CEST Volker Krause wrote:
> Hi,
> 
> as previously discussed here and finally approved during Akademy we will
> move KContacts and KCalendarCore from Applications to Frameworks. This
> should hopefully cause minimal disruptions as the versions then released
> with KF 5.63 are drop-in replacements for the previously releases with
> Applications (same ABI, higher version number).
> 
> KCalendarCore will however rename its Git repo in the process to be
> consistent (kcalcore -> kcalendarcore). For kdesrc-build users not actively
> working on KCalendarCore this should be transparent, otherwise you might
> need to adjust the Git remote accordingly.
> 
> I'll inform you once this process has been completed.

This has now been executed. Framework releases will start with 5.63.0, 
Application releases will end after 19.08.x.

Regards,
Volker

signature.asc
Description: This is a digitally signed message part.

D24076: add a simple smoke test for slaves by using kioclient5

[Alexander Saoutkin]

feverfew added a comment.


  I won't review, but would like to note I think that with KIOFuse, in 
conjuction with fio  we can do some really 
complex testing on KIO, correct me if I'm wrong.
  
  If I'm right, then we can test KIO nicely, although if we do notice a bug via 
using fio, it can technically be in any of FUSE/KIOFuse/KIO, but in my 
experience KIO is the most buggy of the lot.

REPOSITORY
  R320 KIO Extras

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

To: sitter, dfaure
Cc: feverfew, kde-frameworks-devel, kfm-devel, iasensio, fprice, LeGast00n, 
MrPepe, fbampaloukas, alexde, GB_2, Codezela, meven, michaelh, spoorun, 
navarromorales, firef, ngraham, andrebarros, bruns, emmanuelp, mikesomov

KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.13 - Build # 95 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.13/95/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Thu, 19 Sep 2019 14:16:16 +
 Build duration:
7 min 48 sec and counting
   JUnit Tests
  Name: projectroot Failed: 3 test(s), Passed: 49 test(s), Skipped: 0 test(s), Total: 52 test(s)Failed: projectroot.autotests.kiocore_kmountpointtestFailed: projectroot.autotests.kiowidgets_kdirlistertestFailed: projectroot.autotests.kiowidgets_kdirmodeltestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)

D18915: Fix batchrename changing extension to lower case

[David Faure]

dfaure added a comment.


  Let's see which branch this ends up in, don't use 5, 14, 0 just yet, it might 
end up in 5.13.2.

REPOSITORY
  R241 KIO

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

To: cfoster, #dolphin, #frameworks, abalaji, dfaure
Cc: cfeck, bruns, ngraham, elvisangelaccio, chinmoyr, kde-frameworks-devel, 
LeGast00n, GB_2, michaelh

D18915: Fix batchrename changing extension to lower case

[David Faure]

dfaure requested changes to this revision.
dfaure added a comment.
This revision now requires changes to proceed.


  Good catch, but then this is a bug in QMimeDatabase::suffixForFileName.
  
  I just submitted a fix at 
https://codereview.qt-project.org/c/qt/qtbase/+/274548 -- aiming at the 5.14 
branch.
  
  So this commit is still valid of course, but it would be good to use #if 
QT_VERSION < QT_VERSION_CHECK(5, 14, 0) around the workaround, so that it goes 
away once we use a Qt version with the fix.
  AFAICS the workaround is only the use of "extensionLen", though (that's what 
should be ifdef'ed). This commit doesn't only fix casing, it also fixes the 
case of unknown extensions. That's valid and can be kept, no matter which Qt 
version we're using.
  
  I don't understand the comment about right-to-left languages in the commit 
log; this isn't using any locale-dependent APIs, is it?

REPOSITORY
  R241 KIO

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

To: cfoster, #dolphin, #frameworks, abalaji, dfaure
Cc: cfeck, bruns, ngraham, elvisangelaccio, chinmoyr, kde-frameworks-devel, 
LeGast00n, GB_2, michaelh

D24076: add a simple smoke test for slaves by using kioclient5

[Harald Sitter]

sitter created this revision.
sitter added a reviewer: dfaure.
Herald added projects: Dolphin, Frameworks.
Herald added subscribers: kfm-devel, kde-frameworks-devel.
sitter requested review of this revision.

REVISION SUMMARY
  this is meant to give a fairly generic way to easily test core
  functionality of any io slave

TEST PLAN
  ran against sftp and smb and it's all lovely

REPOSITORY
  R320 KIO Extras

BRANCH
  smoketests

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

AFFECTED FILES
  smoketest/README.md
  smoketest/file1
  smoketest/kio_smoke_test/.keep
  smoketest/smoke.sh

To: sitter, dfaure
Cc: kde-frameworks-devel, kfm-devel, iasensio, fprice, LeGast00n, MrPepe, 
fbampaloukas, alexde, GB_2, Codezela, feverfew, meven, michaelh, spoorun, 
navarromorales, firef, ngraham, andrebarros, bruns, emmanuelp, mikesomov

D24012: Supress mouse events in KCMs causing window moves

[Roman Gilg]

romangg added a comment.


  Forgot that KCMUtils is part of Frameworks... And probably doesn't make sense 
to create a bug fix Frameworks release just for that. The KScreen KCM is still 
usable, just moving outputs is difficult but also possible. So just push for 
next Frameworks release.

REPOSITORY
  R295 KCMUtils

BRANCH
  master

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

To: davidedmundson, #plasma, romangg
Cc: romangg, ngraham, anthonyfieroni, kde-frameworks-devel, LeGast00n, GB_2, 
michaelh, bruns

D24072: properly install whole plasmacomponent3

[Aleix Pol Gonzalez]

apol accepted this revision.
This revision is now accepted and ready to land.

REPOSITORY
  R242 Plasma Framework (Library)

BRANCH
  phab/components3

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

To: mart, #plasma, apol
Cc: kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

D24012: Supress mouse events in KCMs causing window moves

[Roman Gilg]

romangg accepted this revision.
romangg added a comment.
This revision is now accepted and ready to land.


  Let's get it in the beta. But can you reply to @anthonyfieroni inline reply 
before pushing?

REPOSITORY
  R295 KCMUtils

BRANCH
  master

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

To: davidedmundson, #plasma, romangg
Cc: romangg, ngraham, anthonyfieroni, kde-frameworks-devel, LeGast00n, GB_2, 
michaelh, bruns

D23205: [KProcessList] Optimize KProcessList::processInfo

[David Hallas]

hallas added a comment.


  @davidedmundson - ping :)

REPOSITORY
  R244 KCoreAddons

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

To: hallas, davidedmundson, broulik
Cc: apol, kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

Re: KDE CI: Frameworks » purpose » kf5-qt5 SUSEQt5.12 - Build # 114 - Failure!

[Ben Cooksley]

On Thu, Sep 19, 2019 at 11:48 AM Aleix Pol  wrote:
>
> On Wed, Sep 18, 2019 at 12:25 AM David Faure  wrote:
> >
> > On mardi 17 septembre 2019 23:53:00 CEST Aleix Pol wrote:
> > > We'll need a libaccounts release I guess, master wouldn't have this 
> > > problem.
> > > I created an issue upstream:
> > > https://gitlab.com/accounts-sso/libaccounts-qt/issues/4
> >
> > Thanks. This is why it passed locally.
> > I'll revert the define for now.
>
> We have a release from libaccounts-qt, I'm not sure how we'd get it
> into the CI though.

The easiest way to get the CI updated on Linux is to ask the OpenSUSE
packagers to include it.
Once it's in their repositories the CI system will pick it up the next
time the Docker images are rebuilt.

For FreeBSD, please ask Adriaan or Tobias and they'll be able to sort
you out for that side of things.

With regards to Windows (if applicable) you'll need to update the
Craft Blueprint for libaccounts-qt.
The Blueprints can be found in the craft-blueprints-kde repository on
git.kde.org.

>
> Aleix

Cheers,
Ben

KDE CI: Frameworks » kcalendarcore » kf5-qt5 SUSEQt5.13 - Build # 3 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20SUSEQt5.13/3/
 Project:
kf5-qt5 SUSEQt5.13
 Date of build:
Thu, 19 Sep 2019 10:23:55 +
 Build duration:
13 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5CalendarCore-5.63.0.xmlcompat_reports/KF5CalendarCore_compat_report.htmllogs/KF5CalendarCore/5.63.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 491 test(s), Skipped: 0 test(s), Total: 492 test(s)Failed: projectroot.autotests.testicaltimezones
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(2/2)96%
(82/85)96%
(82/85)69%
(9042/13174)48%
(4093/8574)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(38/38)100%
(38/38)96%
(2658/2780)52%
(743/1438)src94%
(44/47)94%
(44/47)61%
(6384/10394)47%
(3350/7136)

KDE CI: Frameworks » kcalendarcore » kf5-qt5 SUSEQt5.12 - Build # 3 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20SUSEQt5.12/3/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Thu, 19 Sep 2019 10:23:55 +
 Build duration:
3 min 48 sec and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5CalendarCore-5.63.0.xmlcompat_reports/KF5CalendarCore_compat_report.htmllogs/KF5CalendarCore/5.63.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 491 test(s), Skipped: 0 test(s), Total: 492 test(s)Failed: projectroot.autotests.testicaltimezones
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(2/2)96%
(82/85)96%
(82/85)69%
(9042/13174)48%
(4093/8574)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(38/38)100%
(38/38)96%
(2658/2780)52%
(743/1438)src94%
(44/47)94%
(44/47)61%
(6384/10394)47%
(3350/7136)

KDE CI: Frameworks » kcalendarcore » kf5-qt5 FreeBSDQt5.13 - Build # 3 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20FreeBSDQt5.13/3/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Thu, 19 Sep 2019 10:23:55 +
 Build duration:
1 min 26 sec and counting
   JUnit Tests
  Name: projectroot Failed: 456 test(s), Passed: 36 test(s), Skipped: 0 test(s), Total: 492 test(s)Failed: projectroot.autotests.Compat_libical3_AppleICal_1.5.icsFailed: projectroot.autotests.Compat_libical3_Evolution_2.8.2_timezone_test.icsFailed: projectroot.autotests.Compat_libical3_KOrganizer_3.1.icsFailed: projectroot.autotests.Compat_libical3_KOrganizer_3.1a.icsFailed: projectroot.autotests.Compat_libical3_KOrganizer_3.2.icsFailed: projectroot.autotests.Compat_libical3_MSExchange.icsFailed: projectroot.autotests.Compat_libical3_Mozilla_1.0.icsFailed: projectroot.autotests.Compat_libical3_Todos.icsFailed: projectroot.autotests.Compat_libical3_eGroupware.icsFailed: projectroot.autotests.RecurNext_ConnectDaily1.icsFailed: projectroot.autotests.RecurNext_ConnectDaily10.icsFailed: projectroot.autotests.RecurNext_ConnectDaily11.icsFailed: projectroot.autotests.RecurNext_ConnectDaily1a.icsFailed: projectroot.autotests.RecurNext_ConnectDaily2.icsFailed: projectroot.autotests.RecurNext_ConnectDaily3.icsFailed: projectroot.autotests.RecurNext_ConnectDaily4.icsFailed: projectroot.autotests.RecurNext_ConnectDaily5.icsFailed: projectroot.autotests.RecurNext_ConnectDaily6.icsFailed: projectroot.autotests.RecurNext_ConnectDaily7.icsFailed: projectroot.autotests.RecurNext_ConnectDaily8.icsFailed: projectroot.autotests.RecurNext_ConnectDaily9.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase01.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase02.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase03.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase04.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase05.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase06.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase07.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase08.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase09.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase10.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test01.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test02.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test03.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test04.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test05.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test06.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test07.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test08.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test09.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test10.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test11.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test12.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test13.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase01.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase02.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase03.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase04.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase05.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase06.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase07.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase08.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase09.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase10.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase11.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase12.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase15.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase16.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase17.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase18.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase19.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase20.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase21.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase23.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase24.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase25.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase26.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase27.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase28.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase29.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase30.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase31.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase32.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase33.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase34.icsFailed: 

D24072: properly install whole plasmacomponent3

[Marco Martin]

mart created this revision.
mart added a reviewer: Plasma.
Herald added a project: Frameworks.
Herald added a subscriber: kde-frameworks-devel.
mart requested review of this revision.

REVISION SUMMARY
  right now just a subsection of controls are installed under plasmacomponent3
  which makes for random missing stuff, especially any new component added.
  it was done to avoid to have things like "applicationwindow" which don't make 
sense
  in plasma, tough those are already available anyways as plain qqc2
  install the whole folder avoiding many potential headaches

TEST PLAN
  ieverything still works, all the components are available

REPOSITORY
  R242 Plasma Framework (Library)

BRANCH
  phab/components3

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

AFFECTED FILES
  src/declarativeimports/CMakeLists.txt

To: mart, #plasma
Cc: kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

KDE CI: Frameworks » kcalendarcore » kf5-qt5 SUSEQt5.13 - Build # 2 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20SUSEQt5.13/2/
 Project:
kf5-qt5 SUSEQt5.13
 Date of build:
Thu, 19 Sep 2019 09:59:40 +
 Build duration:
16 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5CalendarCore-5.63.0.xmlcompat_reports/KF5CalendarCore_compat_report.htmllogs/KF5CalendarCore/5.63.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 491 test(s), Skipped: 0 test(s), Total: 492 test(s)Failed: projectroot.autotests.testicaltimezones
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(2/2)96%
(82/85)96%
(82/85)69%
(9042/13174)48%
(4093/8574)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(38/38)100%
(38/38)96%
(2658/2780)52%
(743/1438)src94%
(44/47)94%
(44/47)61%
(6384/10394)47%
(3350/7136)

KDE CI: Frameworks » kcalendarcore » kf5-qt5 FreeBSDQt5.13 - Build # 2 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20FreeBSDQt5.13/2/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Thu, 19 Sep 2019 09:59:40 +
 Build duration:
12 min and counting
   JUnit Tests
  Name: projectroot Failed: 456 test(s), Passed: 36 test(s), Skipped: 0 test(s), Total: 492 test(s)Failed: projectroot.autotests.Compat_libical3_AppleICal_1.5.icsFailed: projectroot.autotests.Compat_libical3_Evolution_2.8.2_timezone_test.icsFailed: projectroot.autotests.Compat_libical3_KOrganizer_3.1.icsFailed: projectroot.autotests.Compat_libical3_KOrganizer_3.1a.icsFailed: projectroot.autotests.Compat_libical3_KOrganizer_3.2.icsFailed: projectroot.autotests.Compat_libical3_MSExchange.icsFailed: projectroot.autotests.Compat_libical3_Mozilla_1.0.icsFailed: projectroot.autotests.Compat_libical3_Todos.icsFailed: projectroot.autotests.Compat_libical3_eGroupware.icsFailed: projectroot.autotests.RecurNext_ConnectDaily1.icsFailed: projectroot.autotests.RecurNext_ConnectDaily10.icsFailed: projectroot.autotests.RecurNext_ConnectDaily11.icsFailed: projectroot.autotests.RecurNext_ConnectDaily1a.icsFailed: projectroot.autotests.RecurNext_ConnectDaily2.icsFailed: projectroot.autotests.RecurNext_ConnectDaily3.icsFailed: projectroot.autotests.RecurNext_ConnectDaily4.icsFailed: projectroot.autotests.RecurNext_ConnectDaily5.icsFailed: projectroot.autotests.RecurNext_ConnectDaily6.icsFailed: projectroot.autotests.RecurNext_ConnectDaily7.icsFailed: projectroot.autotests.RecurNext_ConnectDaily8.icsFailed: projectroot.autotests.RecurNext_ConnectDaily9.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase01.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase02.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase03.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase04.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase05.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase06.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase07.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase08.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase09.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase10.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test01.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test02.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test03.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test04.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test05.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test06.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test07.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test08.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test09.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test10.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test11.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test12.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test13.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase01.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase02.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase03.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase04.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase05.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase06.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase07.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase08.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase09.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase10.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase11.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase12.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase15.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase16.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase17.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase18.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase19.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase20.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase21.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase23.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase24.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase25.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase26.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase27.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase28.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase29.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase30.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase31.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase32.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase33.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase34.icsFailed: 

KDE CI: Frameworks » kcalendarcore » kf5-qt5 SUSEQt5.12 - Build # 2 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20SUSEQt5.12/2/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Thu, 19 Sep 2019 09:59:40 +
 Build duration:
12 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5CalendarCore-5.63.0.xmlcompat_reports/KF5CalendarCore_compat_report.htmllogs/KF5CalendarCore/5.63.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 491 test(s), Skipped: 0 test(s), Total: 492 test(s)Failed: projectroot.autotests.testicaltimezones
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(2/2)96%
(82/85)96%
(82/85)69%
(9042/13174)48%
(4093/8574)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(38/38)100%
(38/38)96%
(2658/2780)52%
(743/1438)src94%
(44/47)94%
(44/47)61%
(6384/10394)47%
(3350/7136)

Re: KDE CI: Frameworks » purpose » kf5-qt5 SUSEQt5.12 - Build # 114 - Failure!

[Aleix Pol]

On Wed, Sep 18, 2019 at 12:25 AM David Faure  wrote:
>
> On mardi 17 septembre 2019 23:53:00 CEST Aleix Pol wrote:
> > We'll need a libaccounts release I guess, master wouldn't have this problem.
> > I created an issue upstream:
> > https://gitlab.com/accounts-sso/libaccounts-qt/issues/4
>
> Thanks. This is why it passed locally.
> I'll revert the define for now.

We have a release from libaccounts-qt, I'm not sure how we'd get it
into the CI though.

Aleix

KDE CI: Frameworks » kcontacts » kf5-qt5 WindowsMSVCQt5.13 - Build # 1 - Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcontacts/job/kf5-qt5%20WindowsMSVCQt5.13/1/
 Project:
kf5-qt5 WindowsMSVCQt5.13
 Date of build:
Wed, 18 Sep 2019 17:07:05 +
 Build duration:
3 hr 41 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 31 test(s), Skipped: 0 test(s), Total: 32 test(s)Failed: projectroot.autotests.kcontacts_addresstest

KDE CI: Frameworks » kcalendarcore » kf5-qt5 WindowsMSVCQt5.13 - Build # 1 - Successful!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20WindowsMSVCQt5.13/1/
 Project:
kf5-qt5 WindowsMSVCQt5.13
 Date of build:
Wed, 18 Sep 2019 17:06:56 +
 Build duration:
4 hr 30 min and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 491 test(s), Skipped: 0 test(s), Total: 491 test(s)

KDE CI: Frameworks » kpeople » kf5-qt5 AndroidQt5.13 - Build # 1 - Successful!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kpeople/job/kf5-qt5%20AndroidQt5.13/1/
 Project:
kf5-qt5 AndroidQt5.13
 Date of build:
Wed, 18 Sep 2019 17:08:26 +
 Build duration:
40 min and counting

KDE CI: Frameworks » kcontacts » kf5-qt5 FreeBSDQt5.13 - Build # 1 - Successful!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kcontacts/job/kf5-qt5%20FreeBSDQt5.13/1/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Wed, 18 Sep 2019 17:07:08 +
 Build duration:
7 hr 4 min and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 32 test(s), Skipped: 0 test(s), Total: 32 test(s)