about summary refs log tree commit diff
path: root/test/python/test_version.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-09 20:38:35 +0000
committerPjotr <wrk@bosa.lan>2026-11-09 20:38:35 +0000
commitdc3e0e5ba0fa6f9462d55e9ca9a4802a60eb205f (patch)
treef154549bf81ce0c0d588e4c37e6ad8c7dc80845d /test/python/test_version.py
parent832bf0a6f3961b7ad43635d5770939acba55fb7b (diff)
downloadgenenetwork4-dc3e0e5ba0fa6f9462d55e9ca9a4802a60eb205f.tar.gz
gemma: quote GEMMA's own error, not the wrapper's banner
Every GEMMA failure the sweep produced read the same way -- "gemma-wrapper
bailed out with pid ... exit 1", sometimes with the Ruby backtrace -- which
says nothing about whether the API or the panel is at fault. The line that
does is GEMMA's, printed in the middle of the wrapper's per-chromosome
chatter:

  ERROR: Enforce failed for N>0 in src/fastblas.cpp at line 194 in fast_cblas_dgemm

so `CommandFailed` now carries the last GEMMA diagnostic (an `ERROR`,
`error!`, `****` warning, `Enforce failed` or "not enough" line) rather than
the raw stderr, falling back to the wrapper's own tail when GEMMA said
nothing at all. The wrapper's banner and `.rb:` backtrace lines are skipped:
they are the noise this exists to get past.

Two tests: the complaint is GEMMA's line, not the banner; and a silent
failure still names something.
Diffstat (limited to 'test/python/test_version.py')
0 files changed, 0 insertions, 0 deletions