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
I say "supposed" because the differences are only skin-deep: The new versions (+) resolve through an alias to match the baseline versions (-) exactly.
There may be reasons it is the way it is, but I feel like it'd be better for such situations to not count as diffs. I think this could be accomplished by using os.path.realpath() somewhere in _normalize_string_value(). Although looking at that code, I see that os.path.basename() is used, so maybe I'm misunderstanding what's happening where.
The text was updated successfully, but these errors were encountered:
This does have to do with softlinks. The underlying reason it came up was that I was inadvertently overriding $CESMDATAROOT in my startup files (from way in the past). Now, I've stopped doing that so we aren't likely to see it anymore. This was on Derecho and not that long ago though.
So it's a good change to make, but might not be worth it. Also you could argue that the components that come up with the namelist filenames is the place where this should be corrected. The problem there is it has to be done in each component. If this was easy to do in cime it would allow it to be done in one place.
When comparing a test to a baseline generated by a different user, I ran into the following supposed diff in our namelists:
I say "supposed" because the differences are only skin-deep: The new versions (
+
) resolve through an alias to match the baseline versions (-
) exactly.There may be reasons it is the way it is, but I feel like it'd be better for such situations to not count as diffs. I think this could be accomplished by using
os.path.realpath()
somewhere in_normalize_string_value()
. Although looking at that code, I see thatos.path.basename()
is used, so maybe I'm misunderstanding what's happening where.The text was updated successfully, but these errors were encountered: