Re: git repositories for cygwin packaging - please test

[Ken Brown <kbrown@cornell.edu>]

On 8/6/2020 4:20 PM, Jon Turney wrote:
> On 27/05/2020 23:27, Jon Turney wrote:
>> On 04/08/2019 21:08, Jon Turney wrote:
>>> To remedy this lack, using the same ssh key you use for sftp package upload, 
>>> package maintainers can now also push to git repositories, like so:
>>
>> Package maintainers may have noticed that the output from pushing to these git 
>> repositories now includes a line like:
>>
>> "remote: scallywag: build nnn queued"
>>
>> This is a *prototype* of a system to automatically build the packages, where 
>> the results appear (some time later) at [1] (URL subject to change)
>>
>> [1] https://cygwin.com/cgi-bin2/jobs.cgi
>>
>> Currently, many packages will fail to build correctly due to:
> 
> One problem I have noticed is that some packages have test suites (which are 
> getting run via 'cygport test' invoking src_test()) which:
> 
> - require lots of extra dependencies to run, or
> - don't succeed on Cygwin, or
> - take an inordinate amount of time to run (exceeding the resource limits)
> 
> So I'm wondering if .cygport files need:
> 
> - an annotation to indicate tests shouldn't be run by this system (in RESTRICT? 
> or somewhere new?)
> - a separate TEST_REQUIRES to list packages which depended on for running tests?

I like both ideas.  For the first one (don't run 'cygport test'), I have a 
slight preference for putting the annotation somewhere new, since it's pretty 
different from the current uses of RESTRICT.  It doesn't affect what cygport 
does, but rather it tells the automated system not to run a certain cygport command.

Ken