Re: [PATCH] find RLIM_NLIMITS correctly on Cygwin

["Daniel Shahaf" <d.s@xxxxxxxxxxxxxxxxxx>]

Daniel Shahaf wrote on Fri, 28 Feb 2020 14:19 +00:00:
> Jun T wrote on Fri, 28 Feb 2020 17:42 +0900:
> > > 2020/02/27 22:22, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> > > 
> > > Jun T wrote on Tue, 25 Feb 2020 18:38 +0900:  
> > >> We may hope that a user who sees
> > >> UNKNOWN in the output of limit/ulimit will report it to us, or
> > >> add a simple test like
> > >> 
> > >> limit | grep UNKNOWN || print OK
> > >> 
> > >> somewhere in the test (but in which .ztst file?).  
> > > 
> > > I prefer a new test, but to arrange things in such a way that a failure
> > > of the new test won't fail the build or prevent other tests from
> > > running.  
> > (snip)
> > > We might even add a new flag, e.g., «ZTST_failure_is_fatal=false»  
> > 
> > Currently each test chunk can have flags 'd' 'D' 'q' and 'f'.
> > We can add a new flag, say 'n', to make the failure not fatal.
> 
> If we add a new letter flag, we won't be able to make the non-fatalness
> specific to only one platform, though.  We a new parameter, we'd be
> able to do «[[ $OSTYPE == cygwin* ]] && ZTST_failure_is_fatal=false».

That was just an example; there's no particular reason to make the
«limit | grep UNKNOWN» test specific to any particular set of
${OSTYPE}s.

Cheers,

Daniel