digiKam › digikam-devel

Failed build on Jekins

Classic

List

Threaded

8 messages Options

Veaceslav Munteanu-2

Failed build on Jekins

Hello developers,

after this commit:

https://cgit.kde.org/digikam.git/commit/?id=cb7a04787aa2d734b469a74d042b6125864df3fa

digikam is not building on jenkins anymore...

Does anybody have any idea why?

Gilles Caulier-4

Re: Failed build on Jekins

Sound like Jenkis CI suite is broken :

12:35:33 Started by an SCM change
12:35:33 [EnvInject] - Loading node environment variables.
12:35:33 Building on master in workspace
/var/lib/jenkins/sources/digikam/kf5-qt5
12:35:33 > git rev-parse --is-inside-work-tree # timeout=10
12:35:33 Fetching changes from the remote Git repository
12:35:33 > git config remote.origin.url git://anongit.kde.org/digikam
# timeout=10
12:35:33 Fetching upstream changes from git://anongit.kde.org/digikam
12:35:33 > git --version # timeout=10
12:35:33 > git fetch --tags --progress git://anongit.kde.org/digikam
+refs/heads/*:refs/remotes/origin/* # timeout=120
12:35:37 > git rev-parse origin/master^{commit} # timeout=10
12:35:37 Checking out Revision
09ab6676a7ead1b55b4b4d3c30f615b573319e9e (origin/master)
12:35:37 > git config core.sparsecheckout # timeout=10
12:35:37 > git checkout -f 09ab6676a7ead1b55b4b4d3c30f615b573319e9e
12:35:38 > git rev-list 18189cd53354ac603a8522906052fe5b9b6e47c3 # timeout=10
12:35:39 Strings match run condition: string 1=[], string 2=[gcc]
12:35:39 Run condition [Strings match] preventing perform for step
[Builder to mark whether executed]
12:35:39 Triggering digikam master kf5-qt5 » Linux,gcc
12:35:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
the queue: Waiting for next available executor on
Swarm-2a77ff57083c-10.150.83.1
12:36:43 Configuration digikam master kf5-qt5 » Linux,gcc is still in
the queue: Jenkins doesn’t have label Linux
12:36:43 Swarm-978269d99588-10.150.82.1 is offline
12:36:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
the queue: Waiting for next available executor on Linux
12:39:27 Configuration digikam master kf5-qt5 » Linux,gcc is still in
the queue: Waiting for next available executor on
Swarm-2a77ff57083c-10.150.83.1
12:40:12 Configuration digikam master kf5-qt5 » Linux,gcc is still in
the queue: Jenkins doesn’t have label Linux
12:40:13 Configuration digikam master kf5-qt5 » Linux,gcc is still in
the queue: Jenkins doesn’t have label Linux
12:40:13 Swarm-282e0406a699-10.150.82.1 is offline
12:59:04 digikam master kf5-qt5 » Linux,gcc completed with result FAILURE
12:59:04 Finished: FAILURE

All compile fine on my computer...

Gilles

2017-06-06 17:21 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
> Hello developers,
>
> after this commit:
>
> https://cgit.kde.org/digikam.git/commit/?id=cb7a04787aa2d734b469a74d042b6125864df3fa
>
> digikam is not building on jenkins anymore...
>
> Does anybody have any idea why?

Maik Qualmann

Re: Failed build on Jekins

A different thing I get no Jekins mails more for some time, falls me straight
on. Why?

Maik

Am Dienstag, 6. Juni 2017, 17:53:59 CEST schrieb Gilles Caulier:

> Sound like Jenkis CI suite is broken :
>
> 12:35:33 Started by an SCM change
> 12:35:33 [EnvInject] - Loading node environment variables.
> 12:35:33 Building on master in workspace
> /var/lib/jenkins/sources/digikam/kf5-qt5
> 12:35:33 > git rev-parse --is-inside-work-tree # timeout=10
> 12:35:33 Fetching changes from the remote Git repository
> 12:35:33 > git config remote.origin.url git://anongit.kde.org/digikam
> # timeout=10
> 12:35:33 Fetching upstream changes from git://anongit.kde.org/digikam
> 12:35:33 > git --version # timeout=10
> 12:35:33 > git fetch --tags --progress git://anongit.kde.org/digikam
> +refs/heads/*:refs/remotes/origin/* # timeout=120
> 12:35:37 > git rev-parse origin/master^{commit} # timeout=10
> 12:35:37 Checking out Revision
> 09ab6676a7ead1b55b4b4d3c30f615b573319e9e (origin/master)
> 12:35:37 > git config core.sparsecheckout # timeout=10
> 12:35:37 > git checkout -f 09ab6676a7ead1b55b4b4d3c30f615b573319e9e
> 12:35:38 > git rev-list 18189cd53354ac603a8522906052fe5b9b6e47c3 #
> timeout=10 12:35:39 Strings match run condition: string 1=[], string
> 2=[gcc]
> 12:35:39 Run condition [Strings match] preventing perform for step
> [Builder to mark whether executed]
> 12:35:39 Triggering digikam master kf5-qt5 » Linux,gcc
> 12:35:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
> the queue: Waiting for next available executor on
> Swarm-2a77ff57083c-10.150.83.1
> 12:36:43 Configuration digikam master kf5-qt5 » Linux,gcc is still in
> the queue: Jenkins doesn’t have label Linux
> 12:36:43 Swarm-978269d99588-10.150.82.1 is offline
> 12:36:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
> the queue: Waiting for next available executor on Linux
> 12:39:27 Configuration digikam master kf5-qt5 » Linux,gcc is still in
> the queue: Waiting for next available executor on
> Swarm-2a77ff57083c-10.150.83.1
> 12:40:12 Configuration digikam master kf5-qt5 » Linux,gcc is still in
> the queue: Jenkins doesn’t have label Linux
> 12:40:13 Configuration digikam master kf5-qt5 » Linux,gcc is still in
> the queue: Jenkins doesn’t have label Linux
> 12:40:13 Swarm-282e0406a699-10.150.82.1 is offline
> 12:59:04 digikam master kf5-qt5 » Linux,gcc completed with result FAILURE
> 12:59:04 Finished: FAILURE
>
> All compile fine on my computer...
>
> Gilles
>
> 2017-06-06 17:21 GMT+02:00 Veaceslav Munteanu

<[hidden email]>:

> > Hello developers,
> >
> > after this commit:
> >
> > https://cgit.kde.org/digikam.git/commit/?id=cb7a04787aa2d734b469a74d042b61
> > 25864df3fa
> >
> > digikam is not building on jenkins anymore...
> >
> > Does anybody have any idea why?

Gilles Caulier-4

Re: Failed build on Jekins

Hi Maik,

No idea. I must admit that i do receive a mail from KDE CI since a
while. I think it's relevant of Phabricator integration in KDE server.

Gilles

2017-06-06 18:39 GMT+02:00 Maik Qualmann <[hidden email]>:

> A different thing I get no Jekins mails more for some time, falls me straight
> on. Why?
>
> Maik
>
> Am Dienstag, 6. Juni 2017, 17:53:59 CEST schrieb Gilles Caulier:
>> Sound like Jenkis CI suite is broken :
>>
>> 12:35:33 Started by an SCM change
>> 12:35:33 [EnvInject] - Loading node environment variables.
>> 12:35:33 Building on master in workspace
>> /var/lib/jenkins/sources/digikam/kf5-qt5
>> 12:35:33 > git rev-parse --is-inside-work-tree # timeout=10
>> 12:35:33 Fetching changes from the remote Git repository
>> 12:35:33 > git config remote.origin.url git://anongit.kde.org/digikam
>> # timeout=10
>> 12:35:33 Fetching upstream changes from git://anongit.kde.org/digikam
>> 12:35:33 > git --version # timeout=10
>> 12:35:33 > git fetch --tags --progress git://anongit.kde.org/digikam
>> +refs/heads/*:refs/remotes/origin/* # timeout=120
>> 12:35:37 > git rev-parse origin/master^{commit} # timeout=10
>> 12:35:37 Checking out Revision
>> 09ab6676a7ead1b55b4b4d3c30f615b573319e9e (origin/master)
>> 12:35:37 > git config core.sparsecheckout # timeout=10
>> 12:35:37 > git checkout -f 09ab6676a7ead1b55b4b4d3c30f615b573319e9e
>> 12:35:38 > git rev-list 18189cd53354ac603a8522906052fe5b9b6e47c3 #
>> timeout=10 12:35:39 Strings match run condition: string 1=[], string
>> 2=[gcc]
>> 12:35:39 Run condition [Strings match] preventing perform for step
>> [Builder to mark whether executed]
>> 12:35:39 Triggering digikam master kf5-qt5 » Linux,gcc
>> 12:35:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>> the queue: Waiting for next available executor on
>> Swarm-2a77ff57083c-10.150.83.1
>> 12:36:43 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>> the queue: Jenkins doesn’t have label Linux
>> 12:36:43 Swarm-978269d99588-10.150.82.1 is offline
>> 12:36:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>> the queue: Waiting for next available executor on Linux
>> 12:39:27 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>> the queue: Waiting for next available executor on
>> Swarm-2a77ff57083c-10.150.83.1
>> 12:40:12 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>> the queue: Jenkins doesn’t have label Linux
>> 12:40:13 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>> the queue: Jenkins doesn’t have label Linux
>> 12:40:13 Swarm-282e0406a699-10.150.82.1 is offline
>> 12:59:04 digikam master kf5-qt5 » Linux,gcc completed with result FAILURE
>> 12:59:04 Finished: FAILURE
>>
>> All compile fine on my computer...
>>
>> Gilles
>>
>> 2017-06-06 17:21 GMT+02:00 Veaceslav Munteanu
> <[hidden email]>:
>> > Hello developers,
>> >
>> > after this commit:
>> >
>> > https://cgit.kde.org/digikam.git/commit/?id=cb7a04787aa2d734b469a74d042b61
>> > 25864df3fa
>> >
>> > digikam is not building on jenkins anymore...
>> >
>> > Does anybody have any idea why?

Veaceslav Munteanu-2

Re: Failed build on Jekins

The latest build output is here:

https://build.kde.org/job/digikam%20master%20kf5-qt5/1745/PLATFORM=Linux,compiler=gcc/console

and it is failing to find symbols:

21:55:33 ../libs/transitionmngr/CMakeFiles/digikamlibtransitionmngr_src.dir/transitionpreview.cpp.o:
In function `Digikam::TransitionPreview::setImagesList(QList<QUrl>
const&)':
21:55:33 /home/jenkins/sources/digikam/kf5-qt5/libs/transitionmngr/transitionpreview.cpp:84:
undefined reference to `Digikam::VidSlideTask::makeFramedImage(QString
const&, QSize const&)'
21:55:33 /home/jenkins/sources/digikam/kf5-qt5/libs/transitionmngr/transitionpreview.cpp:88:
undefined reference to `Digikam::VidSlideTask::makeFramedImage(QString
const&, QSize const&)'

Normally I do not expect the build to fail until we add a new dependency...

On Tue, Jun 6, 2017 at 8:37 PM, Gilles Caulier <[hidden email]> wrote:

> Hi Maik,
>
> No idea. I must admit that i do receive a mail from KDE CI since a
> while. I think it's relevant of Phabricator integration in KDE server.
>
> Gilles
>
> 2017-06-06 18:39 GMT+02:00 Maik Qualmann <[hidden email]>:
>> A different thing I get no Jekins mails more for some time, falls me straight
>> on. Why?
>>
>> Maik
>>
>> Am Dienstag, 6. Juni 2017, 17:53:59 CEST schrieb Gilles Caulier:
>>> Sound like Jenkis CI suite is broken :
>>>
>>> 12:35:33 Started by an SCM change
>>> 12:35:33 [EnvInject] - Loading node environment variables.
>>> 12:35:33 Building on master in workspace
>>> /var/lib/jenkins/sources/digikam/kf5-qt5
>>> 12:35:33 > git rev-parse --is-inside-work-tree # timeout=10
>>> 12:35:33 Fetching changes from the remote Git repository
>>> 12:35:33 > git config remote.origin.url git://anongit.kde.org/digikam
>>> # timeout=10
>>> 12:35:33 Fetching upstream changes from git://anongit.kde.org/digikam
>>> 12:35:33 > git --version # timeout=10
>>> 12:35:33 > git fetch --tags --progress git://anongit.kde.org/digikam
>>> +refs/heads/*:refs/remotes/origin/* # timeout=120
>>> 12:35:37 > git rev-parse origin/master^{commit} # timeout=10
>>> 12:35:37 Checking out Revision
>>> 09ab6676a7ead1b55b4b4d3c30f615b573319e9e (origin/master)
>>> 12:35:37 > git config core.sparsecheckout # timeout=10
>>> 12:35:37 > git checkout -f 09ab6676a7ead1b55b4b4d3c30f615b573319e9e
>>> 12:35:38 > git rev-list 18189cd53354ac603a8522906052fe5b9b6e47c3 #
>>> timeout=10 12:35:39 Strings match run condition: string 1=[], string
>>> 2=[gcc]
>>> 12:35:39 Run condition [Strings match] preventing perform for step
>>> [Builder to mark whether executed]
>>> 12:35:39 Triggering digikam master kf5-qt5 » Linux,gcc
>>> 12:35:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>> the queue: Waiting for next available executor on
>>> Swarm-2a77ff57083c-10.150.83.1
>>> 12:36:43 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>> the queue: Jenkins doesn’t have label Linux
>>> 12:36:43 Swarm-978269d99588-10.150.82.1 is offline
>>> 12:36:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>> the queue: Waiting for next available executor on Linux
>>> 12:39:27 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>> the queue: Waiting for next available executor on
>>> Swarm-2a77ff57083c-10.150.83.1
>>> 12:40:12 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>> the queue: Jenkins doesn’t have label Linux
>>> 12:40:13 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>> the queue: Jenkins doesn’t have label Linux
>>> 12:40:13 Swarm-282e0406a699-10.150.82.1 is offline
>>> 12:59:04 digikam master kf5-qt5 » Linux,gcc completed with result FAILURE
>>> 12:59:04 Finished: FAILURE
>>>
>>> All compile fine on my computer...
>>>
>>> Gilles
>>>
>>> 2017-06-06 17:21 GMT+02:00 Veaceslav Munteanu
>> <[hidden email]>:
>>> > Hello developers,
>>> >
>>> > after this commit:
>>> >
>>> > https://cgit.kde.org/digikam.git/commit/?id=cb7a04787aa2d734b469a74d042b61
>>> > 25864df3fa
>>> >
>>> > digikam is not building on jenkins anymore...
>>> >
>>> > Does anybody have any idea why?

Gilles Caulier-4

Re: Failed build on Jekins

Hi Veaceslav,

This is not a new dependency, just a new class compiled in core. The
export symbols rule is not set. This is why the linking stage fail.

The surprising stuff is that i cannot reproduce the problem here.
Probably different GCC versions give different result at linking time.

I fix the problem.

Gilles

2017-06-07 11:21 GMT+02:00 Veaceslav Munteanu <[hidden email]>:

> The latest build output is here:
>
> https://build.kde.org/job/digikam%20master%20kf5-qt5/1745/PLATFORM=Linux,compiler=gcc/console
>
> and it is failing to find symbols:
>
> 21:55:33 ../libs/transitionmngr/CMakeFiles/digikamlibtransitionmngr_src.dir/transitionpreview.cpp.o:
> In function `Digikam::TransitionPreview::setImagesList(QList<QUrl>
> const&)':
> 21:55:33 /home/jenkins/sources/digikam/kf5-qt5/libs/transitionmngr/transitionpreview.cpp:84:
> undefined reference to `Digikam::VidSlideTask::makeFramedImage(QString
> const&, QSize const&)'
> 21:55:33 /home/jenkins/sources/digikam/kf5-qt5/libs/transitionmngr/transitionpreview.cpp:88:
> undefined reference to `Digikam::VidSlideTask::makeFramedImage(QString
> const&, QSize const&)'
>
> Normally I do not expect the build to fail until we add a new dependency...
>
> On Tue, Jun 6, 2017 at 8:37 PM, Gilles Caulier <[hidden email]> wrote:
>> Hi Maik,
>>
>> No idea. I must admit that i do receive a mail from KDE CI since a
>> while. I think it's relevant of Phabricator integration in KDE server.
>>
>> Gilles
>>
>> 2017-06-06 18:39 GMT+02:00 Maik Qualmann <[hidden email]>:
>>> A different thing I get no Jekins mails more for some time, falls me straight
>>> on. Why?
>>>
>>> Maik
>>>
>>> Am Dienstag, 6. Juni 2017, 17:53:59 CEST schrieb Gilles Caulier:
>>>> Sound like Jenkis CI suite is broken :
>>>>
>>>> 12:35:33 Started by an SCM change
>>>> 12:35:33 [EnvInject] - Loading node environment variables.
>>>> 12:35:33 Building on master in workspace
>>>> /var/lib/jenkins/sources/digikam/kf5-qt5
>>>> 12:35:33 > git rev-parse --is-inside-work-tree # timeout=10
>>>> 12:35:33 Fetching changes from the remote Git repository
>>>> 12:35:33 > git config remote.origin.url git://anongit.kde.org/digikam
>>>> # timeout=10
>>>> 12:35:33 Fetching upstream changes from git://anongit.kde.org/digikam
>>>> 12:35:33 > git --version # timeout=10
>>>> 12:35:33 > git fetch --tags --progress git://anongit.kde.org/digikam
>>>> +refs/heads/*:refs/remotes/origin/* # timeout=120
>>>> 12:35:37 > git rev-parse origin/master^{commit} # timeout=10
>>>> 12:35:37 Checking out Revision
>>>> 09ab6676a7ead1b55b4b4d3c30f615b573319e9e (origin/master)
>>>> 12:35:37 > git config core.sparsecheckout # timeout=10
>>>> 12:35:37 > git checkout -f 09ab6676a7ead1b55b4b4d3c30f615b573319e9e
>>>> 12:35:38 > git rev-list 18189cd53354ac603a8522906052fe5b9b6e47c3 #
>>>> timeout=10 12:35:39 Strings match run condition: string 1=[], string
>>>> 2=[gcc]
>>>> 12:35:39 Run condition [Strings match] preventing perform for step
>>>> [Builder to mark whether executed]
>>>> 12:35:39 Triggering digikam master kf5-qt5 » Linux,gcc
>>>> 12:35:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>> the queue: Waiting for next available executor on
>>>> Swarm-2a77ff57083c-10.150.83.1
>>>> 12:36:43 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>> the queue: Jenkins doesn’t have label Linux
>>>> 12:36:43 Swarm-978269d99588-10.150.82.1 is offline
>>>> 12:36:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>> the queue: Waiting for next available executor on Linux
>>>> 12:39:27 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>> the queue: Waiting for next available executor on
>>>> Swarm-2a77ff57083c-10.150.83.1
>>>> 12:40:12 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>> the queue: Jenkins doesn’t have label Linux
>>>> 12:40:13 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>> the queue: Jenkins doesn’t have label Linux
>>>> 12:40:13 Swarm-282e0406a699-10.150.82.1 is offline
>>>> 12:59:04 digikam master kf5-qt5 » Linux,gcc completed with result FAILURE
>>>> 12:59:04 Finished: FAILURE
>>>>
>>>> All compile fine on my computer...
>>>>
>>>> Gilles
>>>>
>>>> 2017-06-06 17:21 GMT+02:00 Veaceslav Munteanu
>>> <[hidden email]>:
>>>> > Hello developers,
>>>> >
>>>> > after this commit:
>>>> >
>>>> > https://cgit.kde.org/digikam.git/commit/?id=cb7a04787aa2d734b469a74d042b61
>>>> > 25864df3fa
>>>> >
>>>> > digikam is not building on jenkins anymore...
>>>> >
>>>> > Does anybody have any idea why?

Gilles Caulier-4

Re: Failed build on Jekins

Done :

https://commits.kde.org/digikam/296aacfe787efc5f39ae942fcec22f6f303523b1

Gilles

2017-06-07 11:35 GMT+02:00 Gilles Caulier <[hidden email]>:

> Hi Veaceslav,
>
> This is not a new dependency, just a new class compiled in core. The
> export symbols rule is not set. This is why the linking stage fail.
>
> The surprising stuff is that i cannot reproduce the problem here.
> Probably different GCC versions give different result at linking time.
>
> I fix the problem.
>
> Gilles
>
> 2017-06-07 11:21 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
>> The latest build output is here:
>>
>> https://build.kde.org/job/digikam%20master%20kf5-qt5/1745/PLATFORM=Linux,compiler=gcc/console
>>
>> and it is failing to find symbols:
>>
>> 21:55:33 ../libs/transitionmngr/CMakeFiles/digikamlibtransitionmngr_src.dir/transitionpreview.cpp.o:
>> In function `Digikam::TransitionPreview::setImagesList(QList<QUrl>
>> const&)':
>> 21:55:33 /home/jenkins/sources/digikam/kf5-qt5/libs/transitionmngr/transitionpreview.cpp:84:
>> undefined reference to `Digikam::VidSlideTask::makeFramedImage(QString
>> const&, QSize const&)'
>> 21:55:33 /home/jenkins/sources/digikam/kf5-qt5/libs/transitionmngr/transitionpreview.cpp:88:
>> undefined reference to `Digikam::VidSlideTask::makeFramedImage(QString
>> const&, QSize const&)'
>>
>> Normally I do not expect the build to fail until we add a new dependency...
>>
>> On Tue, Jun 6, 2017 at 8:37 PM, Gilles Caulier <[hidden email]> wrote:
>>> Hi Maik,
>>>
>>> No idea. I must admit that i do receive a mail from KDE CI since a
>>> while. I think it's relevant of Phabricator integration in KDE server.
>>>
>>> Gilles
>>>
>>> 2017-06-06 18:39 GMT+02:00 Maik Qualmann <[hidden email]>:
>>>> A different thing I get no Jekins mails more for some time, falls me straight
>>>> on. Why?
>>>>
>>>> Maik
>>>>
>>>> Am Dienstag, 6. Juni 2017, 17:53:59 CEST schrieb Gilles Caulier:
>>>>> Sound like Jenkis CI suite is broken :
>>>>>
>>>>> 12:35:33 Started by an SCM change
>>>>> 12:35:33 [EnvInject] - Loading node environment variables.
>>>>> 12:35:33 Building on master in workspace
>>>>> /var/lib/jenkins/sources/digikam/kf5-qt5
>>>>> 12:35:33 > git rev-parse --is-inside-work-tree # timeout=10
>>>>> 12:35:33 Fetching changes from the remote Git repository
>>>>> 12:35:33 > git config remote.origin.url git://anongit.kde.org/digikam
>>>>> # timeout=10
>>>>> 12:35:33 Fetching upstream changes from git://anongit.kde.org/digikam
>>>>> 12:35:33 > git --version # timeout=10
>>>>> 12:35:33 > git fetch --tags --progress git://anongit.kde.org/digikam
>>>>> +refs/heads/*:refs/remotes/origin/* # timeout=120
>>>>> 12:35:37 > git rev-parse origin/master^{commit} # timeout=10
>>>>> 12:35:37 Checking out Revision
>>>>> 09ab6676a7ead1b55b4b4d3c30f615b573319e9e (origin/master)
>>>>> 12:35:37 > git config core.sparsecheckout # timeout=10
>>>>> 12:35:37 > git checkout -f 09ab6676a7ead1b55b4b4d3c30f615b573319e9e
>>>>> 12:35:38 > git rev-list 18189cd53354ac603a8522906052fe5b9b6e47c3 #
>>>>> timeout=10 12:35:39 Strings match run condition: string 1=[], string
>>>>> 2=[gcc]
>>>>> 12:35:39 Run condition [Strings match] preventing perform for step
>>>>> [Builder to mark whether executed]
>>>>> 12:35:39 Triggering digikam master kf5-qt5 » Linux,gcc
>>>>> 12:35:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>>> the queue: Waiting for next available executor on
>>>>> Swarm-2a77ff57083c-10.150.83.1
>>>>> 12:36:43 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>>> the queue: Jenkins doesn’t have label Linux
>>>>> 12:36:43 Swarm-978269d99588-10.150.82.1 is offline
>>>>> 12:36:44 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>>> the queue: Waiting for next available executor on Linux
>>>>> 12:39:27 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>>> the queue: Waiting for next available executor on
>>>>> Swarm-2a77ff57083c-10.150.83.1
>>>>> 12:40:12 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>>> the queue: Jenkins doesn’t have label Linux
>>>>> 12:40:13 Configuration digikam master kf5-qt5 » Linux,gcc is still in
>>>>> the queue: Jenkins doesn’t have label Linux
>>>>> 12:40:13 Swarm-282e0406a699-10.150.82.1 is offline
>>>>> 12:59:04 digikam master kf5-qt5 » Linux,gcc completed with result FAILURE
>>>>> 12:59:04 Finished: FAILURE
>>>>>
>>>>> All compile fine on my computer...
>>>>>
>>>>> Gilles
>>>>>
>>>>> 2017-06-06 17:21 GMT+02:00 Veaceslav Munteanu
>>>> <[hidden email]>:
>>>>> > Hello developers,
>>>>> >
>>>>> > after this commit:
>>>>> >
>>>>> > https://cgit.kde.org/digikam.git/commit/?id=cb7a04787aa2d734b469a74d042b61
>>>>> > 25864df3fa
>>>>> >
>>>>> > digikam is not building on jenkins anymore...
>>>>> >
>>>>> > Does anybody have any idea why?

Gilles Caulier-4

Re: Failed build on Jekins

In reply to this post by Maik Qualmann

Maik,

The new KDE CI infrastructure is online. Look Ben mail posted today :

---------------------------------
Next week we will be introducing the new Continuous Integration system.
It can currently be found at https://build-sandbox.kde.org/

Prior to the switch over taking place, all developers are *strongly*
encouraged to check the status of their builds and tests. You will
also need to check the dependencies which have been installed.

This can be done by reviewing the build logs and other information
displayed by Jenkins for your project.

If your project is in Extragear and you have not previously requested
for your coverage to be continued then you will likely need to request
this.

Additionally, if you have previously requested for email alerts to be
provided, these will need to be re-requested.

The new system among other things has the option to provide both
FreeBSD and Windows builds. If you are interested in this for your
application, please file a Sysadmin request.

Note that in the case of Windows builds you'll need to provide
assistance in getting builds functional for everything above
Frameworks to your application in the event it depends on other KDE
software.

In regards to Qt 4 support, this has been discontinued. Only KF5 / Qt
5 builds are supported from this point onward.

Regards,
Ben
--------------------------------

Gilles

2017-06-06 18:39 GMT+02:00 Maik Qualmann <[hidden email]>: