Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Hudson builds fail on bogus time-out error
Hi,

Now it looks like we just have some kind of severe performance problem in accessing download.eclipse.org via HTTP:  fetching the metadata from p2 repositories hosted there is extremely slow.  I’m working on generation of targets localized for use on Eclipse.org that access the downloads via the local filesystem, as is done in Papyrus.  The build would automatically detect when it is running in the HIPP on Eclipse.org to activate that option.

Cheers,

Christian


On 5 October, 2016 at 08:47:30, Christian Damus (give.a.damus@xxxxxxxxx) wrote:

Hi, Team,

It appears that we now have Gerrit builds failing on a time-out error accessing the latest successful build results of the Papyrus Developer component:

[ERROR] Failed to resolve target definition /jobs/genie.papyrus-rt/Papyrus-RT-Gerrit-Core/workspace/source/org.eclipse.papyrusrt.targetplatform/papyrusrelease/org.eclipse.papyrusrt.targetplatform.neon.rt.included/org.eclipse.papyrusrt.targetplatform.neon.rt.included.target: Failed to load p2 metadata repository from location http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository/: Unable to read repository at http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository/content.xml. Connect to hudson.eclipse.org:80 timed out -> [Help 1]
org.apache.maven.MavenExecutionException: Failed to resolve target definition /jobs/genie.papyrus-rt/Papyrus-RT-Gerrit-Core/workspace/source/org.eclipse.papyrusrt.targetplatform/papyrusrelease/org.eclipse.papyrusrt.targetplatform.neon.rt.included/org.eclipse.papyrusrt.targetplatform.neon.rt.included.target: Failed to load p2 metadata repository from location http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository/
        at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:100)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:266)
        ...
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to hudson.eclipse.org:80 timed out
        at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
   ...









I don’t think that anything has changed in the Papyrus builds that
could cause this.  Is it possible that today's plug-in
installations and/or restart of the Papyrus-RT HIPP could have
broken HTTP connections to the other HIPPs at eclipse.org?








And I don’t suppose it will be just
the Gerrit builds that fail, but the main component and product
builds, too, because they all use the same target-platform files.
 Papyrus has two forms of every TP, one using HTTP access and
one using local disk access for use on the Hudson build servers.
 Should we be doing the same?  I have no trouble
accessing the required resources in the Papyrus Hudson instance
from home; it’s only our builds that are timing out.





This would be another thing to
account for in the single-sourcing of TPs for the build and Oomph
setups for the developers.







Thanks,





Christian



































  Back to the top