Skip to content
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

Test fails on mingwX64 #24

Closed
BenWoodworth opened this issue Mar 12, 2023 · 2 comments
Closed

Test fails on mingwX64 #24

BenWoodworth opened this issue Mar 12, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@BenWoodworth
Copy link
Owner

BinaryNbtReaderTest.should_decode_to_class_correctly:

> Task :mingwX64ProcessResources NO-SOURCE
> Task :mingwX64MainKlibrary
> Task :compileTestKotlinMingwX64
> Task :linkDebugTestMingwX64

Expiring Daemon because JVM heap space is exhausted
Daemon will be stopped at the end of the build after running out of JVM memory
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted

> Task :mingwX64Test FAILED

35 tests completed, 1 failed

net.benwoodworth.knbt.internal.BinaryNbtReaderTest.should_decode_to_class_correctly FAILED
    Unknown

4 actionable tasks: 4 executed
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':mingwX64Test'.
> Test running process exited unexpectedly.
  Current test: should_decode_to_class_correctly


* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org/

BUILD FAILED in 4m
Error: Process completed with exit code 1.
@BenWoodworth BenWoodworth changed the title Test fails on mingwX64: BinaryNbtReaderTest.should_decode_to_class_correctly Test fails on mingwX64 Mar 12, 2023
@BenWoodworth
Copy link
Owner Author

Crashing on the first call to free (plus the other calls if I comment the earlier ones out):

free(strm.ptr)
free(inbuf)
free(outbuf)

BenWoodworth added a commit that referenced this issue Mar 12, 2023
Fixes #24

In mingwX64 the free calls were causing the execution to crash. This seems to fix the issue, and might make sense since the variables being freed are being instantiated with `nativeHeap.alloc()` instead of just `alloc()`
@BenWoodworth
Copy link
Owner Author

Pipeline passed for mingw :)

@BenWoodworth BenWoodworth added the bug Something isn't working label Mar 12, 2023
BenWoodworth added a commit that referenced this issue Mar 21, 2024
Fixes #24

In mingwX64 the free calls were causing the execution to crash. This seems to fix the issue, and might make sense since the variables being freed are being instantiated with `nativeHeap.alloc()` instead of just `alloc()`
BenWoodworth added a commit that referenced this issue Mar 22, 2024
Fixes #24

In mingwX64 the free calls were causing the execution to crash. This seems to fix the issue, and might make sense since the variables being freed are being instantiated with `nativeHeap.alloc()` instead of just `alloc()`
BenWoodworth added a commit that referenced this issue Mar 22, 2024
Fixes #24

In mingwX64 the free calls were causing the execution to crash. This seems to fix the issue, and might make sense since the variables being freed are being instantiated with `nativeHeap.alloc()` instead of just `alloc()`
BenWoodworth added a commit that referenced this issue Mar 22, 2024
Fixes #24

In mingwX64 the free calls were causing the execution to crash. This seems to fix the issue, and might make sense since the variables being freed are being instantiated with `nativeHeap.alloc()` instead of just `alloc()`
BenWoodworth added a commit that referenced this issue Mar 27, 2024
Fixes #24

In mingwX64 the free calls were causing the execution to crash. This seems to fix the issue, and might make sense since the variables being freed are being instantiated with `nativeHeap.alloc()` instead of just `alloc()`
BenWoodworth added a commit that referenced this issue Mar 27, 2024
Fixes #24

In mingwX64 the free calls were causing the execution to crash. This seems to fix the issue, and might make sense since the variables being freed are being instantiated with `nativeHeap.alloc()` instead of just `alloc()`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant