Re: chicken 5.3.0 - improving POSIX test on Cygwin platform
> On Mon, Mar 21, 2022 at 5:19 AM wrote: > > > > Sorry for the overly late reply. I'm not too familiar with cygwin, what > > should the tests report here? The cond-expand for "windows" should trigger > > on cygwin, how is it handling the permission bits (as compared to "raw" > > Windows systems)? Does it "fake" the normal UNIX permission bits? > > > Cygwin maps Windows ACLs into Posix permissions bits, but not 1-1; > consequently, you can't assume that setting the permissions bits and then > reading them back will necessarily produce the same results. Therefore, > any test that depends on that property should be skipped altogether. > Very good, thanks for the information. felix
Re: chicken 5.3.0 - improving POSIX test on Cygwin platform
On Mon, Mar 21, 2022 at 5:19 AM wrote: > Sorry for the overly late reply. I'm not too familiar with cygwin, what > should the tests report here? The cond-expand for "windows" should trigger > on cygwin, how is it handling the permission bits (as compared to "raw" > Windows systems)? Does it "fake" the normal UNIX permission bits? > Cygwin maps Windows ACLs into Posix permissions bits, but not 1-1; consequently, you can't assume that setting the permissions bits and then reading them back will necessarily produce the same results. Therefore, any test that depends on that property should be skipped altogether. > > > felix > > >
Re: chicken 5.3.0 - improving POSIX test on Cygwin platform
> Bonjour, > > Currently, Chicken Scheme 5.3.0 builds without problem on Windows 10 Home > (21H2 64-bit) with a recently updated Cygwin64. > > The check fails during the POSIX test when testing file system permissions. > This failure is expected, but the check process dies. The error is farther > below. > > There are already conditional statements in posix-tests.scm to handle other > Windows differences. Could some familiar with the checking system add a > conditional to handle this expected failure more gracefully. Hi! Sorry for the overly late reply. I'm not too familiar with cygwin, what should the tests report here? The cond-expand for "windows" should trigger on cygwin, how is it handling the permission bits (as compared to "raw" Windows systems)? Does it "fake" the normal UNIX permission bits? felix
chicken 5.3.0 - improving POSIX test on Cygwin platform
Bonjour, Currently, Chicken Scheme 5.3.0 builds without problem on Windows 10 Home (21H2 64-bit) with a recently updated Cygwin64. The check fails during the POSIX test when testing file system permissions. This failure is expected, but the check process dies. The error is farther below. There are already conditional statements in posix-tests.scm to handle other Windows differences. Could some familiar with the checking system add a conditional to handle this expected failure more gracefully. Merci. Error: (posix-tests.scm:127) assertion failed: (equal? (file-permissions "posix-tests.out") exp-perm) Call history: posix-tests.scm:84: chicken.file.posix#directory? posix-tests.scm:87: chicken.process-context#set-environment-variable! posix-tests.scm:88: chicken.process-context#get-environment-variable posix-tests.scm:89: chicken.process-context#unset-environment-variable! posix-tests.scm:90: chicken.process-context#get-environment-variable posix-tests.scm:127: chicken.file.posix#file-creation-mode posix-tests.scm:127: permission-expectation posix-tests.scm:127: ##sys#setter posix-tests.scm:127: g731 posix-tests.scm:127: delete-maybe-readonly-file posix-tests.scm:108: chicken.file#file-exists? posix-tests.scm:111: chicken.file#delete-file* posix-tests.scm:127: chicken.file.posix#file-open posix-tests.scm:127: chicken.file.posix#file-close posix-tests.scm:127: chicken.file.posix#file-permissions posix-tests.scm:127: ##sys#error<-- make: *** [rules.make:1015: check] Error 70 -- Claude Marinier
