Steve Dower wrote:
> On 13Dec2019 0233, Victor Stinner wrote:
> > Azure Pipelines were very unstable one year ago. It's
> > getting better,
> > but there are still some random bugs sometimes. They are not really
> > blocking, so I didn't report them.
> > The only ones I'm aware of are macOS builds
On 13Dec2019 0233, Victor Stinner wrote:
Azure Pipelines were very unstable one year ago. It's getting better,
but there are still some random bugs sometimes. They are not really
blocking, so I didn't report them.
The only ones I'm aware of are macOS builds failing (which don't run on
Travis C
I created https://bugs.python.org/issue39035
I like Travis CI. It's very close to what I have on my laptop, so it's
usually trivial for me to reproduce Travis CI failures. It's also
quite fast and reliable.
Azure Pipelines were very unstable one year ago. It's getting better,
but there are still
> I.e. if someone breaks some test, is Travis-CI the only thing that keeps
the breakage from landing on master?
We still have Azure Pipelines as a mandatory check for PRs before they can
be merged to master, which includes a few additional platforms and hasn't
had any recent issues (AFAIK). I beli
Does Travis-CI serve any purpose for us still? I.e. if someone breaks some
test, is Travis-CI the only thing that keeps the breakage from landing on
master?
On Thu, Dec 12, 2019 at 5:46 PM Kyle Stanley wrote:
> Victor Stinner wrote:
> > What is the issue? Can someone please open a bug report at
Victor Stinner wrote:
> What is the issue? Can someone please open a bug report at
https://bugs.python.org/ so I can try to investigate?
>From my understanding, it looks to be pyenv related and not something we
can fix on our end, at least based on the build logs:
https://travis-ci.org/python/cpyt
What is the issue? Can someone please open a bug report at
https://bugs.python.org/ so I can try to investigate?
Victor
Le ven. 13 déc. 2019 à 02:05, Brett Cannon a écrit :
>
> This is failing again, so I had to switch off Travis from being a requirement
> (again).
>
> I'm not not going to flip
This is failing again, so I had to switch off Travis from being a requirement
(again).
I'm not not going to flip it back on until Travis has been stable for a month
as I don't like being the blocker on stuff when I can help it. And if Travis
isn't stable in a month then we might need to start t
On 12/9/2019 7:33 PM, Brett Cannon wrote:
Victor Stinner wrote:
In that case, would you mind to make Travis CI mandatory again?
Done!
It is again working fine on 3.8 and 3.7.
--
Terry Jan Reedy
___
Python-Dev mailing list -- python-dev@python.org
Victor Stinner wrote:
> In that case, would you mind to make Travis CI mandatory again?
Done!
> Victor
> Le ven. 6 déc. 2019 à 19:10, Brett Cannon br...@python.org a écrit :
> >
> > Victor Stinner wrote:
> > Hello,
> > Le mar. 26 nov. 2019 à 20:40, Brett Cannon br...@python.org a écrit :
> > I ha
Steve Dower wrote:
> GitHub Actions *is* a CI service now, so my PR is actually using their
> machines for Windows/macOS/Ubuntu build and test.
Oh I see, that makes more sense. Thanks for the clarification.
Steve Dower wrote:
> It doesn't change the ease of enabling/disabling anything - that's st
In that case, would you mind to make Travis CI mandatory again?
Victor
Le ven. 6 déc. 2019 à 19:10, Brett Cannon a écrit :
>
> Victor Stinner wrote:
> > Hello,
> > Le mar. 26 nov. 2019 à 20:40, Brett Cannon br...@python.org a écrit :
> > > I have turned Travis off as a required check on the
> >
On 06Dec2019 1023, Kyle Stanley wrote:
Steve Dower wrote:
> As a related aside, I've been getting GitHub Actions support together
> (which I started at the sprints).
Would adding support for GitHub Actions make it easier/faster to
temporarily disable and re-enable specific CI services when th
Steve Dower wrote:
> As a related aside, I've been getting GitHub Actions support together
> (which I started at the sprints).
Would adding support for GitHub Actions make it easier/faster to
temporarily disable and re-enable specific CI services when they're having
external issues? IIUC, that see
Victor Stinner wrote:
> Hello,
> Le mar. 26 nov. 2019 à 20:40, Brett Cannon br...@python.org a écrit :
> > I have turned Travis off as a required check on the
> > 3.7, 3.8, and master branches until someone is able to get a fix in.
> > That makes me sad :-( Is there an issue at bugs.python.org to t
On 06Dec2019 0620, Victor Stinner wrote:
What's the status? Right now, I see Travis CI jobs passing on 3.7,
3.8 and master branches so I don't understand the problem. Maybe the
issue has been fixed and Travis CI can be made mandatory again?
They've been passing fine for me too, I'm not quite su
Hello,
Le mar. 26 nov. 2019 à 20:40, Brett Cannon a écrit :
> I have turned Travis off as a required check on the 3.7, 3.8, and master
> branches until someone is able to get a fix in.
That makes me sad :-( Is there an issue at bugs.python.org to track
it? What's the status? Right now, I see Tr
I have turned Travis off as a required check on the 3.7, 3.8, and master
branches until someone is able to get a fix in.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.
On 11/25/2019 12:40 PM, Ivan Pozdeev via Python-Dev wrote:
On 25.11.2019 9:50, Terry Reedy wrote:
On 11/24/2019 7:30 PM, Ivan Pozdeev via Python-Dev wrote:
On 25.11.2019 1:10, Terry Reedy wrote:
Travis passed https://github.com/python/cpython/pull/17366
but a half hour later twice failed
htt
On 25.11.2019 9:50, Terry Reedy wrote:
On 11/24/2019 7:30 PM, Ivan Pozdeev via Python-Dev wrote:
On 25.11.2019 1:10, Terry Reedy wrote:
Travis passed https://github.com/python/cpython/pull/17366
but a half hour later twice failed
https://github.com/python/cpython/pull/17370
This is build lo
On 11/24/2019 7:30 PM, Ivan Pozdeev via Python-Dev wrote:
On 25.11.2019 1:10, Terry Reedy wrote:
Travis passed https://github.com/python/cpython/pull/17366
but a half hour later twice failed
https://github.com/python/cpython/pull/17370
This is build logic's fault, `python3.8` is not guarantee
On 25.11.2019 1:10, Terry Reedy wrote:
Travis passed https://github.com/python/cpython/pull/17366
but a half hour later twice failed
https://github.com/python/cpython/pull/17370
This is build logic's fault, `python3.8` is not guaranteed to be present. I believe Configure is finding pyenv's shi
22 matches
Mail list logo
