Build failed in Jenkins: plasma-framework_master_qt5 #875

KDE CI System null at kde.org
Wed Oct 30 17:40:44 UTC 2013


See <http://build.kde.org/job/plasma-framework_master_qt5/875/changes>

Changes:

[notmart] removing panels works

------------------------------------------
Started by remote host 127.0.0.1 with note: Triggered by commit
Building remotely on LinuxSlave - 3 in workspace <http://build.kde.org/job/plasma-framework_master_qt5/ws/>
Running Prebuild steps
[plasma-framework_master_qt5] $ /bin/sh -xe /tmp/hudson1730342452513293531.sh
+ /home/jenkins/scripts/setup-env.sh

Preparing to perform KDE Continuous Integration build
== Setting Up Sources

fatal: Unable to look up anongit.kde.org (port 9418) (Name or service not known)

== Cleaning Source Tree

HEAD is now at 33e4c1c add panel action is back
Success build forhudson.tasks.Shell at 403a7d73
Fetching changes from the remote Git repository
Fetching upstream changes from git://anongit.kde.org/plasma-framework.git
Checking out Revision 512aecb8034f720c30c5d89ecef1528ba22c9b1c (refs/heads/jenkins)
[plasma-framework_master_qt5] $ /bin/sh -xe /tmp/hudson2991792156718662786.sh
+ /home/jenkins/scripts/execute-job.sh

KDE Continuous Integration Build
== Building Project: plasma-framework - Branch master
== Build Dependencies:
==== extra-cmake-modules - Branch master
==== libstreams - Branch master
==== strigiclient - Branch master
==== attica - Branch master
==== kactivities - Branch frameworks
==== strigidaemon - Branch master
==== libstreamanalyzer - Branch master
==== phonon - Branch master
==== qt5 - Branch stable
==== kdelibs - Branch frameworks
==== strigiutils - Branch master

== Applying Patches
=== No patches to apply

== Syncing Dependencies from Master Server

ssh: Could not resolve hostname build.kde.org: Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(605) [Receiver=3.0.9]
Syncing dependencies from master server for project plasma-framework failed.
Build step 'Execute shell' marked build as failure
[WARNINGS] Skipping publisher since build result is FAILURE
Skipping Cobertura coverage report as build was not UNSTABLE or better ...
Recording test results


More information about the Kde-frameworks-devel mailing list