We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug [1] BKTKmeansK: 3, BKTLeafSize: 6, Samples: 100, BKTLambdaFactor:-1.000000 TreeNumber: 1, ThreadNum: 2. unknown location(0): fatal error: in "SSDServingTest/TestHeadUInt8L2DEFAULT": signal: SIGSEGV, si_code: 0 (memory access violation at address: 0x00000080) /app/Test/src/SSDServingTest.cpp(444): last checkpoint: "TestHeadUInt8L2DEFAULT" test entry
*** 1 failure is detected in the test module "Main"
Re-run the test and get another error
[1] BKTKmeansK: 3, BKTLeafSize: 6, Samples: 100, BKTLambdaFactor:-1.000000 TreeNumber: 1, ThreadNum: 2. Fatal error: glibc detected an invalid stdio handle Aborted
To Reproduce x86_64 GNU/Linux Host OS: Ubuntu 18.04.6 LTS
docker build -t sptag .
docker run sptag:latest ./Release/SPTAGTest
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
[1] BKTKmeansK: 3, BKTLeafSize: 6, Samples: 100, BKTLambdaFactor:-1.000000 TreeNumber: 1, ThreadNum: 2.
unknown location(0): fatal error: in "SSDServingTest/TestHeadUInt8L2DEFAULT": signal: SIGSEGV, si_code: 0 (memory access violation at address: 0x00000080)
/app/Test/src/SSDServingTest.cpp(444): last checkpoint: "TestHeadUInt8L2DEFAULT" test entry
*** 1 failure is detected in the test module "Main"
Re-run the test and get another error
[1] BKTKmeansK: 3, BKTLeafSize: 6, Samples: 100, BKTLambdaFactor:-1.000000 TreeNumber: 1, ThreadNum: 2.
Fatal error: glibc detected an invalid stdio handle
Aborted
To Reproduce
x86_64 GNU/Linux
Host OS: Ubuntu 18.04.6 LTS
docker build -t sptag .
docker run sptag:latest ./Release/SPTAGTest
The text was updated successfully, but these errors were encountered: