Unit tests aren't all passing.
Open
Nobody has claimed this yet.
bug
testing
- Dominant language
- C++
- Stars
- 10
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
We have some work in flight, and are still reviving polytope, so this is understandable. But when we start using Travis CI to vet pull requests, we need all of our tests to pass. This issue represents that goal.
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 reviewing the repository's unit-test failures and the work already in flight around reviving polytope. The issue is done when all unit tests pass and Travis CI can vet pull requests successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100