Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 563816 - ci.eclipse.org/jgit terribly slow
Summary: ci.eclipse.org/jgit terribly slow
Status: CLOSED DUPLICATE of bug 563645
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: CI Admin Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-02 05:14 EDT by Thomas Wolf CLA
Modified: 2020-06-09 05:21 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Wolf CLA 2020-06-02 05:14:18 EDT
JGit build run significantly slower recently. Normally JGit builds take some 30-40 minutes, now we're more often than not hitting timeouts after 60 minutes.

See https://ci.eclipse.org/jgit/job/jgit/buildTimeTrend .

As far as I can tell it's not caused by some code changes in JGit. Locally, builds run fast. (Much faster than on that Kubernetes infrastructure anyway; a normal full build including tests (but excluding signing) take about 15 minutes locally.)

Just increasing the timeout for the build is probably not an option, the latest build (#80) just got about 50% of its work done before being aborted.

Given that there are other similar reports in bug 563221 or bug 563645, the slowness of builds might be a general problem?
Comment 1 Thomas Wolf CLA 2020-06-02 05:18:53 EDT
P.S.: egit jobs are also hitting timeouts after 80 minutes more frequently recently: https://ci.eclipse.org/egit/job/egit.gerrit/buildTimeTrend
Comment 2 Mikaël Barbero CLA 2020-06-09 05:21:15 EDT
If you don't mind, I'll just close this one as a dup of bug 563645 as this is most probably due to the same root cause and will be fixed the same way. 

Feel free to reopen this one or another one if it happens again once bug 563645 is fixed.

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