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

2018-05-16 Thread Eric V. Smith 
That's very helpful, thanks. The issue was that I wasn't logged on to 
Travis. I didn't know that was a thing.


I'll check and see if this info is in the devguide.

Eric


On 5/15/18 12:20 PM, Alex Gaynor wrote:
FWIW, attached is an image pointing out the re-run button. If you're 
not seeing those it means either a) you're not logged into Travis, b) 
somehow it's not picking up your permissions correctly.


Alex

On Tue, May 15, 2018 at 11:36 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
options"
menu and no "re-run". The next time something fails I'll look again.

On 5/15/18 11:23 AM, Brett Cannon wrote:
> 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 mailto:[email protected]>
> >> wrote:
>
> I accidentally checked in some test files, and they got
backported to
> 3.7. I pushed a commit to delete them, and it was committed
to master.
>
> But in the 3.7 backport, something has gone wrong with
AppVeyor and
> Travis-CI.
>
> https://github.com/python/cpython/pull/6844
>
> AppVeyor says "Expected — Waiting for status to be reported".
> There's no
> obvious way to get it to actually report the status, or to
restart.
> There is no "Details" button listed on the PR page.
>
> For Travis-CI, Miss Isslington sent me an email that says
"Backport
> status check is done, and it's a failure ❌ ." The Travis-CI
log file
> ends with a timeout:
>
>
 ==
> FAIL: test_stdin_broken_pipe
>  (test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)
>
 --
> Traceback (most recent call last):
>File
>
 
"/home/travis/build/python/cpython/Lib/test/test_asyncio/test_subprocess.py",
>
> line 214, in test_stdin_broken_pipe
>  self.loop.run_until_complete, coro)
> AssertionError: (,  'ConnectionResetError'>) not raised by run_until_complete
>
 --
>
> I'm sure this is all due to the heavy load the systems are
under. I
> can't find a way to kick both of these off again. I couldn't
find
> anything in the devguide, but if I missed it please let me know.
>
> Thanks.
> Eric
> ___
> 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/



--
"I disapprove of what you say, but I will defend to the death your 
right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)

"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6



___
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] Mentoring Office Hours - the idea, and a question

2018-05-16 Thread Brian Curtin 
Hey all,

At the Language Summit last week, after Mariatta's talk we had a
conversation around diversity and how to grow our contributor base, which
led to someone (Steve Dower?) suggesting we post a sort of "Office Hours"
list. This would be a list of current core developers who are interested in
being available at set time(s) for helping mentor newer contributors in our
community through our process and, if they're interested, mentoring them
through the process of becoming core developers themselves.

This "Office Hours" concept is a type of thing that has worked well
elsewhere, including around the software world, and we have some people
interested in offering said mentorship, so I would like to move on to
getting this list up somewhere so we can start doing it.

With that said, before I go make a PR to the devguide to start iterating on
the implementation, an important question:

As this is both an event similar to an in-person meetup and an event meant
to be a safe space for those getting started, it will explicitly mention
the code of conduct. As such, it needs a person/persons/list to contact
should something arise in this context that needs to be handled. What/who
should that be?
 * Suggestion 1: use the already in-place [email protected],
though I can't tell who's on there.
 * Suggestion 2: Create some new list with a few key people on it.
 * Suggestion 3: List some direct names. Who?

As for implementation, there are some tools out there we could possibly
use, but in the interests of getting something out there I'm just going to
make a table and fill in some common information, starting with my own.
Calendar apps and other integrations can come as we figure them out.

Brian
___
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] Mentoring Office Hours - the idea, and a question

2018-05-16 Thread Victor Stinner 
Hi,

I'm usually available between 10:00 and 16:00 in the French timezone
(currently, it's CEST = UTC+2).

A few months ago, I wrote a tutorial and a list of available core
developers... currently it's just me :-D

   http://cpython-core-tutorial.readthedocs.io/en/latest/getting_help.html

Maybe this list should be moved in the developer guide?

   https://devguide.python.org/help/

I chose to put it in my tutorial, since it's less official, and I was
not sure if I should put myself in the official guide ;-)

