tree 79164ed314febc9b932c675be5b435d57e75cc09
parent 9a4a4cc5030ad28a2cb49109f9608220db45b49b
author Brian Norris <briannorris@chromium.org> 1535507036 -0700
committer chrome-bot <chrome-bot@chromium.org> 1538102660 -0700

[autotest] netperf_runner: filter out 'catcher: timer popped ...'

I see a smattering of reports like these across the lab:

  MIGRATED TCP MAERTS TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.0.254 () port 12866 AF_INET
  catcher: timer popped with times_up != 0
  Recv   Send    Send
  Socket Socket  Message  Elapsed
  Size   Size    Size     Time     Throughput
  bytes  bytes   bytes    secs.    10^6bits/sec

  87380  16384  16384    2.00      207.87

Because we expected results to be on exactly the 6th or 7th line, this
trips us up with an exception:

  Unhandled IndexError: list index out of range

Looking at the netperf code, it seems like this can happen if, e.g.,
netperf gets a SIGINT at the same time as its timer alarm. Possibly for
other reasons too. In any case, all the results I've seen still look
valid, so let's ignore that warning.

While we're at it, make this slightly less fragile by avoiding
memorizing line numbers, and instead only process numeric lines.

BUG=chromium:889556
TEST=network_WiFi_Perf

Change-Id: I7d3ce90019851e9370b42d3ba39ec6d8f0266457
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1246840
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Kirtika Ruchandani <kirtika@chromium.org>