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
With the merge of #26554, I believe that util/buildRelease/testReleaseHelp is now the only script in our code base that uses csh rather than bash or python (check my work). This issue is to capture the desire to convert it to bash or python to get us completely onto those two scripting technologies.
The text was updated successfully, but these errors were encountered:
Good point, I didn't think to look for those, and was grepping on /csh due to too many false positives with simply csh.
[aside: Interesting that those tcsh-based tests didn't fail in the recent linux32 run where the csh-based tests did… I hadn't realized tcsh has become more predictably available than csh, where I think it used to be the opposite.]
@jabraham17 : Looking more closely, those tcsh scripts don't seem to be used by our testing system, which may explain why they didn't cause failures. I also don't (personally) have a problem with tcsh scripts existing in a test directory if they're not scripts we invoke as part of testing, so I think those could stay as-is.
I had no memory about pbs-aprun using tcsh. Checking that case, that's related to the expect script that's used to interact with the queuing system to determine when the job has completed. I think it could/should be updated to use bash and opened #26566 to capture this.
With the merge of #26554, I believe that
util/buildRelease/testReleaseHelp
is now the only script in our code base that uses csh rather than bash or python (check my work). This issue is to capture the desire to convert it to bash or python to get us completely onto those two scripting technologies.The text was updated successfully, but these errors were encountered: