Skip to content

Conversation

pabelanger
Copy link
Contributor

The git.cmd.execute function has the ability to use the
kill_after_timeout variable, however currently the clone function has
as_process hardcoded to True.

If progress is None, we can likley rely directly on git.cmd.execute()
for process handling, which then exposes kill_after_timeout properly.

Signed-off-by: Paul Belanger pabelanger@redhat.com

The git.cmd.execute function has the ability to use the
kill_after_timeout variable, however currently the clone function has
as_process hardcoded to True.

If progress is None, we can likley rely directly on git.cmd.execute()
for process handling, which then exposes kill_after_timeout properly.

Signed-off-by: Paul Belanger <pabelanger@redhat.com>
@pabelanger
Copy link
Contributor Author

I am not sure about the failures in AppVeyor, they don't look related

@Byron
Copy link
Member

Byron commented Oct 7, 2017

Thanks for your contribution.
To me it looks like if there is no progress, the function will not wait anymore for the clone to be finished. This, however, is a requirement, the function is expected to be synchronized.
Even though I would think that some tests should fail (on travis) if there is a problem, I would feel more comfortable if there would be a test that explicitly verifies this requirement.
What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants