clustericious / Yars

Yet-another ARchive Service
5 stars 2 forks source link

intermittent failure in t/060_mark_down.t #5

Closed plicease closed 10 years ago

plicease commented 10 years ago

I haven't personally reproduced this, but examples include:

http://www.cpantesters.org/cpan/report/014a93f5-6cbb-1014-8319-0293f03158fb http://www.cpantesters.org/cpan/report/da479493-7265-1014-af27-8db75cf4dae8 http://www.cpantesters.org/cpan/report/6be0fd4a-2502-11e3-b79c-468f7fb60443 http://www.cpantesters.org/cpan/report/fd6414c0-1380-11e3-9af5-7ada6602b1db http://www.cpantesters.org/cpan/report/de33d5e6-1334-11e3-b8ea-16a6aae6ca2d http://www.cpantesters.org/cpan/report/127293da-14fa-11e3-acca-e2a3b3fe1846 http://www.cpantesters.org/cpan/report/77c65220-12a3-11e3-8605-28dd6264a920 http://www.cpantesters.org/cpan/report/5955e63e-14ec-11e3-9044-ee2eabe17584 http://www.cpantesters.org/cpan/report/9945e5e2-1338-11e3-9891-33f425e5b994

plicease commented 10 years ago

Interesting but on Cygwin chmod 555 doesn't seem to actually make a directory read-only.

fs01% dir -d
dr-xr-xr-x+ 1 ollisg None 0 Oct  4 05:31 ./
fs01% touch x
fs01% dir
total 0
-rw-r--r-- 1 ollisg None 0 Oct  4 05:33 x

tricky to detect this behavior, since the chmod is succeeded (and is successful, the mode of the file does change) it is just meaningless on Cygwin I guess.

plicease commented 10 years ago

This may have been fixed by the new more aggressive upness checker. can reopen if it resurfaces.