Re: [mdt-papyrus.dev] Gerrit builds time out

[Johan Hardy <Johan.Hardy@xxxxxxxxxxx>]

Hi,

Confirmed Christian, I experienced the same problem this monring but on another project.

Johan

 

From: mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] On Behalf Of Christian W. Damus
Sent: mardi 1 décembre 2015 15:01
To: Papyrus Project list
Cc: Papyrus Project list
Subject: Re: [mdt-papyrus.dev] Gerrit builds time out

 

Thanks, Camille,

 

I’m glad you’re looking into it.  The JAR downloads in my builds’ console logs all show 0 kB/s, and they tick by very slowly, which suggests that it’s setting up the initial HTTP connection that takes time and the actual transfer then is so fast that Maven doesn’t report any progress intervals (with non-zero kB/s) on them.  But, I’m just guessing now.

 

I don’t think dependency resolution is any slower than before; it really looks to me like the dependency downloads are the bottleneck.

 

Cheers,

 

Christian

 

 

On Tue, Dec 1, 2015 at 8:51 AM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:

Hi Christian,

 

I see green builds from yesterday on Gerrit. And now it takes more than an hour to simply “resolve & download dependencies” (Without compiling anything)

 

So there’s definitely something wrong. It doesn’t seem to be the actual download speed, as it takes less than 1 second to download each artifact, so I suspect the “Resolve dependencies” step is slower than usual. This might be a simple server overload issue, or there might be something else.

 

AFAIK, Papyrus used to be the only project on our HIPP instance a few months ago, but this doesn’t seem to be the case anymore, as I frequently see the server quite busy even when no Papyrus jobs are running

 

I can tweak the Gerrit Job configuration a little bit to improve performances (Similar to what I did for the Extra & Tests jobs), but that would only save a few minutes.

 

Regarding the download speeds for download.eclipse.org, we are currently referencing our dependency update sites via HTTP. We could improve this by using the local filesystem instead, for all update sites located under http://download.eclipse.org. This would also improve the performances, but once again, I don’t believe that download speeds are the source of the issue here.

 

I’m running a dummy Gerrit job to see more precisely what actually takes time

 

Regards,

Camille

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : mardi 1 décembre 2015 14:02
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [mdt-papyrus.dev] Gerrit builds time out

 

Hi, team,

 

It appears that the Gerrit builds are now routinely timing out.  Looking at the glacial pace of the console’s progress in my browser, it appears that fetching JARs from the download server is bizarrely slow.  Don’t these downloads just all route locally in Eclipse Foundation’s network, at presumably blazing speeds?  Is there something in our Hudson instance making this so slow, that we should re-start it?  Or maybe this is going to be normal, and we need to increase our build time-out setting?

 

Any advice or other information will be appreciated.

 

Thanks,

 

Christian

 

 

------------------------------------------------------------------------------

E-MAIL DISCLAIMER

The present message may contain confidential and/or legally privileged information. If you are not the intended addressee and in case of a transmission error, please notify the sender immediately and destroy this E-mail. Disclosure, reproduction or distribution of this document and its possible attachments is strictly forbidden.

SPACEBEL denies all liability for incomplete, improper, inaccurate, intercepted, (partly) destroyed, lost and/or belated transmission of the current information given that unencrypted electronic transmission cannot currently be guaranteed to be secure or error free.
Upon request or in conformity with formal, contractual agreements, an originally signed hard copy will be sent to you to confirm the information contained in this E-mail.

SPACEBEL denies all liability where E-mail is used for private use.

SPACEBEL cannot be held responsible for possible viruses that might corrupt this message and/or your computer system.
-------------------------------------------------------------------------------