geographiclib: Add unit testing

[FannoFlow1]

add unit testing to geographiclib builds

Specify library name and version: geographiclib/2.3

resolves #24172

• I've read the contributing guidelines.
• I've used a recent Conan client version close to the currently deployed.
• I've tried at least one configuration locally with the conan-center hook activated.

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 1 (ed06d3d72672c9ecb366ffe5f603f60caa9ecd4a):

• geographiclib/1.51:
  All packages built successfully! (All logs)

• geographiclib/2.3:
  All packages built successfully! (All logs)

• geographiclib/1.50.2:
  All packages built successfully! (All logs)

• geographiclib/1.52:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 1 (ed06d3d72672c9ecb366ffe5f603f60caa9ecd4a):

• geographiclib/2.3:
  All packages built successfully! (All logs)

• geographiclib/1.50.2:
  All packages built successfully! (All logs)

• geographiclib/1.51:
  All packages built successfully! (All logs)

• geographiclib/1.52:
  All packages built successfully! (All logs)

[jcar87]

Hi @FannoFlow1, thank you for your contribution.

We don't currently build or run tests during the package builds, in particular in our CI as the validity of the packages is a responsibility we place on the users who wish to test that. This is also in line with other package managers.

However let me check with the team, as it is still a useful feature that should be optional in the recipes.
We introduced the tools.build:skip_test configuration for this very purpose - this way the recipes could conditionally build and run tests.

[FannoFlow1]

Hi @FannoFlow1, thank you for your contribution.

We don't currently build or run tests during the package builds, in particular in our CI as the validity of the packages is a responsibility we place on the users who wish to test that. This is also in line with other package managers.

However let me check with the team, as it is still a useful feature that should be optional in the recipes. We introduced the tools.build:skip_test configuration for this very purpose - this way the recipes could conditionally build and run tests.

Ah interesting! For some reason I thought I was seeing unit tests in other packages being built, with this being an outlier. I must have been seeing something else in the logs since you're right the recipes I'm looking at don't run tests.

I think it would be very desirable to have cmake.test() in the conan center recipes which leverages the tools.build:skip_test property internally.

[FannoFlow1]

I would also argue it would be very important to run the unit tests with the conancenter index packages because there are so many compiler variables. The compiler settings the package author tested with might be (or likely are) different than the conan center index builds. And I'm not sure its a safe assumption to argue that those differences dont matter.
Now most probably dont have an affect on most packages, but I'm not sure you can guarantee that for all packages in all builds without running the unit tests. Especially if downstream users of those binaries are considering them pre-tested, but I'm not sure we can assume they've been pre-tested since the unit tests aren't running during the build process.

And same goes for the downstream user building from source. At best you'll get compiler / linker errors, at worst you have a silent runtime issue giving you the wrong answer on some math.

[perseoGI]

Hi @FannoFlow1!

Thank you for your interest in Conan Center Index.
Running unit tests is not a CCI policy so we are closing this PR because we can't find the value in deviating from it.

Nevertheless, thanks a lot for taking the time to open the PR, we appreciate it 🐸