JanusGraph / JanusGraph/janusgraph
Flaky index test: indexShouldNotExistAfterDeletion
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
## Flaky Test
* **Test Name:** BerkeleyElasticsearchTest.indexShouldNotExistAfterDeletion
* **Link:** https://github.com/JanusGraph/janusgraph/blob/e2b0bed82f95817f2656606ce2a62225aed2a9f0/janusgraph-es/src/test/java/org/janusgraph/diskstorage/es/ElasticsearchJanusGraphIndexTest.java#L81
* **Branch:** master
* **Notes:**
### Stack Trace
```
Error: Failures:
Error: BerkeleyElasticsearchTest>ElasticsearchJanusGraphIndexTest.indexShouldNotExistAfterDeletion:98->JanusGraphIndexTest.registerIndex:3943 expected: but was:
```
Contributor guide
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
Start with ElasticsearchJanusGraphIndexTest.java at the referenced test and inspect the failure at line 98 through JanusGraphIndexTest.registerIndex. Reproduce BerkeleyElasticsearchTest.indexShouldNotExistAfterDeletion and determine why registration reports false after deletion. Done means the test reliably passes and verifies that the index does not exist after deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, java
- Domain
- databases, search, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100