db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-7011) Set up a new Jenkins job to run the JUnit tests with a module path
Date Sat, 01 Dec 2018 16:33:00 GMT

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

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

Yes, that's right. But the short-circuited tests ran fine last night. I will gradually increase
the size of the short-circuited suite to see if I can tickle this bug. In case there is a
platform-related issue, I have logged DERBY-7021 to make sure that I run the module tests
on Linux and Windows. If you have some spare cycles, it would be helpful if you could run
the module tests on any platforms you have handy. Thanks.

> 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
>         Attachments: derby-7011-01-aa-shortCircuitAfterDerbyNetSuite.diff
>
>
> 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)

Mime
View raw message