3 subject="""comment 3"""
4 date="2020-10-06T14:30:42Z"
6 Looks like this time it was a git-annex info --batch. And none of
7 the child processes look unusual like what you showed before,
8 it's the usual collection of git cat-file.
10 lr-x------ 1 test test 64 Oct 6 10:27 /proc/896711/fd/0 -> 'pipe:[190817413]'
11 l-wx------ 1 test test 64 Oct 6 10:44 /proc/896825/fd/7 -> 'pipe:[190817413]'
13 The git-annex process's stdin is still connected to a pipe, the other end of
14 which datalad still has open for write. So there's no reason for git-annex to exit,
15 it's still waiting for batch requests.
17 datalad_crawler.nodes.tests.test_annex.test_annex_file('full',) ... [WARNING] Caught Command '['git', '-c', 'annex.merge-annex-branches=false', 'annex', 'info', '--bytes', '--json', '--json-error-messages', '--batch']' timed out after 3.0 seconds [subprocess.py:_wait:1616] on trial #1. Sleeping 1.000000 and retrying
18 [WARNING] Caught Command '['git', '-c', 'annex.merge-annex-branches=false', 'annex', 'info', '--bytes', '--json', '--json-error-messages', '--batch']' timed out after 3.0 seconds [subprocess.py:_wait:1616] on trial #2. Sleeping 1.000000 and retrying
20 3 seconds? Are you sure this is the same problem? Or that this is a problem at
21 all? git-annex info could take longer than 3 seconds if you ask it for
22 info on a directory, or if it needs to merge the git-annex branch,
23 or maybe in other circumstances.
25 Getting the feeling the problem may be in your test machinery..