Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Account value not being saved in configuration files #11

Closed
coleslaw481 opened this issue Jan 12, 2017 · 1 comment
Closed

Account value not being saved in configuration files #11

coleslaw481 opened this issue Jan 12, 2017 · 1 comment
Assignees
@coleslaw481
Labels
bug
Milestone
0.5.1

Comments

@coleslaw481
Copy link
Contributor

For Comet and rocce cluster the runjobs.CLUSTER and runmerge.CLUSTER files are generated once by createchmjob.py which sets the account value from --account flag.

For Gordon cluster this value is lost since runjobs.gordon and runmerge.gordon is re-written when checkchmjob.py --submit is invoked. To remedy this the account value needs to be stored in a configuration file so it can be loaded into CHMConfig.
@coleslaw481 coleslaw481 self-assigned this Jan 12, 2017
@coleslaw481 coleslaw481 added this to the 0.5.1 milestone Jan 12, 2017
coleslaw481 added a commit that referenced this issue Jan 12, 2017
@coleslaw481
fixes for issue #12 involving update of checking job status for gordo…
20e65ff 
…n and issue #11 which deals with account value not being saved in configuration which is needed for gordon job submissions since the run*gordon files are rewritten by checkchmjob.py --submit
@coleslaw481
Copy link
Contributor Author

Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@coleslaw481 coleslaw481

Labels
bug
Projects
None yet
Milestone
0.5.1
Development

No branches or pull requests
1 participant
@coleslaw481