[
https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638296#comment-16638296
]
Rick Hillegas commented on DERBY-7011:
--------------------------------------
The first run of the new Jenkins task failed because the test run timed out:
https://builds.apache.org/blue/organizations/jenkins/Derby-trunk-test-junit-all-with-modulepath/detail/Derby-trunk-test-junit-all-with-modulepath/1/artifacts/
I have increased the timeout limit from 400 to 500 minutes to see if this lets
the task run to completion.
> Set up a new Jenkins job to run the JUnit tests with a module path
> ------------------------------------------------------------------
>
> Key: DERBY-7011
> URL: https://issues.apache.org/jira/browse/DERBY-7011
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.15.0.0
> Reporter: Rick Hillegas
> Priority: Major
>
> I have set up a new Jenkins job (Derby-trunk-test-junit-all-with-modulepath)
> to run the JUnit tests with a module path. This issue is a place to collect
> feedback on how to finish setting up this job.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
