[issue34509] Starting to use gcc-8 on CI

[Jun Aruga]

Jun Aruga  added the comment:

Sure, alright. Thanks for informing me.

On Thu, 16 May 2019 at 00:08, Zachary Ware  wrote:
>
>
> Zachary Ware  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 
> 
> ___

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34509] Starting to use gcc-8 on CI

[Zachary Ware]

Zachary Ware  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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34509] Starting to use gcc-8 on CI

[Jun Aruga]

Jun Aruga  added the comment:

> 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/#/

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34509] Starting to use gcc-8 on CI

[Zachary Ware]

Zachary Ware  added the comment:

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.

--
nosy: +zach.ware

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34509] Starting to use gcc-8 on CI

[Jun Aruga]

Change by Jun Aruga :


--
keywords: +patch
pull_requests: +8418
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue34509] Starting to use gcc-8 on CI

[Jun Aruga]

New submission from Jun Aruga :

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

--
messages: 324125
nosy: junaruga
priority: normal
severity: normal
status: open
title: Starting to use gcc-8 on CI
type: enhancement
versions: Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com