JanusGraph / JanusGraph/janusgraph
Flaky HBase OLAP test: testVertexPartitionOlapCluster
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:** HBasePartitionGraphTest.testVertexPartitionOlapCluster
* **Link:** https://github.com/JanusGraph/janusgraph/blob/13619a181b7a64004a886223270d003dfdcbb4a0/janusgraph-backend-testutils/src/main/java/org/janusgraph/graphdb/JanusGraphPartitionGraphTest.java#L397
* **Branch:** master
* **Notes:**
### Stack Trace
```
Error: Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 128.7 s <<< FAILURE! -- in org.janusgraph.graphdb.hbase.HBasePartitionGraphTest
Error: org.janusgraph.graphdb.hbase.HBasePartitionGraphTest.testVertexPartitionOlapCluster -- Time elapsed: 4.350 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <1> but was: <0>
at org.janusgraph.graphdb.JanusGraphPartitionGraphTest.testVertexPartitionOlap(JanusGraphPartitionGraphTest.java:443)
at org.janusgraph.graphdb.JanusGraphPartitionGraphTest.testVertexPartitionOlapCluster(JanusGraphPartitionGraphTest.java:398)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
[INFO]
[INFO] Results:
[INFO]
Error: Failures:
Error: HBasePartitionGraphTest>JanusGraphPartitionGraphTest.testVertexPartitionOlapCluster:398->JanusGraphPartitionGraphTest.testVertexPartitionOlap:443 expected: <1> but was: <0>
```
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 JanusGraphPartitionGraphTest.testVertexPartitionOlapCluster at line 398 and the testVertexPartitionOlap assertion at line 443, then run the HBasePartitionGraphTest to reproduce the failure. Investigate why the assertion intermittently observes 0 instead of 1; done means the test passes reliably without masking the reported condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100