This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Starting to use gcc-8 on CI
Type: enhancement Stage: resolved
Components: Versions: Python 3.8
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: junaruga, zach.ware
Priority: normal Keywords: patch

Created on 2018-08-26 17:14 by junaruga, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 8945 closed junaruga, 2018-08-26 17:17
Messages (5)
msg324125 - (view) Author: Jun Aruga (junaruga) * Date: 2018-08-26 17:14
This ticket is from below conversation on python-dev mailing list.
https://mail.python.org/pipermail/python-dev/2018-August/155011.html

Right now the Python project Travis CI is running on gcc-4.8.4 for coverage testing.
I want to replace it or add the latest version gcc-8 case.

The benefit to use gcc-8 is,

* It is important to run on the old version 4.8 but, it is also meaningful to follow the latest version and care issues such as warnings on the latest version gcc.
* I am working in Fedora project that is using gcc version 8 as a main c compiler. If the Python project care gcc-8, that might be helpful for people who maintain Python Debian/Fedora package or Installer on Mac/Windows.


The demerit is

* Right now the gcc-4.8 is used for the coverage. The total running time on gcc-8 might be longer than current one.
* To run the latest gcc-8, we can add the repository [1] with the way [2][3], but I am not sure whether the repository is stable.

I would show you 2 cases to use gcc-8 on Linux.

[1] https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test
[2] https://docs.travis-ci.com/user/installing-dependencies/#installing-packages-from-a-custom-apt-repository
[3] https://docs.travis-ci.com/user/languages/c/#gcc-on-os-x
[4] Ruby
   https://travis-ci.org/junaruga/ruby/builds/418242410
   https://github.com/junaruga/ruby/blob/feature/ci-new-gcc/.travis.yml
   https://github.com/ruby/ruby/pull/1937
[5] Trinity
   Example for gcc-8 on both Linux and Mac.
   https://travis-ci.org/trinityrnaseq/trinityrnaseq
   https://github.com/trinityrnaseq/trinityrnaseq/blob/master/.travis.yml
msg324131 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2018-08-26 17:46
I think rather than switching Travis CI (or VSTS) to GCC 8, it would be better to set up a buildbot running GCC 8, or switching one of our existing workers to it.  We want to keep the pre-merge CI as stable as possible, and using a bleeding-edge compiler doesn't strike me as particularly stable.
msg324132 - (view) Author: Jun Aruga (junaruga) * Date: 2018-08-26 17:57
> it would be better to set up a buildbot running GCC 8, or switching one of our existing workers to it.  We want to keep the pre-merge CI as stable as possible, and using a bleeding-edge compiler doesn't strike me as particularly stable.

Oh it seems that we have already had the CI environment as buildbot. I did not know that. Yeah it might be better to add it as a buildbot.

https://buildbot.python.org/all/#/
msg342606 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2019-05-15 22:08
We do now have at least one builder using GCC 8 (ware-gentoo-x86) and one using GCC 9 (cstratak-fedora), so I'm closing the issue.  Thanks for bringing this up, and sorry it fell through the cracks for a while!
msg342671 - (view) Author: Jun Aruga (junaruga) * Date: 2019-05-16 20:34
Sure, alright. Thanks for informing me.

On Thu, 16 May 2019 at 00:08, Zachary Ware <report@bugs.python.org> wrote:
>
>
> Zachary Ware <zachary.ware@gmail.com> added the comment:
>
> We do now have at least one builder using GCC 8 (ware-gentoo-x86) and one using GCC 9 (cstratak-fedora), so I'm closing the issue.  Thanks for bringing this up, and sorry it fell through the cracks for a while!
>
> ----------
> resolution:  -> fixed
> stage: patch review -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue34509>
> _______________________________________
History
Date User Action Args
2022-04-11 14:59:05adminsetgithub: 78690
2019-05-16 20:34:26junarugasetmessages: + msg342671
2019-05-15 22:08:15zach.waresetstatus: open -> closed
resolution: fixed
messages: + msg342606

stage: patch review -> resolved
2018-08-26 17:57:08junarugasetmessages: + msg324132
2018-08-26 17:46:43zach.waresetnosy: + zach.ware
messages: + msg324131
2018-08-26 17:17:39junarugasetkeywords: + patch
stage: patch review
pull_requests: + pull_request8418
2018-08-26 17:14:57junarugacreate