drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Westin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-2515) Add allocator state verification at the end of test suites
Date Fri, 26 Jun 2015 19:57:05 GMT

     [ https://issues.apache.org/jira/browse/DRILL-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Westin updated DRILL-2515:
--------------------------------
    Fix Version/s:     (was: 1.1.0)
                   1.3.0

> Add allocator state verification at the end of test suites
> ----------------------------------------------------------
>
>                 Key: DRILL-2515
>                 URL: https://issues.apache.org/jira/browse/DRILL-2515
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Tools, Build & Test
>    Affects Versions: 0.8.0
>            Reporter: Chris Westin
>            Assignee: Chris Westin
>             Fix For: 1.3.0
>
>
> In order to speed up testing, we've set up maven so that it reuses the JVM between test
classes in "mvn install". However, this means that if there are missing closures of allocators
or other resources, we don't find out until much later, after the offending test, instead
of in the test, as we would when running a JUnit test from an IDE.
> The suggestion here is to add @AfterClass methods to base test classes that do some kind
of verification. We'll need to add something to the top level allocator that does the same
verification it does now in close(), but allows us to spot check it between tests. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message