ci: Check that the `geos` installation produces a usable library and runtime
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 287
- Forks
- 109
- Avg merge
- 4d 41m
- Merged PRs (30d)
- 5
Description
What is the requested feature?
The integration of the PR #3282 has broken the non-regression tests of Pangea3 (see issue #3305) due to a missing installation of shared libraries (see fix #3307).
It is a blind spot in the current ci: it should be tested somewhere that we can successfully use the ci installation.
Describe the solution you'd like
One or few very fast tests have to execute the geos runtime produced in the install directory (and maybe after removing the build directory).
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 with the CI installation step that produces the geos runtime and inspect how its install directory is used after installation. Add one or a few fast checks that execute the installed runtime, including after the build directory is removed, and confirm the shared libraries are available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100