Re: [python-committers] Turning off AppVeyor as required

2018-06-10 Thread Victor Stinner 
Brett Cannon just made AppVeyor required again on 2.7, 3.6, 3.7 and master ;-)

Victor

2018-06-04 21:38 GMT+01:00 Victor Stinner :
> I have very good news from AppVeyor:
>
> * AppVeyor runs again jobs on pull requests: it's back!
> * Issue with quotas: it was a disk issue, it was on their side and
> it's now fixed.
> * AppVeyor donate us additional parallel job to the python account!
>
> Moreover:
>
> * They proposed us to extend the timeout to 90 minuts. Hopefully, a
> full build (download + compile + run tests) takes usually less than 15
> min, so it's fine.
> * They explained me how to disable AppVeyor on branches to only run
> tests on pull requests. "Do not build feature branches with open Pull
> Requests in UI (skip_branch_with_pr: true if you use YAML)." seems the
> safest option. Another option is: "disable Pushes event in GitHub
> Webhook settings" but I don't undestand if it only impacts AppVeyor or
> all our hooks.
>
> Thank you very much AppVeyor! See my support issue for the details:
>
> http://help.appveyor.com/discussions/problems/14532-cpython-exceeded-allowed-resource-quotas-what-are-these-quotas-can-them-be-increased
>
> Victor
>
> 2018-06-04 17:02 GMT+02:00 Brett Cannon :
>> Victor noticed that AppVeyor stopped building about 19 hours ago, leading to
>> it blocking all open PRs. I have gone ahead and switched off requiring
>> AppVeyor for now, so please pay attention to at least the Windows VSTS
>> status check to make sure you're not breaking Windows by accident.
>>
>> ___
>> 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] b.p.o. status and resolution permissions

2018-06-10 Thread Tal Einat 
Hi,

I'm a (somewhat) new core-dev and have begun working on various issues.

I don't have permission to change issue status and resolution on b.p.o. It
seems at this point that is holding things back and making more work for
others. I will be extra careful and only change those when I'm very sure it
is appropriate.

Can the necessary permission bits be flipped?

- Tal Einat
___
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] b.p.o. status and resolution permissions

2018-06-10 Thread Ned Deily 
On Jun 11, 2018, at 01:38, Tal Einat  wrote:
> I'm a (somewhat) new core-dev and have begun working on various issues.
> 
> I don't have permission to change issue status and resolution on b.p.o. It 
> seems at this point that is holding things back and making more work for 
> others. I will be extra careful and only change those when I'm very sure it 
> is appropriate.
> 
> Can the necessary permission bits be flipped?

You should be good to go now.  Welcome to the tracker!

--
  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/