drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5112) Unit tests derived from PopUnitTestBase fail in IDE due to config errors
Date Tue, 28 Mar 2017 18:28:42 GMT

    [ https://issues.apache.org/jira/browse/DRILL-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945681#comment-15945681

Paul Rogers commented on DRILL-5112:

This is a development issue that needs no QA verification.

> Unit tests derived from PopUnitTestBase fail in IDE due to config errors
> ------------------------------------------------------------------------
>                 Key: DRILL-5112
>                 URL: https://issues.apache.org/jira/browse/DRILL-5112
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.8.0
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>              Labels: ready-to-commit
>             Fix For: 1.10.0
> Drill provides a wide variety of unit tests. Many derive from {{PopUnitTestBase}} to
test the Physical OPerators.
> The tests use a default configuration:
> {code}
> protected static DrillConfig CONFIG;
>   @BeforeClass
>   public static void setup() {
>     CONFIG = DrillConfig.create();
>   }
> {code}
> The tests rely on config settings specified in the {{pom.xml}} file (see note below.)
When run in Eclipse, no such config exists, so the tests use only the default config. The
defaults allow a web server to be started.
> Many tests start multiple Drillbits using the above config. When this occurs, each tries
to start a web server. The second one fails because the HTTP port is already in use.
> The solution is to initialize the config using the same settings as used in the {{BaseTestQuery}}
test case: the unit tests then work fine in Eclipse.
> As an aside, having multiple ways to set up the Drill config (and other items) leads
to much wasted time as each engineer must learn the quirks of each test hierarchy.

This message was sent by Atlassian JIRA

View raw message