On 22.07.23 04:44, 'Earl Chew' via EFI Boot Guard wrote: > Jan, > > I think I might have to revise the commit message, but let's sort out > the details here first. > >> Will that prevent calling the test suite with CK_FORK=no >> (https://libcheck.github.io/check/doc/check_html/check_4.html#No-Fork-Mode)? > > I have libcheck compiled with CF_FORK=no, and discovered that the tests > would not pass. > > I figure the tests have been written assuming CF_FORK=yes, and each test > inherits a pristine copy of global state in the forked child process. > Mutations of global state by the child process are not propagated > forward to the next test. > > The point of this commit is to expose this implicit assumption as an > explicit test. > > What do you think?
OK, now it makes sense to me. Please update the patch accordingly. Jan -- Siemens AG, Technology Linux Expert Center -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/344bbae3-2690-c271-33f8-65a5873e4d9f%40siemens.com.
