-
Notifications
You must be signed in to change notification settings - Fork 872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue on direct memory allocation in scala+sbt environment #7641
Comments
@tglman Thanks! I was not very precise describing my error. Sorry for that. This is the error I get:
I am running:
|
hi @fixundfertig123 , I actually got a different error first, that we are checking, after we will check also this case. Regards |
@tglman could you try again on the latest source? |
hi @fixundfertig123, I've been able to fix the first problem I had and reproduce the schema issue, I'm debugging to find out the cause of that problem and provide a fix. Regards |
Hi @fixundfertig123, The root problem is the auto-creation of the database in concurrent way, this is not supported out of the box in 2.2.x, so probably the best way is to do a "before" operation that guarantee that the database exists before the tests run, in remote you don't have a problem because the database is required to exists in that case. Regards |
Hi @tglman, thank you for your effort!!! To be honest, I am not quite sure whether I get your point. Assuming that you are referencing to the "BeforeAndAfter" traits I tried to work with that. For some reason on the new code I now get some memory exceptions I assume you fixed:
So we have some points open:
Best regards |
hi @fixundfertig123, The fix is already landed in the 2.2.x branch so it will be released with 2.2.27 in a couple of weeks, if you want to do some early try you can get the I'm not an expert on how to write MT tests in scala+sbt, but is enough to have a:
before your current code start in MT. Regards |
Hi @tglman, To make other save some time, I uploaded the running code at my repo: https://github.com/fixundfertig123/7547/releases/tag/WorkingTestSuite I think crucial was changing the test suite into an object rather than a class. This hopefully helps some people and you if you recieve other SBT / SCALA / Testsuite questions. Thanks for you effort! |
hi @fixundfertig123, Good to know you solved, can we close this ? Regards |
@tglman yes, and thanks |
OrientDB Version: 2.2.25 2.2.26-SNAPSHOT
Java Version: java 8
OS: Debian
Expected behavior
Test case: https://github.com/fixundfertig123/7547/blob/InMemoryErrorFlatSpec/src/test/scala/Test.scala goes smooth
Actual behavior
Out Of Memory on Direct Memory allocation
Steps to reproduce
Checkout the project https://github.com/fixundfertig123/7547 on the branch https://github.com/fixundfertig123/7547/tree/InMemoryErrorFlatSpec and run
sbt clean
+sbt compile
+sbt test
from previous debug session the issue seems to come from a allocation size calculation issue:
The text was updated successfully, but these errors were encountered: