-
Notifications
You must be signed in to change notification settings - Fork 353
Known Limitation: PF Unit test subgrid hierarchy isn't filled out #3931
Copy link
Copy link
Open
Labels
closed: wontfixWe won't fix this issue, because it would be too difficult and/or isn't important enough to fixWe won't fix this issue, because it would be too difficult and/or isn't important enough to fixdevopsDevelopment Operations to improve development throughput, E.g., adding GitHub WorkflowsDevelopment Operations to improve development throughput, E.g., adding GitHub Workflowstest: PFUNITPass FUNITCTSM tests before mergingPass FUNITCTSM tests before mergingtestingadditions or changes to testsadditions or changes to tests
Milestone
Metadata
Metadata
Assignees
Labels
closed: wontfixWe won't fix this issue, because it would be too difficult and/or isn't important enough to fixWe won't fix this issue, because it would be too difficult and/or isn't important enough to fixdevopsDevelopment Operations to improve development throughput, E.g., adding GitHub WorkflowsDevelopment Operations to improve development throughput, E.g., adding GitHub Workflowstest: PFUNITPass FUNITCTSM tests before mergingPass FUNITCTSM tests before mergingtestingadditions or changes to testsadditions or changes to tests
For the PF unit tests of the Fortran code the subgrid structure is typically only filled out for the subgrid level of interest. For example for patch arrays only for patches. So it won't necessarily have proper mapping for gridcells. Landunits, and columns. Some unit tests populate more than one layer, but most do not populate all layers.
This can matter if you expect all layers to be populated. For example if you use the point option to endrun to write information on all layers.