se-wgs-variation: convert asserts to list form (blocked by bcftools concat SIGSEGV)#1277
se-wgs-variation: convert asserts to list form (blocked by bcftools concat SIGSEGV)#1277jmchilton wants to merge 1 commit into
Conversation
YAML collapses duplicate mapping keys (last wins), so repeated has_text entries only ran the last assertion per type. Convert to list form so each runs. Isolated from the passing-subset PR: this workflow's test currently ERRORS for a reason unrelated to this change — bcftools concat segfaults (SIGSEGV, rc -11) inside lofreq_call's biocontainer while combining empty VCF chunks. IWC only tests changed workflows, so touching this file is what surfaced the pre-existing crash. Kept separate so it doesn't block the genuinely-green set. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Test Results (powered by Planemo)Test Summary
Errored Tests
|
Root cause found + upstream fix filedThe red here is not the assert conversion — it's a pre-existing crash this workflow surfaces (IWC only tests changed workflows). Tracked it all the way down: Chain: Why: it's a bcftools regression — samtools/bcftools#2286, "bcftools concat segfault if VCF files contain only headers." Present in 1.21, fixed in 1.22. The pinned Verified in the shipped container (
Fix filed upstream: bioconda-recipes PR bioconda/bioconda-recipes#67152 — pins Once that merges and the lofreq package rebuilds with bcftools ≥1.22, this workflow's |
Summary
Convert the
se-wgs-variationasserts:blocks from duplicate-keyed dict form to list form so every assertion runs (same fix as the passing-subset PR). Split out on its own because the test currently errors for a reason unrelated to this change, and I didn't want it dragging the green set red.Why this is red (not our change)
IWC CI only tests changed workflows, so editing this test file is what caused
se-wgs-variationto run at all — surfacing a pre-existing crash:rc -11= SIGSEGV.bcftools concatsegfaults insidelofreq_call's biocontainer while combining the (empty — "0 tests performed", "idxstats reports no reads mapped") VCF chunks. That's a Galaxy job-level crash, upstream of anything the test YAML does — the assertion conversion cannot cause it. The workflow errors before assertions are ever evaluated, so this change can't be green-validated until the crash is resolved.Tracking
bcftools concatSIGSEGV is biocontainer/version-specific or a broader environment regression (it may affect other bcftools/lofreq workflows — only changed ones get tested, so it's under-reported)Do not merge while red — this PR is a holding place for the assertion fix + a paper trail on the crash.