ukaea / ukaea/PROCESS

[BUG] `run-tracking-inputs` passing when a regression file has failed to run

Open
#3,806 2 comments 0 reactions 2 assignees View on GitHub

@timothy-nunn is already working on this.

Since Aug 21, 2025.

CI
Dominant language
Python
Stars
71
Forks
27
Avg merge
2d 18h
Merged PRs (30d)
33

Description

Describe the bug

Image

The regression tests failed to run as part of the run-tracking-inputs job on a PR: https://github.com/ukaea/PROCESS/actions/runs/17123518609/job/48571670054

However, the run-tracking-inputs job was reported as succeeding despite this. This caused regression test failures on main because the test assets were not updated accordingly (due to the error in running PROCESS in the run-tracking-inputs job) and so the references mfiles were not correctly updated in time for the regression test job. The regression test job used the previous regression test assets instead, resulting in regression test failures on main as the references MFILEs were not updated to reflect the variable name changes in the merged PR.

Steps to reproduce

Expected behaviour

The run-tracking-inputs job should fail if PROCESS has failed to run on any of the regression input files, instead of showing as passed in the CI and using out of date reference mfiles.

Evidence

Environment

  • OS:
  • Version:

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.