-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rerunning link_workflow.sh generates gdas fix error #1100
Comments
The following change to
Executing
|
Another error noted in
The two extra whitespace trace back to the initial commit of
yields a functional link in |
Thanks for these fixes @RussTreadon-NOAA ! I've tested it myself as well and confirm the error and resulting fix works (including the dead link and its fix). I will initiate a PR to get these fixes into |
Fix 1: When link_workflow.sh is rerun an error occurs: -bash-4.2$ ./link_workflow.sh ./link_workflow.sh completed successfully -bash-4.2$ ./link_workflow.sh ln: failed to create symbolic link 'bump/20220805': Permission denied ./link_workflow.sh encounted an error at line 184 (rc=1) Update link_workflow.sh gdas section to remove the subfolder symlinks if they already exist before trying to make them. Error goes away now. Fix 2: Dead symlink for a GSI monitoring file under /fix/gdas Two extra whitespaces in link_workflow.sh cause a dead link. Remove the whitespaces and link is created correctly. Refs #1100
Expected behavior
Reruns
./link_workflow.sh
should complete without error.Current behavior
Rerunning
./link_workflow.sh
returns an error as shown belowMachines affected
Only tested on Hera but may occur on other machines.
To Reproduce
cd sorc
./checkout.sh -u
./build_all.sh
./link_workflow.sh
./link_workflow.sh
The second execution of
./link_workflow.sh
will generate an error.Context
It is not uncommon for a developer change of a g-w component to necessitate relinking files.
Additional Information
If the gdas fix section of
./link_workflow.sh
is commented out, reruns of./link_workflow.sh
complete without error.The text was updated successfully, but these errors were encountered: