Re: [python-committers] AppVeyor and Travis-CI

2018-05-15 Thread Terry Reedy
On 5/16/2018 2:31 AM, Victor Stinner wrote: Oh, maybe I saw them. Are you talking about: "test_multiprocessing_forkserver: TestIgnoreEINTR.test_ignore() fails on Travis CI" https://bugs.python.org/issue33531 "test_asyncio: test_subprocess test_stdin_broken_pipe() failure on Travis CI" https://b

Re: [python-committers] AppVeyor and Travis-CI

2018-05-15 Thread Victor Stinner
Oh, maybe I saw them. Are you talking about: "test_multiprocessing_forkserver: TestIgnoreEINTR.test_ignore() fails on Travis CI" https://bugs.python.org/issue33531 "test_asyncio: test_subprocess test_stdin_broken_pipe() failure on Travis CI" https://bugs.python.org/issue33532 (I just created the

Re: [python-committers] AppVeyor and Travis-CI

2018-05-15 Thread Victor Stinner
It seems like the job has been rescheduled. I cannot see the failure ("394 tests OK"). Would you mind to open a bug report? Do you only see these failures in the 3.6 branch? Victor 2018-05-15 16:36 GMT-04:00 Terry Reedy : > I am getting repeated bogus failures, completely unrelated to a trivial

Re: [python-committers] Proposing Mark Shannon to be a core developer

2018-05-15 Thread Guido van Rossum
Thanks Mariatta! It would also be nice if we gave new committers a task along the lines of "mentor one woman or other person of diversity through their first non-trivial PR". (If the new committer is not comfortable actually merging the PR they can ask a more experienced core dev to do that -- aft

Re: [python-committers] Proposing Mark Shannon to be a core developer

2018-05-15 Thread Mariatta Wijaya
Part of the new core dev initiation should be watching this talk, titled "What is a Python Core Developer?" https://youtu.be/hhj7eb6TrtI On Tue, May 15, 2018, 11:35 AM Guido van Rossum wrote: > Let's stop the email barrage, Mark is in. Can someone tell Mark what to do? > > __

Re: [python-committers] AppVeyor and Travis-CI

2018-05-15 Thread Terry Reedy
I am getting repeated bogus failures, completely unrelated to a trivial patch, more often than not, on Travis-CI For instance, https://travis-ci.org/python/cpython/jobs/379349709 2 tests failed: test_asyncio test_multiprocessing_forkserver 1 test altered the execution environment: test_im

Re: [python-committers] AppVeyor and Travis-CI

2018-05-15 Thread Guido van Rossum
IIUC you have to close and reopen the PR. On Tue, May 15, 2018 at 11:35 AM, Eric V. Smith wrote: > Thanks. You mean close and re-open the bpo issue? > > In the past I saw a Travis "re-run" button, but now I don't. I expected to > see it on the Travis page, but last night I only saw a "More optio

Re: [python-committers] AppVeyor and Travis-CI

2018-05-15 Thread Brett Cannon
You can always close and then open an issue to re-trigger CI. As for Travis specifically, you should have the proper permissions to forcibly re-run the builds. On Mon, 14 May 2018 at 21:50 Eric V. Smith wrote: > I accidentally checked in some test files, and they got backported to > 3.7. I push

Re: [python-committers] AppVeyor and Travis-CI

2018-05-15 Thread Eric V. Smith
Thanks. You mean close and re-open the bpo issue? In the past I saw a Travis "re-run" button, but now I don't. I expected to see it on the Travis page, but last night I only saw a "More options" menu and no "re-run". The next time something fails I'll look again. On 5/15/18 11:23 AM, Brett Ca

Re: [python-committers] Proposing Mark Shannon to be a core developer

2018-05-15 Thread Guido van Rossum
Let's stop the email barrage, Mark is in. Can someone tell Mark what to do? On Tue, May 15, 2018 at 12:27 AM, Victor Stinner wrote: > 2018-05-14 16:41 GMT-04:00 Larry Hastings : > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, > writing > > both the PEP and the implementa

Re: [python-committers] Idea: Create subteams?

2018-05-15 Thread Andrew Svetlov
Agree with Yuri. We have not big amount of non-committer contributions into asyncio, and every non-trivial change requires very careful review. On Thu, Apr 26, 2018, 17:32 Yury Selivanov wrote: > On Thu, Apr 26, 2018 at 10:12 AM Victor Stinner > wrote: > [..] > > I identified 3 obvious subteams

[python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-15 Thread Ned Deily
This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your feature fixes, bug fixes, and documentation updates in before 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days from now. We will then tag and produce the 3.7.0 release candidate. Our goal continues been to be t