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.
_
Hum. For backports, should we stop to approve PRs in advance?
miss-islington currently ignores VSTS status and so may merge a
backport even if VSTS Windows fails.
Victor
2018-06-04 17:02 GMT+02:00 Brett Cannon :
> Victor noticed that AppVeyor stopped building about 19 hours ago, leading to
> it b
I'm currently not in the mood to argue about VSTS' stability so I don't
feel comfortable flipping that on as a requirement quite yet.
On Mon, 4 Jun 2018 at 08:33 Victor Stinner wrote:
> Hum. For backports, should we stop to approve PRs in advance?
> miss-islington currently ignores VSTS status a
2018-06-04 18:18 GMT+02:00 Brett Cannon :
> I'm currently not in the mood to argue about VSTS' stability so I don't feel
> comfortable flipping that on as a requirement quite yet.
I don't suggest to make it mandatory right now.
I will try to keep on eye on VSTS ;-)
Victor
___
>
> miss-islington currently ignores VSTS status
No it does not yet ignore VSTS status. If VSTS status failed, it will not
automerge.
Mariatta
ᐧ
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/p
On 04Jun2018 0932, Victor Stinner wrote:
2018-06-04 18:18 GMT+02:00 Brett Cannon :
I'm currently not in the mood to argue about VSTS' stability so I don't feel
comfortable flipping that on as a requirement quite yet.
I don't suggest to make it mandatory right now.
I will try to keep on eye on
On Sun, 3 Jun 2018 at 20:30 Ned Deily wrote:
> On Jun 3, 2018, at 22:30, Steve Dower wrote:
> > We probably have enough data on the VSTS builds by now to see whether
> they are comparable/faster than AppVeyor. Obviously the idea of doing that
> work was to be able to migrate builds if it made se
By the way, Python 2.7 doesn't have AppVeyor nor VSTS?
Is there a plan to add VSTS to Python 2.7?
Victor
2018-06-04 18:46 GMT+02:00 Steve Dower :
> On 04Jun2018 0932, Victor Stinner wrote:
>>
>> 2018-06-04 18:18 GMT+02:00 Brett Cannon :
>>>
>>> I'm currently not in the mood to argue about VSTS'
Correct, and I wasn't planning on it. The default VSTS machines don’t have the
right compiler, and I’m not about to start managing VMs for 2.7 at this stage.
Top-posted from my Windows 10 phone
From: Victor Stinner
Sent: Monday, June 4, 2018 10:07
To: Steve Dower
Cc: python-committers
Subject: R
On Sun, 3 Jun 2018 at 13:23 Terry Reedy wrote:
> When we used hg, core dev committers could actually commit to the
> repository when they judged it appropriate. When we moved to github,
> Brett, with whoever's approval,
Since this seems very much directed at me, I should mention any authority
I’d also add that it is generally a good thing that people with power and a
voice (e.g. the core devs) are having a similar experience that an external
contributor would. This is our best line of defense against the external
contributor experience degrading to a bad place. By having core devs sh
+1. For example for mypy I use the "triangular" git setup even though as a
mypy core dev I could simply push my branch to the main repo.
On Mon, Jun 4, 2018 at 11:49 AM, Donald Stufft wrote:
> I’d also add that it is generally a good thing that people with power and
> a voice (e.g. the core devs
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 t
On Sun, Jun 03, 2018 at 12:44:55PM -0700, Brett Cannon wrote:
> I will admit that I think we lost some core devs who had zero exposure to
> GitHub prior to switching and never found the motivation to ramp up on the
> new workflow.
*raises hand*
I'm one of them. Not that I was a prolific core dev
14 matches
Mail list logo
