Using nested reports in validphys appears to shift critical error from compile time to run time

Created by: wilsonmr

I've been playing with closure reports and noticed some strange behaviour which I think is unexpected, but perhaps I'm doing something stupid with the input. There might be a shorter minimal (not) working setup but I think this demonstrates the issue (I can't upload files here):

https://drive.google.com/open?id=14FwLAzdTFrmkyN9zTi93TGDMJQlfkdlD

If you run validphys test2.yaml there will be a critical error raised at compile time however if you run validphys test1.yaml there will be a critical error at run time. AFAICT The run cards should be equivalent, however test1.yaml has the nested report structure.

Side note: I'm suprised that there are issues with running this