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

send the output result by email #55

Open
Trophime opened this issue Jun 4, 2018 · 3 comments
Open

send the output result by email #55

Trophime opened this issue Jun 4, 2018 · 3 comments

Comments

@Trophime
Copy link

Trophime commented Jun 4, 2018

Hi,
would it be possible to send the output by email at the end of the slurm script?

@Trophime
Copy link
Author

Trophime commented Jun 4, 2018

here is a way to do it.
Note it also contains a workaround for #49

email-output-patch.txt

@emepetres
Copy link
Contributor

@Trophime nice!

Could you create a pull request instead of a patch file?

Also, did you try your code? What happens if the "mail" command is not available in the HPC or not configured (these errors should be handled)?

@Trophime
Copy link
Author

Trophime commented Jun 5, 2018

I could create a PR but the logs of my branch contains a lot of meaningfull logs..
I don't know how to clean the git history... And I do not have much time to do it right now..

Next I've tried the code. It's working on cesga at least
Right now it doesn't handle any error... My guess if that if mail is not available
the slurm script will report an error... but as we are not able to see any "logs" in the portal,
the user will have no clue why it fails...

The only check we can do is to perform something like:

isMail=$(which mail)
if [ $isMail != "" ]; then ... else ... fi

The good way to check should be like with the def of HPC resource (like what I suggest for #51)

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

No branches or pull requests

2 participants