Update: I fixed the root issue of https://bugs.python.org/issue33694
it was a race condition in ProactorEventLoop, so specific to Windows.
test_asyncio *should* now pass on all Windows CIs. I leave the issue
open a few days to check if the issue is really fixed.
Victor
2018-06-07 18:38
2018-06-07 5:36 GMT+02:00 Brett Cannon :
>> In the meanwhile, AppVeyor seems stable again. Would it be possible to
>> re-enable it in all stable branches?
>
>
> It was never turned off, but if you mean make it required again then yes.
Yes, I mean making it required again... but yesterday I made
2018-06-06 19:37 GMT+02:00 Brett Cannon :
> My point is this is all software which we know isn't perfect and as long as
> there is a way to kick off a wedged/failed build again I don't think it's a
> hard blocker.
Ok, let me elaborate.
I'm trying to stabilize Travis CI, AppVeyor and buildbots
On Wed, 6 Jun 2018 at 04:16 Victor Stinner wrote:
> IHMO this issue is a blocker to make VSTS mandatory:
> https://bugs.python.org/issue33782
>
> VSTS Windows-PR failed with "The request was failed due to an internal
> service error. Please try again."
>
> It would prevent to not be blocked by
It's an error intern to VSTS, it's unrelated to Python. There is no
log. Don't worry, Steve Dower already passed the bug to the VSTS team.
Victor
2018-06-06 15:28 GMT+02:00 Stephane Wirtel :
> On 06/06, Victor Stinner wrote:
>>
>> IHMO this issue is a blocker to make VSTS mandatory:
>>
On 06/06, Victor Stinner wrote:
IHMO this issue is a blocker to make VSTS mandatory:
https://bugs.python.org/issue33782
VSTS Windows-PR failed with "The request was failed due to an internal
service error. Please try again."
Victor, do we have a traceback of the build or just this message?
IHMO this issue is a blocker to make VSTS mandatory:
https://bugs.python.org/issue33782
VSTS Windows-PR failed with "The request was failed due to an internal
service error. Please try again."
It would prevent to not be blocked by an internal VSTS error :-(
Victor
2018-06-05 20:07 GMT+02:00
On Tue, 5 Jun 2018 at 03:52 Victor Stinner wrote:
> Steve has no plan to support VSTS on Python 2.7:
>
> "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."
>
> So I would suggest to
Steve has no plan to support VSTS on Python 2.7:
"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."
So I would suggest to keep AppVeyor for Python 2.7, at least for the
short term, and
On Mon, 4 Jun 2018 at 11:56 Ned Deily wrote:
> On Jun 4, 2018, at 14:34, Brett Cannon wrote:
> > We had to turn off AppVeyor as a requirement today due to it not running
> any builds for the last 20 hours. Ned Deily suggested that since VSTS on at
> least Windows has stabilized that maybe we
2018-06-04 20:34 GMT+02:00 Brett Cannon :
> Since
> https://python.visualstudio.com/cpython/_build/index?context=mine=%5C=4&_a=history
> shows the builder has been stable
Just to be pedantic, it's not 100% stable yet :-) test_asyncio strikes back:
https://bugs.python.org/issue33694#msg318705
I
There are some updates on the AppVeyor side:
https://mail.python.org/pipermail/python-committers/2018-June/005549.html
Victor
2018-06-04 20:34 GMT+02:00 Brett Cannon :
> We had to turn off AppVeyor as a requirement today due to it not running any
> builds for the last 20 hours. Ned Deily
On Jun 4, 2018, at 14:34, Brett Cannon wrote:
> We had to turn off AppVeyor as a requirement today due to it not running any
> builds for the last 20 hours. Ned Deily suggested that since VSTS on at least
> Windows has stabilized that maybe we should switch off AppVeyor off entirely
> and make
13 matches
Mail list logo
