Re: Enabling Travis CI service for SCons on github

Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
Newsgroups gmane.comp.programming.tools.scons.devel
Message-ID <CAEyG4CHuHoMtjOojztu70oVMnYzvV7UFOmiu0DiGX79=J6P_4A@mail.gmail.com>
Sounds good. Just need to ensure that splitting in quarters doesn't either
drop one or run one test twice because of rounding..

-Bill

On Wed, Dec 20, 2017 at 9:00 AM, Daniel Moody <[email protected]> wrote:

> What about this:
>
>      --interval-start FLOAT   Percentile as float (0.0 - 1.0) of what test
> to start on from the
>                                            determined list of all tests
>      --interval-end FLOAT     Percentile as float (0.0 - 1.0) of what test
> to start on from the
>                                            determined list of all tests
>
> interval-start default is 0
> interval-end default is 1
>
> A little more flexible I think.
>
>
>
> On Wed, Dec 20, 2017 at 8:41 AM, Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
> wrote:
>
>> Maybe add a flag directly to runtest.py to split up the tests.
>> --test_mod 4 --test_index 0..3 ?
>>
>> Or something to that affect.
>>
>> On Wed, Dec 20, 2017 at 8:27 AM, Daniel Moody <[email protected]>
>> wrote:
>>
>>> Hey Andrew,
>>>
>>> I also was working on this. I think in your case the builds timed out
>>> due to issues with vswhere:
>>> https://github.com/Microsoft/vswhere/issues/87
>>> https://github.com/Microsoft/vswhere/issues/91
>>>
>>> In this case we will need to use the Visual Studio 2017 image.
>>>
>>> Also just to note; the issue mentioned above is also an issue with SCons
>>> MSVS detection in general now for SCons 3 and newer since that is when it
>>> was switched to use vswhere.
>>>
>>> I liked some of the things you had in your script so I took those and
>>> merge them into my script. I also implemented a script that will split the
>>> build up into multiple jobs like the travis script does, however I have not
>>> been able to get appveyor to do multi-line scripts correctly so it is all
>>> in a one liner at the moment:
>>> https://github.com/dmoody256/scons/blob/AppveyorCI/.appveyor.yml
>>> https://ci.appveyor.com/project/dmoody256/scons/build/1.0.53
>>>
>>> Currently python 3 will fail from several tests so I have them commented
>>> out.
>>>
>>>
>>> On Wed, Dec 20, 2017 at 8:00 AM, Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
>>> wrote:
>>>
>>>> Parallel should help.
>>>>
>>>> On my buildbot worker (with 2 other builds running single threaded
>>>> tests) it takes 2:05.
>>>> So on a reasonably modern machine, -j2 should finish in under an hour
>>>> if not, try -j3?
>>>>
>>>> Or we can split up runs as we've done with the travis run..
>>>>
>>>> -Bill
>>>>
>>>> On Wed, Dec 20, 2017 at 5:54 AM, Andrew Featherstone <
>>>> andrew.featherstone-5LkwijKnu/[email protected]> wrote:
>>>>
>>>>> I've been trying to get AppVeyor working for Windows-based CI, but
>>>>> we're hitting their 1 hour time limit (see
>>>>> https://github.com/ajf58/scons/blob/appveyor/.appveyor.yml and
>>>>> https://ci.appveyor.com/project/ajf58/scons.
>>>>>
>>>>> My next pass at this will be trying to run the unit tests in parallel
>>>>> (as the Windows VM has two cores available). Either that, or we split the
>>>>> job matrix a different way, e.g. run tests grouped by something else other
>>>>> than Python version.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> Andrew
>>>>>
>>>>> On 18 December 2017 at 22:51, Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
>>>>> wrote:
>>>>>
>>>>>> Daniel,
>>>>>>
>>>>>> Can we get travis to test with py2.7, 3.5, and 3.6 ?
>>>>>>
>>>>>> -Bill
>>>>>>
>>>>>> On Wed, Dec 6, 2017 at 12:03 AM, Bill Deegan <
>>>>>> bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org> wrote:
>>>>>>
>>>>>>> Thanks!
>>>>>>> That's pretty cool.
>>>>>>> I'll try to get the coverage hooked up soon.
>>>>>>> That'll also be very useful..
>>>>>>>
>>>>>>> On Tue, Dec 5, 2017 at 8:27 PM, Jonathon Reinhart <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> Yes, it should automatically do that.
>>>>>>>>
>>>>>>>> See this (merged) PR from one of my projects:
>>>>>>>> https://github.com/JonathonReinhart/scuba/pull/98
>>>>>>>>
>>>>>>>> Towards the bottom you'll see a "View Details" button.
>>>>>>>> Clicking that will expand a box showing the results of all the
>>>>>>>> "checks" that ran.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Dec 5, 2017 at 11:13 PM, Bill Deegan <
>>>>>>>> bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org> wrote:
>>>>>>>>
>>>>>>>>> Is there a way to get travis to post the results back into the
>>>>>>>>> pull request?
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Scons-dev mailing list
>>>>>>>> [email protected]
>>>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Scons-dev mailing list
>>>>>> [email protected]
>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Scons-dev mailing list
>>>>> [email protected]
>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Scons-dev mailing list
>>>> [email protected]
>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Scons-dev mailing list
>>> [email protected]
>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>
>>>
>>
>> _______________________________________________
>> Scons-dev mailing list
>> [email protected]
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
>
> _______________________________________________
> Scons-dev mailing list
> [email protected]
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.