influxdata / influxdata/influxdb-java
question of test case: precision()
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 469
- PR merge metrics
- No merged PRs in 30d
Description
hello, i test the case precision() in src/test/java/org/influxdb/impl/BatchProcessorTest.java
it should execute like below:
1. CREATE DATABASE "write_unittest_1659064333553"
2. CREATE RETENTION POLICY somePolicy ON write_unittest_1659064333553 DURATION 30h REPLICATION 2 DEFAULT
3. POST /write?db=write_unittest_1659064333553&rp=somePolicy&precision=s&consistency=one the point
4. DROP DATABASE "write_unittest_1659064333553"'
but, actually it execute look like image below
the drop action before the write action!
i don't know it is my fault or the case has some problem?
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
Start with src/test/java/org/influxdb/impl/BatchProcessorTest.java and run the precision() test to inspect the observed ordering of database creation, write, and drop actions. Compare the test's expected sequence with the actual execution shown in the issue; done means determining whether the ordering comes from the test case or the client behavior and documenting the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100