--

I also heard the idea of pair-programming using a chat, a video
conference, or something else.

For example, when you work on a bug, do it with a contributor to show
how you work. I never did that before, but I may try ;-)

Victor

2018-05-16 9:52 GMT-04:00 Brian Curtin :
> Hey all,
>
> At the Language Summit last week, after Mariatta's talk we had a
> conversation around diversity and how to grow our contributor base, which
> led to someone (Steve Dower?) suggesting we post a sort of "Office Hours"
> list. This would be a list of current core developers who are interested in
> being available at set time(s) for helping mentor newer contributors in our
> community through our process and, if they're interested, mentoring them
> through the process of becoming core developers themselves.
>
> This "Office Hours" concept is a type of thing that has worked well
> elsewhere, including around the software world, and we have some people
> interested in offering said mentorship, so I would like to move on to
> getting this list up somewhere so we can start doing it.
>
> With that said, before I go make a PR to the devguide to start iterating on
> the implementation, an important question:
>
> As this is both an event similar to an in-person meetup and an event meant
> to be a safe space for those getting started, it will explicitly mention the
> code of conduct. As such, it needs a person/persons/list to contact should
> something arise in this context that needs to be handled. What/who should
> that be?
>  * Suggestion 1: use the already in-place [email protected],
> though I can't tell who's on there.
>  * Suggestion 2: Create some new list with a few key people on it.
>  * Suggestion 3: List some direct names. Who?
>
> As for implementation, there are some tools out there we could possibly use,
> but in the interests of getting something out there I'm just going to make a
> table and fill in some common information, starting with my own. Calendar
> apps and other integrations can come as we figure them out.
>
> Brian
>
> ___
> 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] Mentoring Office Hours - the idea, and a question

2018-05-16 Thread Brian Curtin 
Yep, this is something I'm adding directly in the devguide so it's right
where new contributors are already going to be looking for help and
information.

As for how those mentors and mentees actually do the work, to start with I
think it's something that each person should just do what they're
comfortable with and have access to, and then once we have some data to
work off of, maybe then we prescribe some specific ways of doing it. I'm ok
to do video things, but some might not be, so in getting this started I
wanted to just begin with names, days, times, and contact information on an
official website. If someone wants mentorship and they're available when
I'm available, they reach out to me and we find a way to talk.

On Wed, May 16, 2018 at 11:31 AM Victor Stinner  wrote:

> Hi,
>
> I'm usually available between 10:00 and 16:00 in the French timezone
> (currently, it's CEST = UTC+2).
>
> A few months ago, I wrote a tutorial and a list of available core
> developers... currently it's just me :-D
>
>http://cpython-core-tutorial.readthedocs.io/en/latest/getting_help.html
>
> Maybe this list should be moved in the developer guide?
>
>https://devguide.python.org/help/
>
> I chose to put it in my tutorial, since it's less official, and I was
> not sure if I should put myself in the official guide ;-)
>
> --
>
> I also heard the idea of pair-programming using a chat, a video
> conference, or something else.
>
> For example, when you work on a bug, do it with a contributor to show
> how you work. I never did that before, but I may try ;-)
>
> Victor
>
> 2018-05-16 9:52 GMT-04:00 Brian Curtin :
> > Hey all,
> >
> > At the Language Summit last week, after Mariatta's talk we had a
> > conversation around diversity and how to grow our contributor base, which
> > led to someone (Steve Dower?) suggesting we post a sort of "Office Hours"
> > list. This would be a list of current core developers who are interested
> in
> > being available at set time(s) for helping mentor newer contributors in
> our
> > community through our process and, if they're interested, mentoring them
> > through the process of becoming core developers themselves.
> >
> > This "Office Hours" concept is a type of thing that has worked well
> > elsewhere, including around the software world, and we have some people
> > interested in offering said mentorship, so I would like to move on to
> > getting this list up somewhere so we can start doing it.
> >
> > With that said, before I go make a PR to the devguide to start iterating
> on
> > the implementation, an important question:
> >
> > As this is both an event similar to an in-person meetup and an event
> meant
> > to be a safe space for those getting started, it will explicitly mention
> the
> > code of conduct. As such, it needs a person/persons/list to contact
> should
> > something arise in this context that needs to be handled. What/who should
> > that be?
> >  * Suggestion 1: use the already in-place
> [email protected],
> > though I can't tell who's on there.
> >  * Suggestion 2: Create some new list with a few key people on it.
> >  * Suggestion 3: List some direct names. Who?
> >
> > As for implementation, there are some tools out there we could possibly
> use,
> > but in the interests of getting something out there I'm just going to
> make a
> > table and fill in some common information, starting with my own. Calendar
> > apps and other integrations can come as we figure them out.
> >
> > Brian
> >
> > ___
> > 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] AppVeyor and Travis-CI

