Bump ci containers

[D4N]

This should fix the build failures on CentOS that appeared today. Also, I bumped the version of the GitLab CI containers to use the latest tag where applicable.

[clanmills]

Thanks for dealing with this, @D4N

I'm using import zlib in the test suite (for #989). Do we need an easy_install zlib or something like that? It won't show up immediately.

[piponazo]

LGTM! Although gitlab is failing in some cases ... are they random networking failures?

[clanmills]

It was CentOS that was giving trouble. "python3 not found" and I believe Dan changed that. I think he was installing a link from /usr/bin/python3 to /usr/bin/python36 or something like that. Now several platforms are complaining including Ubuntu.

This is rather frustrating. The CI is dictating progress. I still have several issues to fix for v0.27.3 and I'd like fixed issues integrated into v0.27-maintenance before dealing with the remaining open stuff. There's now almost no possibility of releasing 0.27.3 on schedule. On the other hand, there's nothing super urgent. Everything will settle soon.

[D4N]

Robin Mills <[email protected]> writes:

It was CentOS that was giving trouble. "python3 not found" and I believe Dan changed that. I think he was installing a link from /usr/bin/python3 to /usr/bin/python36 or something like that. Now several platforms are complaining including Ubuntu.

I changed all the CI containers to use the latest available version, which incurred a version bump in Debian & Ubuntu (and Fedora, but that one keeps working flawlessly). I'll try to find out what the hell is broken now.

This is rather frustrating. The CI is dictating progress.

On the other hand it prevents broken commits to land in master/maintenance. And belive me, I know this frustration: I've got #898 open since June which fails to build on Windows (on top of that with an error that doesn't make the least bit of sense).

…

I still have several issues to fix for v0.27.3 and I'd like fixed issues integrated into v0.27-maintenance before dealing with the remaining open stuff. There's now almost no possibility of releasing 0.27.3 on schedule. On the other hand, there's nothing super urgent. Everything will settle soon. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #1002 (comment)

[codecov]

Codecov Report

Merging #1002 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1002   +/-   ##
=======================================
  Coverage   71.18%   71.18%           
=======================================
  Files         148      148           
  Lines       19418    19418           
=======================================
  Hits        13823    13823           
  Misses       5595     5595

---

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 1125dcb...e22c97e. Read the comment docs.

Pull request has been modified.