Failed build on Jekins

Gilles Caulier caulier.gilles at gmail.com
Tue Jun 6 19:37:10 BST 2017


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 <metzpinguin at gmail.com>:
> 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
> <veaceslav.munteanu90 at gmail.com>:
>> > 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?



More information about the Digikam-devel mailing list