[python-committers] Sporadic failures in test_multiprocessing_main_handling?

2017-06-12 Thread Antoine Pitrou 

Hello all,

Are we aware of sporadic failures in test_multiprocessing_main_handling?
I got a hang here and I'm wondering if it's due to my changes:
https://travis-ci.org/python/cpython/jobs/242108490#L2211

Thanks & Regards

Antoine.
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Sporadic failures in test_multiprocessing_main_handling?

2017-06-12 Thread Antoine Pitrou 

I manage to reproduce.  Sorry for the noise here.

Regards

Antoine.



Le 12/06/2017 à 19:50, Antoine Pitrou a écrit :
> 
> Hello all,
> 
> Are we aware of sporadic failures in test_multiprocessing_main_handling?
> I got a hang here and I'm wondering if it's due to my changes:
> https://travis-ci.org/python/cpython/jobs/242108490#L2211
> 
> Thanks & Regards
> 
> Antoine.
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California

2017-06-12 Thread Lukasz Langa 
Hello fellow committers!
I'm organizing another core sprint this year to make Python 3.7 the best 
release possible.

WHY:
1. Community.  The sprints at the end of PyCon are great but they mostly get 
the same people in the room year after year.  Many of the most active 
contributors never attend conferences.  My goal with this sprint is to bring 
together many core devs who rarely if ever meet!
2. Focus.  When we have sprints at the end of a conference, many of us are 
pretty tired and less productive than we could have been without the late 
dinners, endless hallway sessions, and so on.  Some of the sprinters are 
preoccupied with tutoring newcomers.  This sprint won't be after a major 
conference, and it's only for seasoned CPython core devs--so get to work!
3. Communication. There are tremendous benefits to getting everyone together in 
one big room.  Conversations that drag on on python-dev can be solved quickly 
in person.  Even contentious debates become faster, easier, and more civil.  
And meeting face-to-face helps us all feel more connected to our community.

WHY THE BAY AREA: We have a large population of core contributors here.  Also, 
I can arrange for Facebook to provide us a "war room" for the whole week, with 
full access to the campus during the sprints. That includes free food for 
breakfast, lunch, dinner, and snacks, compatible with almost any dietary 
restrictions.

WHY EARLY SEPTEMBER: It's almost impossible to find a time that doesn't overlap 
with a PyCon. This week worked well last year so we're redoing it that way. 
Monday September 4 is Labor Day in the US, which may make it easier for 
employees of US companies to attend, as they'd only be taking off four days 
instead of five.

HOW LONG: A full week Monday, Sep 4 to Friday, Sep 8 evening. You can check 
into your hotel the day before the sprint (Sunday, Sep 3) and check out the day 
after (Saturday, Sep 9).

HOW BIG: No fewer than 10, no more than 20.  More than 20 people would be great 
but it'd be hard for me to organize a sprint that big.

WHO PAYS: The venue, hotels, and food are provided by Facebook. I'm working on 
getting flight reimbursements. Last year they were provided by the Python 
Software Foundation. Anybody is free to waive their reimbursement.

PLEASE REPLY: If you're interested in attending and have the commit bit on 
GitHub's python/cpython, fill out this Google Form:
https://goo.gl/forms/MzrNtRe0NAmzvGwF2 

DISCLAIMER: I'd like to be able to host everybody. However, if I receive more 
than 20 applications, this is not going to be possible. In this case, the 
following will happen:

1. I will look at your current level of involvement in CPython development. 
This includes metrics like commits / PRs, activity on the bug tracker and 
python-dev, special role (release manager, infrastructure dev, etc.).
2. I will look at your sprint plan and ability to participate in the entire 
sprint (per answers to the questions above).
3. I will gather all this data and leave the final decision to our Benevolent 
Dictator (who is also attending the sprint). This is one of those occasions 
where having a dictator is useful.

DON'T WAIT: September is closer than you think! Please let me know as soon as 
possible so we can start setting up the event. I'm going to close the sign-up 
form on June 23rd.

