Update requirements

[jngrad]

Increase requirements of CMake, boost, Cython and Python, as discussed in es meeting 2019-11-26.

Closes #3090, Partial fix for #3093

Depends on espressomd/docker#149

[codecov]

Codecov Report

Merging #3375 into python will increase coverage by <1%.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           python   #3375    +/-   ##
=======================================
+ Coverage      86%     86%   +<1%     
=======================================
  Files         537     538     +1     
  Lines       25282   25306    +24     
=======================================
+ Hits        21806   21827    +21     
- Misses       3476    3479     +3

Impacted Files	Coverage Δ
src/core/io/writer/h5md_core.cpp	89% <ø> (ø)	⬆️
src/core/MpiCallbacks.hpp	97% <ø> (ø)	⬆️
...rc/utils/include/utils/math/triangle_functions.hpp	91% <ø> (ø)	⬆️
src/core/accumulators/Correlator.cpp	56% <ø> (ø)	⬆️
src/core/observables/ParticleBodyVelocities.hpp	100% <100%> (ø)	⬆️
src/core/observables/ParticleAngularVelocities.hpp	100% <100%> (ø)	⬆️
...core/observables/ParticleBodyAngularVelocities.hpp	100% <100%> (ø)	⬆️
src/core/domain_decomposition.cpp	94% <100%> (ø)	⬆️
src/core/observables/ComForce.hpp	100% <100%> (ø)	⬆️
src/core/domain_decomposition.hpp	100% <100%> (ø)	⬆️
... and 4 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a6deb15...65e5e6b. Read the comment docs.

[KaiSzuttor]

why do you want to remove this test?

[jngrad]

Here's how I understood our last es meeting:

• we don't test boost 1.55 any more
• boost 1.58 is already tested in cuda:9.0 and clang:6.0
• once Ubuntu 20.04 LTS is released next April, we upgrade boost requirements to 1.65 (for cuda:9.0 which requires Ubuntu 16.04, we build boost 1.65 from sources)
• except for building boost from sources, Dockerfile-min_boost = Dockerfile-18.04, so we can transfer it from master to a new 4.1 branch

[fweik]

We could think about having one container where all the library versions are pinned to the minimal required versions, so that we don't silently stop testing this when a library version is updated in the distribution. This isn't really complicated, all major package managers let you just fix a version.

[jngrad]

cuda:9.0 will essentially fulfill that role. It uses Ubuntu 16.04 and the minimal supported versions of CUDA and CMake. The version numbers of non-graphical Python packages available in the Ubuntu 16.04 repository are used as the minimal versions in requirements.txt (fb4862e). Once Ubuntu 20.04 is out and espresso drops support for CUDA9, we can use the cuda:10.1 to fulfill that role. We could rename the CI job from cuda10:maxset to ubuntu:min-dependencies for clarity.

[fweik]

Whatever you think is appropriate. I'm just saying that it is not as such guaranteed that the package versions in the distributions stay the same, which could lead to a situation where the minimal version of some package is no longer tested.

[jngrad]

We could come up with an extra check in the CI job that tests the docker image to make sure the versions of dependencies match the minimal requirements.

[RudolfWeeber]

My understanding is that we increase minimum requirements on Boost to 1.65, once we get rid of the Ubuntu 16.04 build. That in turn depends on us being able to give up on cuda 9.
This will be pursued offline.

[fweik]

@jngrad did we decide how to deal with the insufficient cmake versions? Unfortunately, I don't remember...

[jngrad]

@fweik in es meeting 2019-11-26 we decided to move to CMake from Ubuntu 18.04 and install it via pip in Ubuntu 16.04 docker images. This PR will pass CI in ~2 hours, when the new Ubuntu 16.04 images get deployed.

[fweik]

Ah, right. Thank you.

[jngrad]

Looks like kodiak won't merge a PR if the last CI pipeline passed while the PR was still in draft mode. Once the PR is marked for review, simply re-run the status_success job to make kodiak happy.