Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 483412 - Build time went from 6 min to 55 min!
Summary: Build time went from 6 min to 55 min!
Status: CLOSED DUPLICATE of bug 483118
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: CI Admin Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-01 15:47 EST by Pascal Rapicault CLA
Modified: 2015-12-02 03:16 EST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2015-12-01 15:47:02 EST
Since yesterday, I can see that the build time went from 6 min to 55 min. Though we are really good at writing awesome code in a blink, this is definitely not the case :) Also we have not changed the build configuration.

From looking at the execution, it appears that the resolution of artifact is extremely slow. Maybe something changed there?
Comment 2 Pascal Rapicault CLA 2015-12-01 15:49:02 EST
Note that I have also restarted our hipp instance.
Comment 3 Denis Roy CLA 2015-12-01 16:10:20 EST
This is like saying "your code is crashing".  Can you point out which step has taken so much longer?
Comment 4 Pascal Rapicault CLA 2015-12-01 20:26:41 EST
If you take the problematic build https://hudson.eclipse.org/egerrit/job/EGerrit/345/ It lasted 56 min
  It starts at 09:57 
  The Maven part ends at 10:49 Note that the Maven build is setup to redownload everything every time
  The Sonar analysis ends at 10:53

Now if you compare to the last fast build https://hudson.eclipse.org/egerrit/job/EGerrit/343/  It lasted 6 min
  It starts at 10:31
  The Maven part ends at 10:36 Note that the Maven build is setup to redownload everything every time
  The Sonar analysis ends at 10:38

Finally the most recent build done today https://hudson.eclipse.org/egerrit/job/EGerrit/350 lasted 13 min
  It starts at 17:44 
  The Maven part ends at 17:55
  The Sonar analysis ends at 17:58


As I said, when I was observing the log, the retrieval of artifacts (even pom.xml which are supposed to be quick to get) felt really slow.
Comment 5 David Williams CLA 2015-12-01 21:20:51 EST
There are a lot of "download" issues documented in bug 483118, that some of us have been having ... thought to be "proxy related". 

One of our builds just failed tonight, "running on build.eclipse.org" with 
[ERROR] An error occurred while transferring artifact packed: osgi.bundle,org.apache.felix.gogo.shell,0.10.0.v201212101605 from repository http://download.eclipse.org/tools/orbit/downloads/drops/S20151016170251/repository:
[ERROR]    Retry another mirror:
[ERROR]       Unable to read repository at http://download.eclipse.org/tools/orbit/downloads/drops/S20151016170251/repository/plugins/org.apache.felix.gogo.shell_0.10.0.v201212101605.jar.pack.gz.
[ERROR] Internal error: org.eclipse.tycho.repository.local.MirroringArtifactProvider$MirroringFailedException: Could not mirror artifact osgi.bundle,org.apache.felix.gogo.shell,0.10.0.v201212101605 into the local Maven repository.See log output for details. connect timed out

= = = = 

Plus, during earlier unit testing, on Hudson, we had a number of failures that all had in common something like 

!ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2015-12-01 14:40:10.746
!MESSAGE Connection to http://download.eclipse.org/eclipse/updates/4.6-I-builds/I20151201-1100/p2.index failed on Operation timed out. Retry attempt 0 started
!STACK 0
java.net.ConnectException: Operation timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589) 
        ....
Comment 6 Pascal Rapicault CLA 2015-12-01 21:48:59 EST
We also had those same failures earlier during the day.
Comment 7 Mikaël Barbero CLA 2015-12-02 03:16:59 EST

*** This bug has been marked as a duplicate of bug 483118 ***