Hi guys, I can't help myself, forgive this comment if its out of place.
On 6/27/07, Kristis Makris <[EMAIL PROTECTED]> wrote:
On Wed, 2007-06-27 at 04:20 -0700, Robert Hudson wrote: > It is possible that a bug in Test Director can be "locked" by some-one > updating it. This means that when we do a commit the "read" checks in > the pre-commit hook pass OK, but then when the post-commit hook tried > to "update" the bug it fails to get the write lock required and so it > doesn't get the updates. Are you saying that the lock changes between the time the activity_verify is issued and the time the activity_commit is issued ? Or are you just saying that the activity_verify simply doesn't check for the lock ? > What I'd like to add is a new method called something like > "check_bug_lock" which can be called as part of the pre-commit hook to Let's call it "integration_bug_lock_available"
What's wrong with integration_bug_in_active_state? Isn't this just another thing that TestDirector.pm should handle? cheers, dim _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
