Thank you for your help.
To review, this command works and succeeds:
mvn clean install -DskipTests=true
mvn test ... with args per your prior email...
fails with the "drill-java-exec: Artifact has not been packaged yet..."
error.
On Fri, Aug 25, 2023 at 3:54 AM James Turton wrote:
> Okay,
Okay, that attempt couldn't even build java-exec. What does the
following do when run from the root of the source tree?"
mvn package -f exec/vector/pom.xml
mvn package -f exec/java-exec/pom.xml
On 2023/08/24 17:09, Mike Beckerle wrote:
Still no luck.
Output from your mvn-test-drill command
Still no luck.
Output from your mvn-test-drill command is attached.
drill-java-exec: Artifact has not been packaged yet.
On Mon, Aug 21, 2023 at 10:36 AM James Turton wrote:
> Hi Mike
>
> I took a look at the build log that you shared with me recently and what
> happened in that run was
Hi Mike
I took a look at the build log that you shared with me recently and what
happened in that run was OOM (first report on line 9348).
| 9355 2198813 ERROR [UserServer-1]
[org.apache.drill.exec.rpc.RpcExceptionHandler] - Exception in RPC
communication. 9355 Connection:
Charles,
fixed your testComplexXSD in your xsd_reader branch.
https://github.com/cgivre/drill/pull/5
Need to add attribute support, but this is quite close.
On Fri, Jul 14, 2023 at 5:59 PM Charles Givre wrote:
> Hi Mike,
> One more thing... I've been working on an XSD Reader for Drill for
Figured out my own issue. This --add-opens is a java 9+ thing. I'll switch
from Java 8 to Java 11.
On Mon, Jul 24, 2023 at 7:07 PM Mike Beckerle wrote:
> Charles,
>
> When you say this is close to working what is the expected behavior of
> the code currently.
> I could debug into this, but
Hmm... Ok.. that's not what's happening on my machine. On my box, the simple
unit tests are passing. The complex ones are still missing some levels of
nesting. But mine will build w/o errors.
What Java version are you using?
-- C
> On Jul 24, 2023, at 7:07 PM, Mike Beckerle wrote:
>
>
Charles,
When you say this is close to working what is the expected behavior of
the code currently.
I could debug into this, but I'm frankly unable to get anything to run.
Currently when I try to run just one test: TestXSDSchema:testSimpleXSD(), I
get the below giant message, to cut to the
Hi drill devs,
I'm still stuck on this problem. Can anyone suggest a way past this?
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
On Mon, Jul 17, 2023 at 9:53 AM
That looks like a great start at what we will need for DFDL.
I will study what you've done carefully and get back to you with questions.
On Fri, Jul 14, 2023 at 5:59 PM Charles Givre wrote:
> Hi Mike,
> One more thing... I've been working on an XSD Reader for Drill for some
> time. (This is
Hi Mike,
One more thing... I've been working on an XSD Reader for Drill for some time.
(This is still very buggy) https://github.com/cgivre/drill/tree/xsd_reader
What this does is attempt to convert a XML XSD file into a Drill Schema.
Best,
-- C
> On Jul 14, 2023, at 2:20 PM, Charles
Mike,
Are you able to build Drill w/o the tests? If so, my suggestion is really just
to start working on the DFDL extensions. I've been doing Drill stuff for far
too long and really haven't needed to run the full battery of unit tests
locally. As long as you can build it and can execute
Update: I did a clean and install -DskipTests=true.
Then I tried the mvn test using the non-UTC timezone stuff, as suggested.
But alas, it still fails, this time the failure unique and is only in "Java
Execution Engine"
[ERROR] Failed to execute goal
Hi Mike,
You can just build Drill with the -DskipTests = true option and that should
work. I do my development in intellij, and just run the relevant unit
tests there. Then to test Drill in its entirety, I'll use the CI in github
which works most of the time. ;-)
-- C
On Thu, Jul 13, 2023 at
To answer questions:
1. Paul: This is a 100% stock build. All I have done is clone the repo
(master branch). Make a new git branch (in case I make future changes). Try
to build (success) and test (failed so far).
2. James: The /opt/drill directory I created is owned by my userid and has
full
I'll add some heresy here... IMHO, for the purposes of developing a DFDL
extension, you probably don't need all the Drill tests to run. For your
project, my suggestion would be to add a module to the contrib package and that
way your changes are relatively self contained.
Best,
-- C
> On
Hi Mike
Here's the command line I use to run tests on a machine that's not in
the UTC time zone (plus some unrelated memory size arguments).
mvn test -Djunit.args="-Duser.timezone=UTC -Duser.language=en
-Duser.region=US" -DmemoryMb=2560 -DdirectMemoryMb=2560
I have one other question to
Hi Mike,
A quick glance at the log suggests a failure in the tests for the JSON
reader, in the Mongo extended types. Drill's date/time support has
historically been fragile. Some tests only work if your machine is set to
use the UTC time zone (or Java is told to pretend that the time is UTC.)
The
18 matches
Mail list logo
