NVIDIA-NeMo / NVIDIA-NeMo/Curator
Investigate flaky CI test
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 328
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 30
Description
Describe the bug
A specific test: tests/stages/test_base.py::TestProcessingStageWith::test_with_method_thread_safety has failed a couple of times in different CI runs:
https://github.com/NVIDIA-NeMo/Curator/actions/runs/18110619087/job/51537937094?pr=1140
https://github.com/NVIDIA-NeMo/Curator/pull/1126#issuecomment-3340182026
Need to investigate whether the test is valid and still needs to be tested (possibly modified) or if it can be removed.
Steps/Code to reproduce bug
Expected behavior
Additional context
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 tests/stages/test_base.py::TestProcessingStageWith::test_with_method_thread_safety and review the linked CI run and pull-request comment for the reported failures. Run the focused test to reproduce or assess the flakiness. Done means deciding whether the test remains valid, then modifying it or removing it as appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100