I read again the read and I misunderstood it. I didn't notice that "make buildbottest" recompiles Python. Ok, I confirm the bug.
I see two options: * move the "make regen-all" check *before* "make" * move the "make regen-all" check in a different Travis CI. If we move the test in a GCC job, it would allow to check regen and GCC warnings in the same job. Victor 2017-07-24 12:16 GMT+02:00 Antoine Pitrou <anto...@python.org>: > > Le 24/07/2017 à 10:55, Victor Stinner a écrit : >> IMHO everything is fine and we don't have to do anything ;-) > > What do you mean? The fact that all the CPython source code (including > C extensions) is compiled twice looks suboptimal to me. We could > probably win a minute or two on Travis-CI build times. > > Regards > > Antoine. > _______________________________________________ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