2018-05-16 Thread Terry Reedy 

On 5/15/2018 12:20 PM, Alex Gaynor wrote:
FWIW, attached is an image pointing out the re-run button. If you're not 
seeing those it means either a) you're not logged into Travis, b) 
somehow it's not picking up your permissions correctly.


Is there anything in the devguide about this?  The first time I tried to 
use a rebuild button, there was some sort of login/registration 
procedure.  Since then, it just works when I am logged in to github.


Thank you for the image.  I did not know that the unlabeled symbols at 
the end of each line for the three sub-builds was a rerun button for the 
one sub-build.  Good to know to only re-run what is needed.


TJR


___
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] Visual Studio Team Services checks on pull requests

2018-05-16 Thread Steve Dower 
Hi all

Just a quick note right now - don't have time for all the details.

I'm experimenting with using Visual Studio Team Services to do builds of
CPython. Right now, you'll probably see failed builds on all PRs while I
get security options figured out.

These *will not* block your PR, so feel free to ignore them. Apologies
for the noise in the meantime.

Cheers,
STeve
___
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] Mentoring Office Hours - the idea, and a question

2018-05-16 Thread Victor Stinner 
2018-05-16 11:31 GMT-04:00 Victor Stinner :
> I'm usually available between 10:00 and 16:00 in the French timezone
> (currently, it's CEST = UTC+2).

Oh, let me be more specific:

10:00-12:00 and 14:00-16:00, Monday to Friday

Yeah, in France we take our time to eat ;-)

Victor
___
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] Visual Studio Team Services checks on pullrequests

2018-05-16 Thread Steve Dower 
And a quick follow up – the builds should be running successfully now. Still 
some write up to do for everyone (tomorrow's job at the sprints), but you 
should be able to click through already and see the logs.

Thanks Microsoft for the 20 concurrent builds on Windows, macOS and Linux :)

Top-posted from my Windows phone

From: Steve Dower
Sent: Wednesday, May 16, 2018 18:10
To: [email protected]
Subject: [python-committers] Visual Studio Team Services checks on pullrequests

Hi all

Just a quick note right now - don't have time for all the details.

I'm experimenting with using Visual Studio Team Services to do builds of
CPython. Right now, you'll probably see failed builds on all PRs while I
get security options figured out.

These *will not* block your PR, so feel free to ignore them. Apologies
for the noise in the meantime.

Cheers,
STeve
___
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] Visual Studio Team Services checks on pullrequests

2018-05-16 Thread Benjamin Peterson 


On Wed, May 16, 2018, at 15:27, Steve Dower wrote:
> Thanks Microsoft for the 20 concurrent builds on Windows, macOS and Linux :)

That is quite generous! Will it be ongoing?
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/