[CI Broken] Wrong package name in coverage configuration

Open Beginner friendly
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
65/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
github-actions, python
Domain
ci-cd, devops

Research direction

Start with .github/workflows/CI.yml line 37, then compare the package name against setup.py and tox.ini. Verify that the coverage command targets juliatorch and that the workflow configuration remains valid; the issue provides the exact affected command and expected result.

Written by the indexing model from the issue text.

Description

Summary

The CI workflow configuration contains an incorrect package name in the coverage command, which would cause CI failures when coverage reports are generated.

Problem

In .github/workflows/CI.yml line 37, the tox command specifies:

run: python -m tox -- --cov=diffeqpy -s

This references diffeqpy instead of the correct package name juliatorch. This appears to be a copy-paste error from another SciML project.

Evidence

The package name is clearly defined as juliatorch in:

  • setup.py line 7: name='juliatorch'
  • setup.py line 23: packages=['juliatorch','juliatorch.tests']
  • tox.ini line 7: --pyargs juliatorch

Impact

This bug would cause coverage reporting to fail or report incorrect coverage metrics, potentially allowing bugs to slip through CI checks.

Suggested Fix

Change line 37 in .github/workflows/CI.yml from:

run: python -m tox -- --cov=diffeqpy -s

To:

run: python -m tox -- --cov=juliatorch -s

Additional Context

This issue was discovered during an automated CI health check. The repository hasn't had commits since October 2023, so there are no recent workflow runs visible to verify current CI behavior (GitHub Actions has a 90-day retention policy for workflow runs).

@ChrisRackauckas

Dominant language
Python
Stars
5
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SciML/juliatorch

All issues in SciML/juliatorch

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.