framework/execution: fix TargetManager termination

- Make sure TargetManager.finalize() actually gets called at the end
  of the run.
- Overrule the "diconnect" parameter behavior for gem5 and make sure it
  always disconnects. This necessary for stats to be generated properly.

wa/framework/execution.py

@@ -138,6 +138,9 @@ class ExecutionContext(object):
         self.output.write_state()
         self.output.write_result()
 
+    def finalize(self):
+        self.tm.finalize()
+
     def start_job(self):
         if not self.job_queue:
             raise RuntimeError('No jobs to run')
@@ -296,6 +299,7 @@ class Executor(object):
         runner = Runner(context, pm)
         signal.send(signal.RUN_STARTED, self)
         runner.run()
+        context.finalize()
         self.execute_postamble(context, output)
         signal.send(signal.RUN_COMPLETED, self)
 

wa/framework/target/manager.py

@@ -56,8 +56,8 @@ class TargetManager(object):
             self.rpm = RuntimeParameterManager(self.target)
 
     def finalize(self):
-        self.logger.info('Disconnecting from the device')
-        if self.disconnect:
+        if self.disconnect or isinstance(self.target.platform, Gem5SimulationPlatform):
+            self.logger.info('Disconnecting from the device')
             with signal.wrap('TARGET_DISCONNECT'):
                 self.target.disconnect()