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.

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

Better logging #84

Open
grzanka opened this issue Jul 18, 2017 · 4 comments
Open

Better logging #84

grzanka opened this issue Jul 18, 2017 · 4 comments
Milestone

Comments

@grzanka
Copy link
Collaborator

grzanka commented Jul 18, 2017

Should include:

  • a way to reproduce worskspace generation (i.e. record the command generatemc and all its switches user executed)
  • time and date
  • username and hostname
  • current directory

Logging should also be generated with submit.sh and collect.sh script.

@antnieszka antnieszka added this to the Next release milestone Aug 28, 2017
@antnieszka
Copy link
Contributor

#85

@grzanka
Copy link
Collaborator Author

grzanka commented Aug 29, 2017

Basic features seems to be implemented.
We also need an information about jobs execution:

  • which jobid was generated by queueing system

More advanced:

  • when first job started to be executed
  • when last job stopped its execution

Probably the best way would be to modify the bash script templated.
https://github.com/DataMedSci/mcpartools/tree/master/mcpartools/scheduler/data

logfile path can be injected as other template items.

@antnieszka
Copy link
Contributor

Maybe job submission time could be logged too? It might be useful in the future.

@grzanka
Copy link
Collaborator Author

grzanka commented Sep 2, 2017

@ant6 I agree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants