tests fail if not cloned as a git repo
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 182
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Pkg.test fails: e.g. https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_date/2021-02/21/Coverage.1.7.0-DEV-d524f21917.log
Testing Running tests...
┌ Warning: skipping local repo tests for Codecov, since not a git repo
└ @ Main ~/.julia/packages/Coverage/3V3Eo/test/runtests.jl:106
coveralls: Error During Test at /Users/jameson/.julia/packages/Coverage/3V3Eo/test/runtests.jl:430
Got exception outside of a @test
GitError(Code:ENOTFOUND, Class:Repository, could not find repository from '/Users/jameson/.julia/packages/Coverage/3V3Eo/test')
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 with test/runtests.jl, especially the checks around lines 106 and 430, and reproduce the failure by running Pkg.test from a checkout that is not a Git repository. Trace why the Coveralls test still calls Git repository detection after the Codecov test is skipped. Done means the test suite no longer raises GitError in that setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100