Revisit LS372 integration tests
Open
Nobody has claimed this yet.
agent: ls372
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
They were dropped for being randomly flaky, but once https://github.com/simonsobs/socs/pull/775 is merged it might be worth revisiting them, perhaps reverting https://github.com/simonsobs/socs/commit/4038404a2269a51a87d1dfbb6ca85684f5fe0e22.
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 reviewing pull request 775 and commit 4038404a2269a51a87d1dfbb6ca85684f5fe0e22 to understand why the LS372 integration tests were dropped and what may change after the pull request is merged. Done means the tests have been revisited and either restored with reliable results or their continued exclusion is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100