From ec66ae2f6fd79e62afcd6a0989bf1737d69cf230 Mon Sep 17 00:00:00 2001 From: Sergei Trofimov Date: Fri, 11 May 2018 14:41:53 +0100 Subject: [PATCH] instrument/trace_cmd: Log the pulling of trace Extracting trace and pulling the trace file from the target can take a relatively long time, as the trace file can be tens, and even hundreds, of MB. Add an info-level log message to inform the user why WA execution appears to have paused for a few seconds. --- wa/instruments/trace_cmd.py | 1 + 1 file changed, 1 insertion(+) diff --git a/wa/instruments/trace_cmd.py b/wa/instruments/trace_cmd.py index f5190300..d008e216 100644 --- a/wa/instruments/trace_cmd.py +++ b/wa/instruments/trace_cmd.py @@ -201,6 +201,7 @@ class TraceCmdInstrument(Instrument): self.collector.stop() def update_output(self, context): # NOQA pylint: disable=R0912 + self.logger.info('Extracting trace from target...') outfile = os.path.join(context.output_directory, 'trace.dat') self.collector.get_trace(outfile) context.add_artifact('trace-cmd-bin', outfile, 'data')