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 a
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 multiprocessin
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
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 c
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
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-committer
