microsoft / microsoft/pg_durable
Database state leak across e2e tests seems possible
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.8k
- Forks
- 80
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 32
Description
This can make tests flaky, e.g. a GRANT in one test can apply to a later test, meaning if the later test is missing a GRANT, then the later test will pass in some scenarios and not others. I don't know if this happens in all cases, or just in certain ones, so I think it needs a bit of investigation. It's not that big of a deal, but is somewhat annoying. I just wanted to note it down, since it could become an issue later (if this fails to get detected in CI, and we land a flakey test, it would be annoying).
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
No files or specific tests are named. Start with the e2e test suite and investigate whether a GRANT in one test affects later tests through shared database state. Done means determining when the leak occurs and documenting or addressing the isolation needed to prevent flaky test results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, rust
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100