[groff] 07/08: PROBLEMS: Note expected Solaris 10 test failures.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 92b1d963d74e9e00c7d3aa532888e8b4b474c01e
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sat Feb 25 04:03:03 2023 -0600

    PROBLEMS: Note expected Solaris 10 test failures.
    
    Commit b2157f22b5, 22 February, exposed this.
---
 PROBLEMS | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/PROBLEMS b/PROBLEMS
index 3eef03993..d010a6e45 100644
--- a/PROBLEMS
+++ b/PROBLEMS
@@ -841,7 +841,7 @@ in place to use a conforming shell.  Here is an example.
       `find . -name '*.sh' | grep /tests/`
   $ PATH=/usr/xpg4/bin:$PATH gmake check
 
-Two test failures remain expected on Solaris 10.
+Some test failures remain expected on Solaris 10.
 
 1.  FAIL: tmac/tests/pdfpic_does-not-choke-on-bad-pdfinfo-output.sh
 
@@ -872,6 +872,25 @@ Two test failures remain expected on Solaris 10.
     which sanitizes $PATH to avoid privilege escalation, thus making it
     likely that the non-conforming tr in /usr/bin will be found first.
 
+3.  FAIL: src/roff/groff/tests/initialization_is_quiet.sh
+    FAIL: src/roff/groff/tests/msoquiet_works.sh
+    FAIL: src/roff/groff/tests/soquiet_works.sh
+
+    /usr/xpg4/bin/sh is non-conforming with the POSIX Issue 4 standard,
+    despite its name.  Its "unset" builtin is buggy.
+
+    These tests use the "unset" shell builtin command to prevent
+    environment variables from confounding test results.
+
+    POSIX says "[u]nsetting a variable ... that was not previously set
+    is not considered an error and will not cause the shell to abort."
+
+    Nevertheless this builtin returns an error exit status in this
+    circumstance.
+
+    $ /usr/xpg4/bin/sh -c 'unset _NON_EXISTENT_XYZ; echo $?'
+    1
+
 ----------------------------------------------------------------------
 
 * I am building from the Git repository, using 'autoreconf' from a GNU