Re: port-vax/60478: releng testbed is busted on VAX

The following reply was made to PR port-vax/60478; it has been noted by GNATS.

From: Robert Elz <[email protected]>
To: [email protected]
Cc: 
Subject: Re: port-vax/60478: releng testbed is busted on VAX
Date: Thu, 23 Jul 2026 08:06:31 +0700

     Date:        Wed, 22 Jul 2026 20:20:00 +0000 (UTC)
     From:        "[email protected] via gnats" <[email protected]>
     Message-ID:  <[email protected]>
 
 
   | 	Something seems to have broken the VAX releng testbed on around
   | 	July 19th:
 
 That was a sh problem, which was since reverted.   It should be fixed
 in a new build now.  What's the build date of the /bin/sh (presumably the
 one on the vax install media) ?    (Using /rescue/sh from the same build
 wouldn't help, not that /rescue is likely to exist at that point).
 
   | 	anita test https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/20260722083921Z/vax/
 
 It should certainly have been fixed before then.   What anita is doing
 differently on some ports than others would be interesting to know.
 The amd64 install failed the same way (and was fixed after the change
 was reverted), but the i386 install wasn't bothered by the change at
 all (and I am still running it as my /bin/sh).
 
 There's no question but that the alteration (since reverted) wasn't
 complete, and could lead to this issue (the "bad file descriptor" would
 be -1, as nothing would have attempted to open the controlling tty to use).
 The question is why the different path through the shell for amd64 and vax
 (and perhaps others) than for i386?
 
 kre