Hello,
Code coverage computation on Travis-CI builds probably takes a non-trivial amount of time and it's not obvious anyone is using the results concretely. Should we disable it? (note we may also disable it selectively on C++, Python, or Rust, depending on the answers) Regards Antoine.
