Thomas,
Though I can't understand why, I'm getting different results from
running "TestAll.java" from Eclipse and from running it on the command
line. I've checked three times, and the JVM that Eclipse is set to use
is the same as my default JVM (Sun's 1.6 JVM). When I run TestAll.java
on code taken directly from SVN, the following tests all fail:
-TestOutOfMemory (runs indefinitely)
-TestKillRestart and TestKillRestartMulti (
-TestExit (NoClassDefFoundError exception?)
-TestSampleApps ("FileNotFoundException: src/test/org/h2/samples/
optimizations.sql", but the file is definitely sitting there in that
path)
I've decided that I am cursed and will never get a working environment
set up. However, I've faked my way through it by commenting out those
particular tests. As long as those tests aren't run, TestAll.java
works great, both on SVN code and on my code. It appears my only
option is to submit patches to you with the caveat that I am incapable
of running those particular tests. However, the test cases I added
guarantee 100% coverage of code I changed, and the code changes I made
shouldn't be anywhere near the stuff that those tests are checking.
Besides that hiccup, everything else seems to be fine -- I was able to
run all other tests, spellchecks, etc. Do you still want me to submit
my patches in spite of the fact that I could not run the tests
specified above?
-Evan
On Feb 26, 1:19 pm, Thomas Mueller <[email protected]>
wrote:
> Hi,
>
> > 1) I currently have all of my changes in different sets of code (in
> > other words, I'd be submitting a different patch for each of the above
> > changes). Does it make more sense to combine all my changes into one
> > patch instead? (It seems like it wouldn't, but I want to be sure).
>
> No, separate patches is better.
>
> > 2) When I run TestAll.java from Eclipse, the program freezes
> > indefinitely on TestOutOfMemory.java. This happens when I run it on
> > the code checked out from SVN or on code with my changes. Any idea
> > what's happening? (I'm running a Ubuntu Linux operating system,
> > perhaps the Linux JVM handles memory differently than the test is
> > expecting) Commenting out the line to run TestOutOfMemory.java lets
> > the test proceed just fine.
> > 3) Similarly, when I run "./build.sh test", it freezes indefinitely.
>
> What JVM do you use? I believe there could be some problems with the
> Kaffee JVM or GCJ. I use the Sun JVM on Ubuntu, it's much faster and
> much more stable.
>
> If it's not the JDK, then could you create a few full thread dumps
> please? I usually use jps / jstack to do that.
>
> > 4) Running "./build.sh spellcheck" produces the following error:
> > Exception in thread "main" java.lang.Error: java.io.IOException:
> > Unsupported suffix: project for file: /h2database/h2/src/.project
>
> I have the project file outside of the src folder, that is in
> /h2database/h2. I suggest to do the same.
>
> Regards,
> Thomas
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en
-~----------~----~----~----~------~----~------~--~---
