[bug #62357] [build] Test suite failure on macOS

[G. Branden Robinson]

Update of bug #62357 (project groff):

                  Status:                    None => Need Info              
             Assigned to:                    None => gbranden               

    _______________________________________________________

Follow-up Comment #1:

Reproducing my comments from the thread.

> The good news here is that this is only 1 failure, not 6. XFAIL tests are
"eXpected to FAIL".  If one one them passes unexpectedly, that's an "XPASS'
and might mean a bug was fixed by accident.

> Shooting in the dark here, I'm wondering if the script is failing to detect
the unavailability of a UTF-8 character encoding and is running a doomed test.
 Bjarni, who often or exclusively uses ISO 8859-15, has more than once exposed
robustness oversights in my test scripts in this regard.

Now with my laptop in front of me, I can more comfortably take a look at
things.

A number of things could have gone wrong with the check--to avoid trying to
match non-basic Latin UTF-8 characters in a shell script, I used printf(1) to
send a device-independent output file to grotty, piped its output to od(1),
and grep(1)ped the result.  I expended some effort to use these utilities
portably, but if I misunderstood POSIX, or if the behavior of the macOS tools
or its shell doesn't strictly conform to it, there could well be trouble.

To try and narrow this down, I'm attaching a copy of the troff output file I
constructed in a shell variable in the test script.

So to test this, do the following from the Git checkout.


$ ./build/grotty -F ./font -F ./build/font basic_latin.grout | sed '/^$/q'


What glyphs show up on the output?  You can try copy-and-pasting it into a
Savannah bug comment and we'll see what shows up.

(file #53148)

    _______________________________________________________

Additional Item Attachment:

File name: basic_latin.grout              Size:0 KB
    <https://file.savannah.gnu.org/file/basic_latin.grout?file_id=53148>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62357>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/