[Vm-dev] appveyor queue is too long

[Nicolas Cellier]

All this take really a long time. Are the stack build really necessary?
We could build one for 32bits and one for 64bits, just to verify that we
did not break the spurstacksrc and spurstack64src, but only if we changes
spurstacksrc, spurstack64src or eventually platforms support code (if ever
spurstacksrc was using different support code than spursrc, which I doubt).
Is it possible to trigger the build on specific changes?
I wonder if we could not arrange to have another subproject that would
build those alternative VM...

Le mer. 2 janv. 2019 à 17:13, Nicolas Cellier <
nicolas.cellier.aka.nice at gmail.com> a écrit :

> Reminder: we also have [skip travis] and [skip appveyor] when we only
> change platforms specific files, or build instructions.
>
> Le mer. 2 janv. 2019 à 16:15, Fabio Niephaus <lists at fniephaus.com> a
> écrit :
>
>>
>>
>>
>> On Wed, 2 Jan 2019 at 3:46 pm, Nicolas Cellier <
>> nicolas.cellier.aka.nice at gmail.com> wrote:
>>
>>>
>>> Or maybe we don't interrupt jobs that already started?
>>>
>>
>> I think you are right. If that's not the case, we should fix it. Also, we
>> should use [ci skip] more often (but carefully of course).
>>
>>
>>>
>>> Le mer. 2 janv. 2019 à 15:44, Nicolas Cellier <
>>> nicolas.cellier.aka.nice at gmail.com> a écrit :
>>>
>>>> Hi all,
>>>> didn't we configure appveyor to cancel the builds when a newer commit
>>>> is performed in the same branch/PR?
>>>>
>>>> Currently, job queue is too deep (and slow)
>>>> https://ci.appveyor.com/project/OpenSmalltalk/vm/history
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20190103/22c29972/attachment-0001.html>