Hi Dean et al,
Could we please remove the path length limitation referred to in this patch -- the path-to and binary-name of xray logfiles are implicitly truncated to 128 chars each. We've run into some (localized) trouble:
- r343295 [0] caused the path that an xray logfile is written to, for one test, to be substantially longer
- The log-file-opening code effectively limits the path to xray logfiles to ~128 characters
- On our local test setup, the path ends up being 135 characters.
- This kills the test
The net effect of the "HalfLength" limitation is that fdr-thread-order.cc writes its logfile in a higher level directory, later failing the test because the output can't be found. The purpose of this limitation isn't clear to me, and it seems much more beneficial to let, on error, the code fall through to the "name too long" code path, which reports something useful instead of silently dropping a file somewhere else.