sktm patchwork aborts if a Jenkins job has no junit results

[spbnick]

Even though sktm patchwork can submit any number of jobs in a single run,
it aborts with an exception if it detects a single of those jobs aborted:

[43632] 2018-04-16 04:17:14,039     INFO   submitted build: upstream #80
[43632] 2018-04-16 04:17:14,039     INFO   submitted patchset: ['https://patchwork.ozlabs.org/patch/897858']
[43632] 2018-04-16 04:17:16,839     INFO   submitted build: upstream #81
[43632] 2018-04-16 04:17:16,839     INFO   submitted patchset: ['https://patchwork.ozlabs.org/patch/897863']
[43632] 2018-04-16 04:17:20,333     INFO   submitted build: upstream #82
[43632] 2018-04-16 04:17:20,333     INFO   submitted patchset: ['https://patchwork.ozlabs.org/patch/897892']
[43632] 2018-04-16 04:24:26,006     INFO   job completed: jjid=53; type=1
[43632] 2018-04-16 04:24:26,863     INFO   build_status=ABORTED
Traceback (most recent call last):
  File "/home/skt/sktm/sktm.py", line 129, in <module>
    sw.wait_for_pending()
  File "/home/skt/sktm/sktm/__init__.py", line 275, in wait_for_pending
    self.check_pending()
  File "/home/skt/sktm/sktm/__init__.py", line 218, in check_pending
    bres = self.jk.get_result(self.jobname, bid)
  File "/home/skt/sktm/sktm/jenkins.py", line 143, in get_result
    build.get_status()))
Exception: No results for build 53 (ABORTED)

Instead it should note the job result and continue waiting for the rest of the
jobs.

[spbnick]

This also happens if the Jenkins job aborts before skt has a chance to run, e.g. on installing skt.

[spbnick]

This would likely need an update to the build status enum, along with database update.