On macOS 10.15.7 with Xcode 12.4, gawk-select 1.1.2 encounters these errors when running the tests:
======== Starting select tests ========
kill
inputfd
outputfd
./outputfd.ok _outputfd differ: char 397, line 13
make[1]: [outputfd] Error 1 (ignored)
nonblock
./nonblock.ok _nonblock differ: char 187, line 13
make[1]: [nonblock] Error 1 (ignored)
select
signal
timeout_parse
======== Done with select tests ========
2 TESTS FAILED
make[2]: *** [pass-fail] Error 1
for i in _* ; \
do \
if [ "$i" != "_*" ]; then \
echo ============== $i ============= ; \
if [ -r ${i#_}.ok ]; then \
diff -c ${i#_}.ok $i ; \
else \
diff -c ./${i#_}.ok $i ; \
fi ; \
fi ; \
done | more
============== _nonblock =============
*** nonblock.ok 2015-03-28 09:48:41.000000000 -0500
--- _nonblock 2022-01-13 13:46:11.000000000 -0600
***************
*** 10,14 ****
--- 10,15 ----
1 would block; pausing...
2 would block; pausing...
3 would block; pausing...
+ 4 would block; pausing...
goodbye
0
============== _outputfd =============
*** outputfd.ok 2017-12-18 08:02:18.000000000 -0600
--- _outputfd 2022-01-13 13:46:06.000000000 -0600
***************
*** 10,14 ****
-1
see how output_fd actually launches the command
rc 1
! 0
0
--- 10,14 ----
-1
see how output_fd actually launches the command
rc 1
! 0
0
make[1]: *** [check] Error 1
Sorry for the long delay. The first "nonblock" error looks like a weird timing issue. Is the system extremely sluggish?
The second issue seems to be caused by unexpected output formatting from "wc -l".
In both cases, I think it's not important, and the extension is in fact working properly.
Is this still a concern? If so, we can try to fix these nits, but it's probably not important.
Regards,
Andy
I got access to a MacOS system on the GCC compile farm. I am unable to depulicate the "nonblock" error. As best I can tell, that must have been caused by an extremely sluggish system. Are you able to replicate the problem?
I patched the "outputfd" test case to use "cksum" instead of "wc -l", since "cksum" seems to have a more consistent output format. Please try gawk-select-1.1.4.
Regards,
Andy
Whether test failures are a concern is up to you! I just wanted to make sure you were aware of them.
I can't recall whether the system I was using when I reported this initially was sluggish.
Today I'm on a different Mac running macOS 12.7.2 and with gawk-select 1.1.4 I get some different test failures: