SDK Logs/Downloads Throw Errors if Job Doesn't Run

[alexandermichels]

Expected Behavior

When a job fails, we should not display "Job Completed" and we should not attempt to view/download logs or results, but instead notify the user that the job did not run, with a reason why it did not run, and next steps (run again, who to contact, etc.).

Actual Behavior

If a job is unable to run, the SDK says that the job is completed, attempts to view the logs, and throws errors. I assume a similar error will also occur if we try to download results automatically.

The message says that the job completed, we should check the events to see if that's actually true.

I assume this same issue comes up with Download Results and automatic download.

Steps to Reproduce the Problem

1. Run a job that doesn't run due to malformed HPC configs.

[alexandermichels]

Use hello_world_half_hour on the "cgjobsup-dev.cigi.illinois.edu" server to test this out