You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2018/11/30 15:51:00 UTC

[jira] [Commented] (DERBY-7011) Set up a new Jenkins job to run the JUnit tests with a module path

    [ https://issues.apache.org/jira/browse/DERBY-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704943#comment-16704943 ] 

Rick Hillegas commented on DERBY-7011:
--------------------------------------

The modulepath junit tests are still failing and they timeout before producing any error output: https://builds.apache.org/blue/organizations/jenkins/Derby-trunk-test-junit-all-with-modulepath/detail/Derby-trunk-test-junit-all-with-modulepath/8/changes/ The tests were aborted after running for more than 8 hours. I will try to short-circuit the tests when they run on the jenkins machines using the modulepath so that we can at least get some preliminary error information.

> 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)