You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, this does stem from #3053. In that PR, I made it so whatever was in the CI YAML would be overridden by the workflow/hosts machine YAML. This allowed for features that were not supported on a machine to be disabled, even if it is explicitly enabled in the CI test (such as METplus or the TC tracker).
I will need to think about how to reconcile this to allow users to influence assignments.
What is wrong?
One used to be able to do something like:
and it would replace all the ACCOUNT information with
da-cpu
that is no longer the case, it's insteadfv3-cpu
What should have happened?
HPC_ACCOUNT=da-cpu
should fill inda-cpu
where appropriateWhat machines are impacted?
All or N/A
What global-workflow hash are you using?
1ba8985
Steps to reproduce
See above
Additional information
No response
Do you have a proposed solution?
No response
The text was updated successfully, but these errors were encountered: