Add try-except propagation status fails

[jwokaty]

I tested on jetstream by removing some files in public_html/3.17/bioc/nebbiolo1/buildsrc and the end of run file. It sends a message to maintainers from [email protected] with the subject "[BBS] PostRun Failed" and the following content:

    Postrun failed on the BBS with the following error:
    Error: Command '/home/biocbuild/bbs-3.17-bioc/R/bin/Rscript -e "source('/home/biocbuild/BBS/utils/makePropagationStatusDb.R');makePropagationStatusDb('OUTGOING','file://home/biocpush/PACKAGES/3.17/bioc',db_filepath='PROPAGATION_STATUS_DB.txt')"' returned non-zero exit status 1.

Would it be possible to split this from the other scenario because this could be useful as the other might take a little time to understand?

Close #297

[hpages]

Nice!

Why not send from the same address than the other emails sent by BBS? ([email protected])

Also maybe make the subject line more informative so we know immediately where to go for the troubleshooting e.g. something like "postrun failed on nebbiolo1 for the 3.17 bioc builds". Replace "nebbiolo1" with BBSvars.node_hostname, "3.17" with BBSvars.bioc_version, and "bioc" with BBSvars.buildtype.

Thanks

[jwokaty]

@hpages Thanks, those are good ideas.

[hpages]

Small detail: the low-level bbs.* modules are usually imported before the higher-level BBS* modules. See BBS-notify.py for example.

[hpages]

Can we make sure the name of the machine shows up in the subject? Thanks

[jwokaty]

Sorry, I thought I had pushed this change while ago but I realized I had only pushed to my repository.

[hpages]

👍 ready to go