RE: cygport test has zero exit status on failures

["Jason Pyeron" <jpyeron@pdinc.us>]

> -----Original Message-----
> From: Achim Gratz
> Sent: Tuesday, May 18, 2021 4:16 PM
> 
> Jason Pyeron writes:
> > If I put it in ~/.config/cygport.conf it will impact all packages, not
> > just the "one". The only place it is limited to applicable package is
> > in the package.cygport file, or am I missing something?
> 
> You can always override these settings when starting a build on a CI
> (either by changing the config file or just remove/set more environment
> variables), but the point was that the cygport file should not lock in a
> specific behaviour, but rather allow the environment to determine it.

Having trouble groking the conceptual design.

If I have a CI build for *.cygport - is it expected to have conditional logic based on which package is being processed? 

I thought was the purpose of the cygport file [1] was to contain only the compiling, testing, and installation instructions, just like portage [2]. 

In any case the all or all-test does not execute the test step, so the customization of the src_test does not impact the default behaviors.

As an example you can look at my CI builds [3] to see the sequence: 

1. ensure dependencies are installed on build host
2. cygport file.cygport download
3. cygport file.cygport all-test
4. cygport file.cygport test
5. archive artifacts

The same build host is used (serially) for other builds.

-Jason

1: /usr/share/doc/cygport/README §2
2: https://devmanual.gentoo.org/ebuild-writing/functions/src_test/index.html
3: https://www.pdinc.us/ci/job/oss-cygwin-pdfgrep/job/cygwin-cygport-2.1.2/3/