pingcap / pingcap/tidb-operator
Collecting logs for each serial e2e case
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem? Please describe:
Currently, we can't get the logs (especially from operator) after each serial e2e test. This is hard to debug when e2e failed in serial cases.
Describe the feature you'd like:
We can get operator contaioner logs in each serial test case.
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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 by locating the serial end-to-end test harness and the code that manages the operator container. Trace how each test case currently handles logs, then verify that operator container logs are available separately after every serial case, including failed cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100