Coverage CI
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- c, github-actions
- Domain
- ci-cd, testing-qa
Research direction
Start with .github/workflows/benchmark.yml and the existing coverage target, then review the coverage-related results in the linked repository code search. Define the supported platforms and baseline threshold before implementing publishing and failure checks. Done means coverage is published, the threshold is enforced, and the dlopen-related coverage behavior has been reviewed.
Written by the indexing model from the issue text.
Description
🚀 Feature
We need a coverage CI like this one: https://github.com/metacall/core/blob/develop/.github/workflows/benchmark.yml
But for publishing the coverage information.
Right now we already support the coverage target but it's not being published anywhere, and I think it's only supported in Linux, it may be interesting if it can be extended to Windows and MacOS and then published.
Ut will be also interesting to make it fail if the % of the coverage goes lower than the current baseline. For example 60% covered.
Apart from that, I think the current implementation may be buggy due to dlopen mechanism we use on the plugins, we should review that in depth.
For more information check this out: https://github.com/search?q=repo%3Ametacall%2Fcore+coverage&type=code
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 266
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 14
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from metacall/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
metacall/core#964 · 1 comment ·
Maintainers usually reply within 1 day
-
pre-push hook empties VERSION when the clone has no tagsPossibly taken @vedant21-oss claimed this 18 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
metacall/core#939 · 3 comments ·
Maintainers usually reply within 1 day
-
TOCTOU race condition vulnerability!Possibly taken @akshatchitransh claimed this 1 day ago. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
metacall/core#961 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 Half a day Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Go Port Race Conditions on MacOSPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
metacall/core#942 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
`table_create()` crashes when an `hccalloc()` for the option table failsPossibly taken @marinelay claimed this today. Opentype: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AlessandroSangiuliano/Uros#950 ·
-
ESP32
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
HandBrake/HandBrake#8266 · 1 comment ·
Maintainers usually reply within 1 day