Ctest failed
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 6.5k
- Forks
- 627
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 6
Description
I'm getting below example of errors
124 - testH3NeighborRotations_test124 (Not Run)
125 - testH3NeighborRotations_test125 (Not Run)
126 - testDirectedEdgeExhaustive_test126 (Not Run)
127 - testVertexExhaustive_test127 (Not Run)
128 - testCellToLocalIjExhaustive_test128 (Not Run)
129 - testGridPathCellsExhaustive_test129 (Not Run)
130 - testGridDistanceExhaustive_test130 (Not Run)
131 - testH3CellAreaExhaustive_test131 (Not Run)
132 - testCliCellToLatLng_test131 (Not Run)
133 - testCliLatLngToCell_test131 (Not Run)
134 - testH3Memory_test132 (Not Run)
Errors while running CTest
Output from these tests are in: E:/New folder/my-h3/h3/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
Contributor 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.
Research direction
Start by reading E:/New folder/my-h3/h3/build/Testing/Temporary/LastTest.log, then rerun the failed cases with CTest's --rerun-failed --output-on-failure options. Determine why tests 124–134 are marked Not Run and confirm that the affected CTest run completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100