Skip to content

A Fortran error stop in the f2py reference kills the run: no report, no summary #21

Description

@chenyueqi

The reference module built by `f2py-golden-flat` runs in the engine's own process. CLUBB's `interpolation.F90` has four `error stop` statements on invalid grid indices; when `differential.bitexact` samples an input that reaches one, the Fortran runtime terminates the interpreter with exit status 1. Nothing after that happens: the verdicts recorded so far stay on disk, but the report is never printed, `--summary` is never written, and the exit status is indistinguishable from a gate failure. Reproduced on `translate-clubb` over 14 tier-0 units with `fortran:interpolation` last in the list -- the whole run's report vanished.

Proposal: run the reference (or the whole comparison for a subprogram) in a child process, and record `candidate raised`-style verdicts for the reference side too (`reference aborted: error stop`), so a Fortran abort is a comparison that could not be made rather than the end of the run.

Found 2026-09-03 running the recast-clubb extension's tier-0 units (CLUBB_core of larson-group/clubb_release at 8ab3902).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:verifierthe gates: static.rwset, differential.bitexact/tolerance, oraclesbugSomething isn't workingfound-by:clubbsurfaced by the recast-clubb extension on CLUBB_core

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions