Closed ndkeen closed 1 week ago
This seems like a CIME issue. When CIME checks if all input data is present, it should also check the permissions, to ensure current user can at least read.
Yea I was wondering if it was just CIME. However, I don't recall seeing this type of error with vanilla e3sm -- guess I could try to test it. Now if CIME isn't going to change, is there a way we can do our own checking before runtime?
I've already fixed the permissions on the file.
Yeah, I think we can check the permissions, during buildnml in eamxx. The best we can do is error out though: no way to force new download, which would fail anyway since we can't overwrite the file.
@ndkeen this was quite easy to do, so I just went ahead and I did it. See linked PR.
Also, congrats on opening issue 3000!
A user outside of e3sm group was trying a case and hit this runtime error:
I'm trying to change the permissions on the file (as Ben on vacation, I need to ask NERSC to change owner), but I would think we would not want this to be a runtime error -- as user could have waited quite a while in the Q.
Currently: