Chris Westin wrote:
Variability: for me so far 2 out of 2 times.
No stack trace, but as above, when I try to reproduce it in an IDE
"This seems to be because the test is getting an ExceptionInInitializer in
DrillbitClassLoader because the app.class.path property isn't set (and then
the resulting String.length() on its value throws an NPE)."
Yes, I just ran into that today too, trying to run it in an IDE (Eclipse).
I don't see app.class.path set anywhere in any pom.xml (so it's not getting
set when I copy the surefire arguments into the IDE's launch configuration
for the test, either).
It does seem to be set by something in the JDBC-all POM file, but not
directly--there's some embedded Ant script getting the value from
somewhere else.)
Daniel
On Tue, Sep 15, 2015 at 9:09 PM, Jacques Nadeau <[email protected]> wrote:
It was tested on a clean machine a number of times. Any thoughts on the
variability? Can you provide stack trace?
On Sep 15, 2015 6:28 PM, "Sudheesh Katkam" <[email protected]> wrote:
Yes, I see this issue too.
On Sep 15, 2015, at 5:53 PM, Chris Westin <[email protected]>
wrote:
This seems to be because the test is getting an ExceptionInInitializer
in
DrillbitClassLoader because the app.class.path property isn't set (and
then
the resulting String.length() on its value throws an NPE).
Bueller?
On Tue, Sep 15, 2015 at 5:20 PM, Chris Westin <[email protected]
wrote:
I just rebased, and twice in a row I've gotten wedged running
org.apache.drill.jdbc.ITTestShadedJar
--
Daniel Barclay
MapR Technologies
