At Sat, 13 Mar 2021 20:57:20 +0700, Robert Elz wrote:
Subject: Re: odd ATF failure for sh: ulimit_redirection_interaction failed
>
> OK, I see what is going on now.
>
> The difference for you is your initial ulimit -n
> value. Not that it is big, but that when
> reduced the way
OK, I see what is going on now.
The difference for you is your initial ulimit -n
value. Not that it is big, but that when
reduced the way that test does it, getting
smaller and smaller till < 16, it happens to
land on a value < 10 as the first such limit
it tries. Using the default max fd value
Date:Fri, 12 Mar 2021 18:37:02 -0800
From:"Greg A. Woods"
Message-ID:
| The attempted FD is #18, but the error just
| says "1", not "18":
I am still looking for the source of that
error message, I suspect finding that and seeing
what sys call is actually generat
Date:Fri, 12 Mar 2021 21:38:54 -0800
From:"Greg A. Woods"
Message-ID:
Gred quoting Mouse quoting Greg:
| > > The attempted FD is #18, but the error just says "1", not "18":
I will look into the content/format of the
error message, but that's not the main issue.
G
At Fri, 12 Mar 2021 21:46:29 -0500 (EST), Mouse
wrote:
Subject: Re: odd ATF failure for sh: ulimit_redirection_interaction failed
>
> > But it still doesn't really make sense from what I see in the source.
> > The attempted FD is #18, but the error just says "1",
> But it still doesn't really make sense from what I see in the source.
> The attempted FD is #18, but the error just says "1", not "18":
Does >&N _ever_ work for multi-digit N? I thought it didn't. Maybe
that was just least-common-denominator sh, or maybe the test is broken?
/~\ The ASCII
At Fri, 12 Mar 2021 15:49:37 +0700, Robert Elz wrote:
Subject: Re: odd ATF failure for sh: ulimit_redirection_interaction failed
>
> The -X should allow...
>
> | tc-se:stderr:
> | tc-se:helper.sh: 1: Invalid argument
>
> to reveal just what is producing that error mes
Date:Thu, 11 Mar 2021 15:11:15 -0800
From:"Greg A. Woods"
Message-ID:
| My build (for amd64) of very recent -current sources (2021/03/08)
| exhibit an odd failure in the ATF tests for /bin/sh.
I'm not seeing that, and nor is the b5 testbed, not even in the recen
My build (for amd64) of very recent -current sources (2021/03/08)
exhibit an odd failure in the ATF tests for /bin/sh. (I'm not sure when
this first appeared, but it's not there in my older builds, e.g. from
2020/06)
From glancing through the test script I'm not sure quite what's
happening, thoug
