All that appears to show is that while the spark driver was waiting for the job to finish, it got interrupted. That generally means someone/something interrupted the process using the signal API call/kill command line action, or a control-C action. There's no other information in that trace, I'm afraid