db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (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 03:55:00 GMT

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

Bryan Pendleton commented on DERBY-7011:
----------------------------------------

To make sure I understand: these tests appear to run fine when you run them on your MacBook.

But when you run what you think is the exact same set of tests on one of our Jenkins worker
machines, they hang and misbehave and aren't giving you any useful diagnostics about where
things are going wrong?

> 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