You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2017/10/26 10:06:00 UTC
[jira] [Comment Edited] (JENA-1407) Improvements to development
build
[ https://issues.apache.org/jira/browse/JENA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220261#comment-16220261 ]
Andy Seaborne edited comment on JENA-1407 at 10/26/17 10:05 AM:
----------------------------------------------------------------
Is there some way to improve the Elephas I/O testing where suites alternate being around 5 seconds and around 60-70 seconds per suite.
The accumulated effect of the 1 minute+ suite runs cost half the build time, but the system seems to be waiting for some kind of timeout. Very little CPU is being used.
was (Author: andy.seaborne):
Is there some way to improve the Elephas I/O testing where suites alternate being around 5 seconds and around 60-70 seconds per suite.
The accumulated effect of the 1 minute+ suite runs cost half the build time.
> Improvements to development build
> ---------------------------------
>
> Key: JENA-1407
> URL: https://issues.apache.org/jira/browse/JENA-1407
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Priority: Minor
>
> We have {{-Pdev}} for a build that tests the main parts of Jena up to jena-fuseki2 to speed up testing for changes. It omits jena-iri and jena-shaded-guava and can fail if run when the build picks up snapshots built by Jenkins. We also have {{-Pbootstrap}} which includes these.
> Proposal:
> # Have one profile, which builds everything up to jena-fuseki2.
> # Don't build the javadoc (for speed reasons).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)