If we call burning with only existing instance, then it will fail to
create any of them, and thus in the removal phase it won't have anything
to remove. Since calling luxi.SUBMIT_MULTIPLE_JOBS with an empty job set
is an error (and will raise an exception), this creates a very strange
error in burnin (which is unfortunatelly hiden by ExecJobSet()).

As such, we modify CommitQueue to return immediately if it has an empty
op queue.
---
 Should we maybe log this as a warning?

 tools/burnin |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/tools/burnin b/tools/burnin
index ae18f30..e5cce50 100755
--- a/tools/burnin
+++ b/tools/burnin
@@ -375,7 +375,7 @@ class Burner(object):
 
   def CommitQueue(self):
     """Execute all submitted opcodes in case of parallel burnin"""
-    if not self.opts.parallel:
+    if not self.opts.parallel or not self.queued_ops:
       return
 
     if self.queue_retry:
-- 
1.7.1

Reply via email to