Lightning-AI / Lightning-AI/lightning-thunder
Flaky code coverage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
Seems like code coverage can cause CI failures like:
```
Wrote XML report to coverage.xml
+ ./codecov --token=*** --commit=5efa041b7c2b6f256bf1571a043d58267faaf3e1 --flags=gpu,pytest,networks --name=GPU-coverage --env=linux,azure
/__w/_temp/b50911ff-a252-4a97-8003-3fbfbb5d1ac2.sh: line 14: ./codecov: No such file or directory
##[error]Bash exited with code '127'.
```
See https://dev.azure.com/Lightning-AI/72ab7ed8-b00f-4b6e-b131-3388f7ffafa7/_apis/build/builds/221986/logs/43 for an example.
I'm not sure what these code coverage reports do. Maybe we should remove them, or not fail the CI if they fail?
cc @borda
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 by locating the Azure CI step that writes coverage.xml and invokes ./codecov, then compare it with the linked build log. Determine whether the missing codecov executable is expected and establish the intended behavior when coverage reporting fails; done should mean the affected CI job no longer fails unexpectedly and coverage behavior is documented by a test or CI check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100