Guilhem's notes:
Terminating process of command [git, blame, c, --abbrev=7, 6e5cdd9d, -, … due to timeout 30 seconds
Non-zero exit status 143 from command [git, blame, -c, --abbrev=7, 6e5cdd9d, …
and 10s later:
19:57:34 <@guilhem> I guess this should be raised a bit
19:57:57 <@guilhem> tried it some weeks ago but the settings seemed ignored
19:58:09 <@guilhem> will do more research
Looking at the source, I now understand why setting <void property="commandTimeout"/> had no effect here: there are two timeout settings: "commandTimeout", and "interactiveCommandTimeout", cf.
https://github.com/oracle/opengrok/blob/1.1.2/opengrok-indexer/src/main/java/org/opengrok/indexer/configuration/Configuration.java#L352
and for whatever reason the forking git-blame(1) processes use the interactive flavor…
https://github.com/oracle/opengrok/blob/1.1.2/opengrok-indexer/src/main/java/org/opengrok/indexer/history/GitRepository.java#L443
Both are now set to 120s. A quick benchmark on a couple of random files suggests that it should be more that enough for core (these processes seem to take 25 to 35s at the moment, hence the unreproducible nature of this issue).