Mirror family does not turn complete

[uandrae]

What happened?

In the screenshort below the family Mirrors doesn't get complete after requeue in the suite feature_split_tests_intel_CY49t2_ALARO_DEMO_60x80_2500m_20260610. This has the consequence that the suite feature_split_tests_intel_CY49t2_ALARO_DEMO_60x80_2500m_20260610_ddh` will never start as it's triggered on the suite and not a specific task.

What are the steps to reproduce the bug?

Two suites where one mirrors the other and where the first is requeued should reproduce the problem.

Version

5.16

Platform (OS and architecture)

ECMWF ATOS

Relevant log output

Accompanying data

No response

Organisation

SMHI/ACCORD

[marcosbento]

Hi @uandrae, I understand the problem.

It seems that the state of the mirrored task is not being correctly propagated up the node tree.
I will investigate.

[marcosbento]

Hi @uandrae,

After further investigation, the "non-propagation" of the mirrored state up the tree was an intentional behaviour.

The goal at the time of implementation was exactly to avoid "polluting" the local suite marking it as aborted "simply" because the mirrored task aborted, since the use case we had in mind was to trigger directly from the mirrored task. However, in hindsight, perhaps doing the state propagation should have been the default behaviour, to simulate the local execution of the mirrored node as in your use case.

To circumvent this issue, we propose to consider an additional option --propagate to explicitly enable propagation. The default when this option is not provided would be not to propagate, but users like yourself can still opt-in to the propagation behaviour.

Please let us know your opinion.