Sorry for replying to an older thread. Travis has also limited their build
minutes for open source projects as per new pricing plan :
https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
Thanks
Regards,
Karthikeyan S
On Fri, Oct 16, 2020, 2:12 PM Victor Stinner wrote:
> Hi,
>
> Python h
> On 19 Oct 2020, at 21:22, Ned Deily wrote:
>>> Let's just disable Travis on all branches for now until there is reason to
>>> believe the problems we've seen are fixed.
>> +1 from me.
>
> Pablo, Łukasz: any objections to disabling Travis on your branches? If not,
> one of us, or Ernest, can
On Oct 19, 2020, at 14:35, Brett Cannon wrote:
> On Mon, Oct 19, 2020 at 11:22 AM Ned Deily wrote:
>> On Oct 19, 2020, at 13:59, Brett Cannon wrote:
>> > On Sun, Oct 18, 2020 at 2:21 PM Ethan Furman wrote:
>> >> On 10/18/20 1:18 PM, Ned Deily wrote:
>> >> > On Oct 18, 2020, at 15:45, Carol Will
On Mon, Oct 19, 2020 at 11:22 AM Ned Deily wrote:
> On Oct 19, 2020, at 13:59, Brett Cannon wrote:
> > On Sun, Oct 18, 2020 at 2:21 PM Ethan Furman wrote:
> >> On 10/18/20 1:18 PM, Ned Deily wrote:
> >> > On Oct 18, 2020, at 15:45, Carol Willing wrote:
> >> >> We've largely moved away from Tra
On Oct 19, 2020, at 13:59, Brett Cannon wrote:
> On Sun, Oct 18, 2020 at 2:21 PM Ethan Furman wrote:
>> On 10/18/20 1:18 PM, Ned Deily wrote:
>> > On Oct 18, 2020, at 15:45, Carol Willing wrote:
>> >> We've largely moved away from Travis for Jupyter testing in favor of
>> >> Azure pipelines and
On Sun, Oct 18, 2020 at 2:21 PM Ethan Furman wrote:
> On 10/18/20 1:18 PM, Ned Deily wrote:
> > On Oct 18, 2020, at 15:45, Carol Willing wrote:
> >> We've largely moved away from Travis for Jupyter testing in favor of
> Azure pipelines and CircleCI as Travis was becoming increasingly slow and
>
On 10/18/20 1:18 PM, Ned Deily wrote:
On Oct 18, 2020, at 15:45, Carol Willing wrote:
We've largely moved away from Travis for Jupyter testing in favor of Azure
pipelines and CircleCI as Travis was becoming increasingly slow and timing out.
Along those lines, if we are basically going to ign
On Oct 18, 2020, at 15:45, Carol Willing wrote:
> We've largely moved away from Travis for Jupyter testing in favor of Azure
> pipelines and CircleCI as Travis was becoming increasingly slow and timing
> out.
Along those lines, if we are basically going to ignore the Travis CI results,
perhaps
We've largely moved away from Travis for Jupyter testing in favor of Azure
pipelines and CircleCI as Travis was becoming increasingly slow and timing
out.
On Sun, Oct 18, 2020 at 11:03 AM Victor Stinner wrote:
> Sometimes, when you reschedule a build in Travis CI, a PR gets *two*
> Travis CI job
Sometimes, when you reschedule a build in Travis CI, a PR gets *two*
Travis CI jobs instead of one, and the first one remains stale
forever. There are multiple issues with Travis CI.
Victor
Le sam. 17 oct. 2020 à 19:58, Larry Hastings a écrit :
>
>
>
> I don't know how the configuration on this
I don't know how the configuration on this stuff works. But my dim
understanding is: some automation from Github (that we own / configure /
wrote) notices that we have a new checkin on a PR and kicks off the
Travis CI build. The problem is that sometimes the status of the Travis
CI build d
On Fri, Oct 16, 2020 at 12:26 PM Brett Cannon wrote:
>
> On Fri, Oct 16, 2020 at 11:58 AM Pablo Galindo Salgado <
> pablog...@gmail.com> wrote:
>
>> > We should simply mark the github actions "Tests / Ubuntu" CI as
>> required.
>>
>> +1 I completely agree with everything Gregory said.
>>
>
> +1 f
On Fri, Oct 16, 2020 at 11:58 AM Pablo Galindo Salgado
wrote:
> > We should simply mark the github actions "Tests / Ubuntu" CI as
> required.
>
> +1 I completely agree with everything Gregory said.
>
+1 from me as well.
-Brett
>
>
> On Fri, 16 Oct 2020 at 19:36, Gregory P. Smith wrote:
>
>>
> We should simply mark the github actions "Tests / Ubuntu" CI as required.
+1 I completely agree with everything Gregory said.
On Fri, 16 Oct 2020 at 19:36, Gregory P. Smith wrote:
>
>
> On Fri, Oct 16, 2020 at 1:42 AM Victor Stinner
> wrote:
>
>> Hi,
>>
>> Python has no mandatory Linux CI j
On Fri, Oct 16, 2020 at 1:42 AM Victor Stinner wrote:
> Hi,
>
> Python has no mandatory Linux CI job on pull requests anymore. Right
> now Windows (x64) remains the only mandatory job. Please be careful to
> manually check other CI before merging a PR.
>
> --
>
> We had to deal with at least 3 di
Should we consider dropping Travis CI as a CI provider if it continues to
be so flaky? Otherwise isn't it becoming just noise on a PR?
On Fri, Oct 16, 2020 at 1:42 AM Victor Stinner wrote:
> Hi,
>
> Python has no mandatory Linux CI job on pull requests anymore. Right
> now Windows (x64) remains
16 matches
Mail list logo
