SPTAGTest fatal error
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5k
- Forks
- 622
- Avg merge
- 8h 37m
- Merged PRs (30d)
- 5
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Build and run SPTAGTest with the documented Docker commands, then reproduce the crash in SSDServingTest/TestHeadUInt8L2DEFAULT. Inspect the checkpoint at /app/Test/src/SSDServingTest.cpp line 444 and compare the SIGSEGV with the invalid stdio handle failure; done means the test completes without either fatal error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- search, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100