KDE CI: Frameworks » kirigami » kf5-qt5 WindowsMSVCQt5.15 - Build # 496 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kirigami/job/kf5-qt5%20WindowsMSVCQt5.15/496/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 29 Sep 2021 22:18:05 + Build duration: 1 min 30 sec and counting JUnit Tests Name: projectrootC_.CI.Job_Build Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)
KDE CI: Frameworks » kirigami » kf5-qt5 FreeBSDQt5.15 - Build # 614 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kirigami/job/kf5-qt5%20FreeBSDQt5.15/614/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Wed, 29 Sep 2021 22:18:05 + Build duration: 45 sec and counting JUnit Tests Name: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515 Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)
Re: Rollout of Gitlab CI
Le mer. 29 sept. 2021 à 19:37, Ben Cooksley a écrit : > On Thu, Sep 30, 2021 at 3:41 AM Johnny Jazeix wrote: > >> >> >> Le mer. 29 sept. 2021 à 11:27, Ben Cooksley a écrit : >> >>> Hi all, >>> >>> As those of you who watch and work on Frameworks repositories will be >>> aware, we've just rolled out the first set of native Gitlab CI builds. >>> >>> These builds are at this time Linux only, but do include support for >>> both regular branch builds as well as for Merge Requests. It is anticipated >>> that Windows, FreeBSD and Android builds will follow in the near future - >>> there are a few extra things we need to get completed first before they can >>> be rolled out. As part of carrying out the build the scripts will also >>> gather Code Coverage and Code Quality information using gcovr and cppcheck >>> respectively, and this will be made available to you within the Gitlab >>> interface. >>> >>> With regards to availability to projects outside Frameworks, projects >>> that depend only on Frameworks (and no other KDE project) may enable CI for >>> their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files >>> to their repositories. I anticipate that once the necessary changes have >>> been made to the "seed" jobs used to provision the initial artifacts it >>> should be possible for all projects to rollout support (although i'd like >>> to add ccache support to the system to ensure larger project builds >>> complete promptly first). >>> >>> If anyone would like to help out with getting the seed jobs ready please >>> let me know as this is definitely something that the community can assist >>> with (and will also help with easing the rollout of Windows, FreeBSD and >>> Android builds). >>> >>> For those projects that do go ahead with enabling Gitlab CI support >>> please ensure you add the necessary .kde-ci.yml file beforehand, specifying >>> in it the necessary Dependencies, as well as the necessary Options your >>> project needs to customise for their build. A list of all the possible >>> values in a .kde-ci.yml file can be found at >>> https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 >>> >>> For those projects that are not yet able to enable the system, it is >>> strongly encouraged that you go ahead and get the .kde-ci.yml files ready >>> in your repository now - especially if other projects depend on your >>> project. This will allow the rollout of the CI system to those projects to >>> proceed much more smoothly (otherwise we will need to get them added to >>> those projects which have other projects depending on them). >>> >>> Please note that this new infrastructure replaces all existing Gitlab CI >>> jobs we provided in the initial testing phase, and those should be removed >>> (much like how I did for Frameworks) when switching to the new setup. >>> >>> Thanks, >>> Ben >>> >> >> Hi, >> >> is there a template for the .gitlab-ci.yml or should we use the same as >> https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e >> for example? >> > > You can use the same as that file. > > We're not providing a .gitlab-ci.yml template as there will be Windows, > FreeBSD and Android builds as well (and potentially in the future macOS as > well) which are options that won't necessarily apply to all projects. > > >> Cheers, >> >> Johnny >> > > Cheers, > Ben > Ok, super. It works fine for GCompris: https://invent.kde.org/education/gcompris/-/tree/master Thanks for providing this! Johnny
Re: Rollout of Gitlab CI
On Thu, Sep 30, 2021 at 3:41 AM Johnny Jazeix wrote: > > > Le mer. 29 sept. 2021 à 11:27, Ben Cooksley a écrit : > >> Hi all, >> >> As those of you who watch and work on Frameworks repositories will be >> aware, we've just rolled out the first set of native Gitlab CI builds. >> >> These builds are at this time Linux only, but do include support for both >> regular branch builds as well as for Merge Requests. It is anticipated that >> Windows, FreeBSD and Android builds will follow in the near future - there >> are a few extra things we need to get completed first before they can be >> rolled out. As part of carrying out the build the scripts will also gather >> Code Coverage and Code Quality information using gcovr and cppcheck >> respectively, and this will be made available to you within the Gitlab >> interface. >> >> With regards to availability to projects outside Frameworks, projects >> that depend only on Frameworks (and no other KDE project) may enable CI for >> their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files >> to their repositories. I anticipate that once the necessary changes have >> been made to the "seed" jobs used to provision the initial artifacts it >> should be possible for all projects to rollout support (although i'd like >> to add ccache support to the system to ensure larger project builds >> complete promptly first). >> >> If anyone would like to help out with getting the seed jobs ready please >> let me know as this is definitely something that the community can assist >> with (and will also help with easing the rollout of Windows, FreeBSD and >> Android builds). >> >> For those projects that do go ahead with enabling Gitlab CI support >> please ensure you add the necessary .kde-ci.yml file beforehand, specifying >> in it the necessary Dependencies, as well as the necessary Options your >> project needs to customise for their build. A list of all the possible >> values in a .kde-ci.yml file can be found at >> https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 >> >> For those projects that are not yet able to enable the system, it is >> strongly encouraged that you go ahead and get the .kde-ci.yml files ready >> in your repository now - especially if other projects depend on your >> project. This will allow the rollout of the CI system to those projects to >> proceed much more smoothly (otherwise we will need to get them added to >> those projects which have other projects depending on them). >> >> Please note that this new infrastructure replaces all existing Gitlab CI >> jobs we provided in the initial testing phase, and those should be removed >> (much like how I did for Frameworks) when switching to the new setup. >> >> Thanks, >> Ben >> > > Hi, > > is there a template for the .gitlab-ci.yml or should we use the same as > https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e > for example? > You can use the same as that file. We're not providing a .gitlab-ci.yml template as there will be Windows, FreeBSD and Android builds as well (and potentially in the future macOS as well) which are options that won't necessarily apply to all projects. > Cheers, > > Johnny > Cheers, Ben
Re: Rollout of Gitlab CI
Le mer. 29 sept. 2021 à 11:27, Ben Cooksley a écrit : > Hi all, > > As those of you who watch and work on Frameworks repositories will be > aware, we've just rolled out the first set of native Gitlab CI builds. > > These builds are at this time Linux only, but do include support for both > regular branch builds as well as for Merge Requests. It is anticipated that > Windows, FreeBSD and Android builds will follow in the near future - there > are a few extra things we need to get completed first before they can be > rolled out. As part of carrying out the build the scripts will also gather > Code Coverage and Code Quality information using gcovr and cppcheck > respectively, and this will be made available to you within the Gitlab > interface. > > With regards to availability to projects outside Frameworks, projects that > depend only on Frameworks (and no other KDE project) may enable CI for > their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files > to their repositories. I anticipate that once the necessary changes have > been made to the "seed" jobs used to provision the initial artifacts it > should be possible for all projects to rollout support (although i'd like > to add ccache support to the system to ensure larger project builds > complete promptly first). > > If anyone would like to help out with getting the seed jobs ready please > let me know as this is definitely something that the community can assist > with (and will also help with easing the rollout of Windows, FreeBSD and > Android builds). > > For those projects that do go ahead with enabling Gitlab CI support please > ensure you add the necessary .kde-ci.yml file beforehand, specifying in it > the necessary Dependencies, as well as the necessary Options your project > needs to customise for their build. A list of all the possible values in a > .kde-ci.yml file can be found at > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 > > For those projects that are not yet able to enable the system, it is > strongly encouraged that you go ahead and get the .kde-ci.yml files ready > in your repository now - especially if other projects depend on your > project. This will allow the rollout of the CI system to those projects to > proceed much more smoothly (otherwise we will need to get them added to > those projects which have other projects depending on them). > > Please note that this new infrastructure replaces all existing Gitlab CI > jobs we provided in the initial testing phase, and those should be removed > (much like how I did for Frameworks) when switching to the new setup. > > Thanks, > Ben > Hi, is there a template for the .gitlab-ci.yml or should we use the same as https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/63bec5521d245e3a1ea50109b86a2b716966938e for example? Cheers, Johnny
KDE CI: Frameworks » kirigami » kf5-qt5 WindowsMSVCQt5.15 - Build # 495 - Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kirigami/job/kf5-qt5%20WindowsMSVCQt5.15/495/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 29 Sep 2021 08:50:00 + Build duration: 56 min and counting JUnit Tests Name: projectrootC_.CI.Job_Build Failed: 1 test(s), Passed: 11 test(s), Skipped: 0 test(s), Total: 12 test(s)Failed: projectrootC_.CI.Job_Build.autotests.pagepool/tst_layers.qml
KDE CI: Frameworks » kwayland » kf5-qt5 SUSEQt5.15 - Build # 132 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20SUSEQt5.15/132/ Project: kf5-qt5 SUSEQt5.15 Date of build: Wed, 29 Sep 2021 08:53:06 + Build duration: 34 min and counting BUILD ARTIFACTS acc/KF5Wayland-5.87.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.autotests Failed: 1 test(s), Passed: 46 test(s), Skipped: 0 test(s), Total: 47 test(s)Failed: projectroot.autotests.client.kwayland_testWaylandRegistry Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report63% (5/8)90% (218/241)90% (218/241)84% (28386/33634)53% (12802/24333)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests.client100% (43/43)100% (43/43)99% (13096/13167)50% (8207/16317)autotests.server100% (6/6)100% (6/6)99% (539/542)50% (283/568)src.client97% (72/74)97% (72/74)83% (6382/7673)64% (1836/2880)src.compat100% (2/2)100% (2/2)100% (78/78)100% (0/0)src.server96% (95/99)96% (95/99)83% (8291/9964)63% (2476/3933)src.tools0% (0/2)0% (0/2)0% (0/786)0% (0/302)src.tools.testserver0% (0/2)0% (0/2)0% (0/119)0% (0/14)tests0% (0/13)0% (0/13)0% (0/1305)0% (0/319)
Rollout of Gitlab CI
Hi all, As those of you who watch and work on Frameworks repositories will be aware, we've just rolled out the first set of native Gitlab CI builds. These builds are at this time Linux only, but do include support for both regular branch builds as well as for Merge Requests. It is anticipated that Windows, FreeBSD and Android builds will follow in the near future - there are a few extra things we need to get completed first before they can be rolled out. As part of carrying out the build the scripts will also gather Code Coverage and Code Quality information using gcovr and cppcheck respectively, and this will be made available to you within the Gitlab interface. With regards to availability to projects outside Frameworks, projects that depend only on Frameworks (and no other KDE project) may enable CI for their project by adding the necessary .kde-ci.yml and .gitlab-ci.yml files to their repositories. I anticipate that once the necessary changes have been made to the "seed" jobs used to provision the initial artifacts it should be possible for all projects to rollout support (although i'd like to add ccache support to the system to ensure larger project builds complete promptly first). If anyone would like to help out with getting the seed jobs ready please let me know as this is definitely something that the community can assist with (and will also help with easing the rollout of Windows, FreeBSD and Android builds). For those projects that do go ahead with enabling Gitlab CI support please ensure you add the necessary .kde-ci.yml file beforehand, specifying in it the necessary Dependencies, as well as the necessary Options your project needs to customise for their build. A list of all the possible values in a .kde-ci.yml file can be found at https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/config-template.yml#L10 For those projects that are not yet able to enable the system, it is strongly encouraged that you go ahead and get the .kde-ci.yml files ready in your repository now - especially if other projects depend on your project. This will allow the rollout of the CI system to those projects to proceed much more smoothly (otherwise we will need to get them added to those projects which have other projects depending on them). Please note that this new infrastructure replaces all existing Gitlab CI jobs we provided in the initial testing phase, and those should be removed (much like how I did for Frameworks) when switching to the new setup. Thanks, Ben
KDE CI: Frameworks » kservice » kf5-qt5 FreeBSDQt5.15 - Build # 176 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20FreeBSDQt5.15/176/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Wed, 29 Sep 2021 09:00:00 + Build duration: 13 min and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 11 test(s), Skipped: 0 test(s), Total: 11 test(s)Name: projectroot.tests Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
KDE CI: Frameworks » kdelibs4support » kf5-qt5 SUSEQt5.15 - Build # 101 - Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kdelibs4support/job/kf5-qt5%20SUSEQt5.15/101/ Project: kf5-qt5 SUSEQt5.15 Date of build: Wed, 29 Sep 2021 08:43:30 + Build duration: 17 min and counting BUILD ARTIFACTS acc/KF5KDELibs4Support-5.87.0.xml 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: 38 test(s), Skipped: 0 test(s), Total: 39 test(s)Failed: projectroot.autotests.kmimetypetest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report29% (4/14)43% (124/291)43% (124/291)48% (22216/4)39% (14127/36196)Coverage Breakdown by Package Name FilesClassesLinesConditionalsdefault0% (0/1)0% (0/1)0% (0/88)0% (0/50)autotests98% (44/45)98% (44/45)97% (11654/12061)50% (8281/16641)src0% (0/1)0% (0/1)0% (0/4)0% (0/2)src.kdebugdialog0% (0/7)0% (0/7)0% (0/256)0% (0/61)src.kdecore76% (65/86)76% (65/86)54% (9785/18188)49% (5543/11400)src.kdeui19% (13/67)19% (13/67)8% (767/9714)6% (302/5296)src.kio7% (2/27)7% (2/27)0% (10/2273)0% (1/1140)src.kioslave.metainfo0% (0/1)0% (0/1)0% (0/32)0% (0/4)src.kparts0% (0/1)0% (0/1)0% (0/24)0% (0/12)src.kssl0% (0/8)0% (0/8)0% (0/1807)0% (0/843)src.kssl.kcm0% (0/3)0% (0/3)0% (0/265)0% (0/103)src.solid0% (0/3)0% (0/3)0% (0/196)0% (0/87)src.solid-networkstatus.kded0% (0/7)0% (0/7)0% (0/222)0% (0/90)tests0% (0/34)0% (0/34)0% (0/1536)0% (0/467)
KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.15 - Build # 122 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.15/122/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Wed, 29 Sep 2021 08:53:05 + Build duration: 6 min 6 sec and counting JUnit Tests Name: projectroot.autotests Failed: 14 test(s), Passed: 29 test(s), Skipped: 0 test(s), Total: 43 test(s)Failed: projectroot.autotests.client.kwayland_testCompositorFailed: projectroot.autotests.client.kwayland_testDataDeviceFailed: projectroot.autotests.client.kwayland_testDataSourceFailed: projectroot.autotests.client.kwayland_testIdleFailed: projectroot.autotests.client.kwayland_testRegionFailed: projectroot.autotests.client.kwayland_testShmPoolFailed: projectroot.autotests.client.kwayland_testSubCompositorFailed: projectroot.autotests.client.kwayland_testSubSurfaceFailed: projectroot.autotests.client.kwayland_testWaylandConnectionThreadFailed: projectroot.autotests.client.kwayland_testWaylandRegistryFailed: projectroot.autotests.client.kwayland_testWaylandShellFailed: projectroot.autotests.client.kwayland_testWaylandSurfaceFailed: projectroot.autotests.client.kwayland_testXdgShellV5Failed: projectroot.autotests.server.kwayland_testWaylandServerDisplay
KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1091 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1091/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Wed, 29 Sep 2021 08:52:35 + Build duration: 4 min 17 sec and counting JUnit Tests Name: projectroot Failed: 2 test(s), Passed: 58 test(s), Skipped: 0 test(s), Total: 60 test(s)Failed: projectroot.autotests.kiocore_kmountpointtestFailed: projectroot.autotests.kiowidgets_kdirlistertestName: 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)
KDE CI: Frameworks » kdav » kf5-qt5 SUSEQt5.15 - Build # 85 - Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kdav/job/kf5-qt5%20SUSEQt5.15/85/ Project: kf5-qt5 SUSEQt5.15 Date of build: Wed, 29 Sep 2021 08:42:25 + Build duration: 12 min and counting BUILD ARTIFACTS acc/KF5DAV-5.87.0.xml 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: 5 test(s), Skipped: 0 test(s), Total: 6 test(s)Failed: projectroot.autotests.kdav_davcollectionsmultifetchjobtest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report75% (3/4)67% (33/49)67% (33/49)45% (1023/2267)25% (398/1572)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests100% (7/7)100% (7/7)91% (360/397)50% (217/437)src.common63% (24/38)63% (24/38)39% (577/1474)24% (169/697)src.protocols67% (2/3)67% (2/3)28% (86/302)21% (12/58)test0% (0/1)0% (0/1)0% (0/94)0% (0/380)
KDE CI: Frameworks » kirigami » kf5-qt5 FreeBSDQt5.15 - Build # 613 - Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kirigami/job/kf5-qt5%20FreeBSDQt5.15/613/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Wed, 29 Sep 2021 08:50:00 + Build duration: 1 min 14 sec and counting JUnit Tests Name: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515 Failed: 1 test(s), Passed: 11 test(s), Skipped: 0 test(s), Total: 12 test(s)Failed: projectroot.usr.home.jenkins.workspace.Frameworks.kirigami.kf5-qt5_FreeBSDQt515.autotests.tst_theme.qml
KDE CI: Frameworks » kcrash » kf5-qt5 FreeBSDQt5.15 - Build # 95 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kcrash/job/kf5-qt5%20FreeBSDQt5.15/95/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Wed, 29 Sep 2021 08:41:55 + Build duration: 1 min 55 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 3 test(s)Failed: projectroot.autotests.metadatatest
KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 SUSEQt5.15 - Build # 289 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/289/ Project: kf5-qt5 SUSEQt5.15 Date of build: Wed, 29 Sep 2021 08:37:25 + Build duration: 4 min 41 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.KDEFetchTranslationsName: projectroot.home.jenkins.workspace.Frameworks.extra-cmake-modules Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.tests Failed: 0 test(s), Passed: 76 test(s), Skipped: 0 test(s), Total: 76 test(s)Name: projectroot.tests.ECMAddTests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) Cobertura Report Project Coverage Summary Name Cobertura Coverage Report
KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 FreeBSDQt5.15 - Build # 251 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20FreeBSDQt5.15/251/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Wed, 29 Sep 2021 08:37:25 + Build duration: 2 min 24 sec and counting JUnit Tests Name: projectroot Failed: 1 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.KDEFetchTranslationsName: projectroot.tests Failed: 0 test(s), Passed: 66 test(s), Skipped: 0 test(s), Total: 66 test(s)Name: projectroot.tests.ECMAddTests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)
KDE CI: Frameworks » attica » kf5-qt5 WindowsMSVCQt5.15 - Build # 79 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/attica/job/kf5-qt5%20WindowsMSVCQt5.15/79/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 29 Sep 2021 08:33:56 + Build duration: 1 min 51 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)
KDE CI: Frameworks » attica » kf5-qt5 FreeBSDQt5.15 - Build # 86 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/attica/job/kf5-qt5%20FreeBSDQt5.15/86/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Wed, 29 Sep 2021 08:33:55 + Build duration: 45 sec and counting JUnit Tests Name: projectroot Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)
