[
https://issues.apache.org/jira/browse/GIRAPH-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan Kumar resolved GIRAPH-917.
--------------------------------
Resolution: Fixed
Assignee: Pavan Kumar
seems that the build is now taking 41 minutes, so the 30 minute timeout cause
all builds from Mar 18th to get aborted.
Thanks [~aching] for changing time out to 60 minutes. The first successful
build after a long time is here : [yay]
https://builds.apache.org/job/Giraph-trunk-Commit/1461/ [I triggered it]
Build status:
https://builds.apache.org/job/Giraph-trunk-Commit/
> Every commit is followed by ABORTED: Integrated in Giraph-trunk-Commit
> ----------------------------------------------------------------------
>
> Key: GIRAPH-917
> URL: https://issues.apache.org/jira/browse/GIRAPH-917
> Project: Giraph
> Issue Type: Task
> Reporter: Pavan Kumar
> Assignee: Pavan Kumar
>
> Currently, every continuous build is aborted, because it is taking too long.
> Shouldn't we reduce the testing time so we can be with in the time limit or
> have a way to increase the time limits.
> Would be great if some one from PMC can take a look. This issue has been
> bugging us for very long now. Continuous build has become useless in
> verifying correctness of commit because of this issue.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
