After fixing and/or working around everything in #7, I find that I see a failure like
▶ 5/5 - ../tests/process-api-tests.c:process:wait_signal: Assertion 'status & 0x000000FF == signum' failed: status & 0x000000FF == 5, signum == 4 FAIL
5/5 unit api tests FAIL 11.33s 419/420 subtests passed
when I build and test mmlib 1.4.2 on Fedora Linux.
This didn’t always fail; I’m not sure what triggered the regression. However, it seems strange to be hard-coding implementation details in the API of a portability library. I’m not sure that the current approach operates at the right level of abstraction. I’m not sure, at a glance, what to propose instead, but I’m happy, upon request, to provide additional information or to test patches.
After fixing and/or working around everything in #7, I find that I see a failure like
when I build and test
mmlib1.4.2 on Fedora Linux.This didn’t always fail; I’m not sure what triggered the regression. However, it seems strange to be hard-coding implementation details in the API of a portability library. I’m not sure that the current approach operates at the right level of abstraction. I’m not sure, at a glance, what to propose instead, but I’m happy, upon request, to provide additional information or to test patches.