Weird issue with release directory not being created

[Ryan Carmelo Briones]

So yesterday I upgraded to capistrano 2.5.11 (for the mkmf removal) at
the same time as moving our SCM from svn to git and I experienced a
very weird issue: the release directory, on some occasions was not
being created with zero errors in the capistrano output. I say "some"
because a subsequent deploy seemed to fix the problem. Today the same
problem happened again, but this time a second deploy didn't fix it.
After some server hackery, a downgrade to cap 2.5.10 and another
deploy I started spelunking through the code for changes between
2.5.10 and 2.5.11. The only thing I could find that looked promising
was 92941e855d70a5778eb094a972fdf43c70802b95 (http://github.com/
capistrano/capistrano/commit/
92941e855d70a5778eb094a972fdf43c70802b95). I say promising because
this is the output of both versions of the `ls`, mimicking
"current_release" on the server in question:

irb(main):003:0> `ls -xt /var/www/apps/gldl/
releases`.split.reverse.last
=> "20091230170408"
irb(main):004:0> `ls -x /var/www/apps/gldl/
releases`.split.reverse.last
=> "20091228205912"

The one using `ls -xt` is correct, the `ls -x` is incorrect. I didn't
submit a bug in lighthouse because I'm not sure how this commit really
affects this process. Hope this is helpful to the development process.
I'd be willing to test no-deployment/destructive changes if need be.
Thanks!

$ uname -a
Linux [REDACTED] 2.6.18-92.1.6.el5xen #1 SMP Wed Jun 25 14:13:10 EDT
2008 x86_64 x86_64 x86_64 GNU/Linux
$ ruby -v
ruby 1.8.6 (2008-08-11 patchlevel 287) [x86_64-linux]
Ruby Enterprise Edition 20090610

-- Ryan Briones

[Lee Hambley]

Ryan,

Thanks for the report, I'll look into this as soon as I get a minute :) have a good new year!

-- Lee Hambley

Twitter: @leehambley | @capistranorb