On Feb 21, 2011, at 1:00 AM, Mike Dubman wrote:
> Mercurial uses "Copytree" to copy fresh checked-out copy to the build
> location.
This statement threw me for a little while; I had to go to the code to figure
it out. It's not Mercurial.pm that uses copytree; it looks like SCM.pm sets up
a po
Mercurial uses "Copytree" to copy fresh checked-out copy to the build
location.
These are messages coming from mtt during problematic situation:
Debug message stating that post-copy completed (should be applied AFTER copy
to the build location):
> >> copytree running post_copy command:
Debug mess
Hmm -- I'm having difficulty understanding the exact scenario here.
Are you using the Mercurial SCM module, or copytree?
I don't think that I have used the Mercurial SCM module before -- I believe
Ethan added that. Ethan -- does SCM/Mercurial work well for you?
On Feb 18, 2011, at 2:06 AM, M
1. post_copy fails because does not find some files which should be already
copied.
2. In the mtt debug output, (attached in original post) you can see that
"post_copy" is executed before "copytree" has finished.
>> copytree running post_copy command:
...
...
>> copytree finished copying
On Fri,
On Feb 10, 2011, at 2:36 PM, Mike Dubman wrote:
> There is a race condition in SCM, Mercurial module when used from MPI GET
> phase:
>
> - scm_post_copy hook can be started before MPI GET completed copy of fetched
> tree into install location.
How have you verified this?
> - This leads to mtt