Organizational-ly yours,
Ł
Vice-Minister of Silly Sprints


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] IMPORTANT: Python 3.6.2 Maintenance Release Release Candidate in 3+ days (Monday 2017-06-12 12:00 UTC)

2017-06-12 Thread Ned Deily 
An update on 3.6.2rc1: we have been working through a few critical and release 
blocker issues that needed to be fixed for 3.6.2.  Thanks to everyone who has 
helped with them!  At the moment, we have one security-related release blocker 
(http://bugs.python.org/issue29591) which I think we need to get addressed in 
3.6.2.  So, I'm delaying 3.6.2rc1 until we can get that resolved.  That means 
that, for the moment, changes going into the 3.6 branch will likely make in 
into 3.6.2.  I'll let you know when we are ready to tag.

Thanks!
--Ned


On Jun 8, 2017, at 23:34, Ned Deily  wrote:
> We are approaching the end of the second calendar quarter of 2017 and, 
> according to PEP 494, it's time to start producing the second maintenance 
> release for the 3.6 series.  The schedule calls for the release candidate to 
> be produced on Monday 2017-06-12 UTC.  As was the case with previous 3.6.x 
> releases, the plan is for the release candidate to be the same as the final 
> release, that is, no additional changes go in after the release candidate 
> except for any showstopper critical problems that might be discovered with 
> rc1.  So please plan to get any security fixes, bug fixes, and documentation 
> changes you think should be in 3.6.2 merged in ASAP.  The 3.6.2 final is 
> planned for two weeks following rc1, that is, on 2017-06-26.  The next 3.6 
> maintenance release (3.6.3) is planned to follow about 3 months later, so 
> most likely in 2017-09.
> 
> A reminder that the 3.6 branch will remain open for checkins throughout the 
> 3.6.2rc and final cycle.  Once 3.6.2rc1 is tagged, new commits to the 3.6 
> branch will release with 3.6.3.  As always, if you find any problem in 
> 3.6.2rc1 that you may believe should be corrected in 3.6.2, please ensure the 
> problem is documented in a new or existing open issue on bugs.python.org, 
> ensure that the Priority field of the issue is set to "release blocker", and 
> that "Python 3.6" is included in the selected Versions.  Comments or tags on 
> github Pull Requests are NOT sufficient!
> 
> Thanks again for all of your efforts in bringing 3.6 into the world and for 
> helping now to make it even better!
> 
> https://www.python.org/dev/peps/pep-0494/
> http://cpython-devguide.readthedocs.io

--
  Ned Deily
  [email protected] -- []

___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Sporadic failures in test_multiprocessing_main_handling?

2017-06-12 Thread Victor Stinner 
Hi Antoine,

Buildbots got a new coloor last month: orange. It means that we
detected "warnings", one of these warnings are tests which failed once
but then passed when run a second time. I started to open an issue for
each CI failure and for each unstable test (fail then pass).

For multiprocessing, I already have 4 open issues:

http://bugs.python.org/issue30595
http://bugs.python.org/issue30356
http://bugs.python.org/issue30339
http://bugs.python.org/issue30333

See also by "buildbot report" emails to python-dev.

Victor

2017-06-12 19:50 GMT+02:00 Antoine Pitrou :
>
> Hello all,
>
> Are we aware of sporadic failures in test_multiprocessing_main_handling?
> I got a hang here and I'm wondering if it's due to my changes:
> https://travis-ci.org/python/cpython/jobs/242108490#L2211
>
> Thanks & Regards
>
> Antoine.
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Sporadic failures in test_multiprocessing_main_handling?

2017-06-12 Thread Victor Stinner 
typo:

2017-06-13 8:42 GMT+02:00 Victor Stinner :
> See also *my* "buildbot report" emails to python-dev.

Oh, it seems like you bug you saw is not in the bug tracker. I opened
this issue:
http://bugs.python.org/issue30643

You can use it to track your progress on that one, since it sems like
you are able to reproduce it (good!).

Victor
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/