diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-11 16:31:44 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-11 16:31:44 +0000 |
| commit | 0751e56b5f56bca61b3599c0a96cfc5f0fd30f32 (patch) | |
| tree | 4574f734c4d6f3a9b7af532d8495ae02e6228bd7 /test/python | |
| parent | fd7234a68c0a03925cdf5d678d7b76b97e815617 (diff) | |
| download | genenetwork4-0751e56b5f56bca61b3599c0a96cfc5f0fd30f32.tar.gz | |
bulklmm: report Julia's error line, not its last line
A failing scan came back as
BulkLMM failed: in expression starting at scripts/bulklmm_scan.jl:26
which names neither the package nor the reason. Julia had said it plainly,
two lines up:
ERROR: LoadError: ArgumentError: Package CSV not found in current path.
- Run `import Pkg; Pkg.add("CSV")` to install the CSV package.
The complaint finder looked for a line starting "Error" -- Julia writes
"ERROR:" -- and fell back to the last non-empty line, which is the line
number. That is the same defect as gemma-wrapper's Ruby backtrace, in our
own error handling: the wrapped tool said why, and we threw it away.
julia_complaint takes the first ERROR:/LoadError line plus Julia's hint
line when there is one, with the last line kept only as a fallback for a
driver that fails silently. Three unit tests cover the three shapes.
The integration tests also stop failing on a half-instantiated Julia
project: bulklmm_available used to accept any directory with a
Project.toml, and /tmp/gj-env has one naming BulkLMM and nothing else, so
the scan died on `using CSV` instead of skipping. It now requires the
project to name the three packages the driver loads, which is what a
usable env is.
Diffstat (limited to 'test/python')
0 files changed, 0 insertions, 0 deletions
