New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 808230 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 808174
Owner:
Last visit > 30 days ago
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Wifi performance tests are failing to run netperf command.

Project Member Reported by aashuto...@chromium.org, Feb 1 2018

Issue description

Tests from wifi_perf suite are failing to run netperf command (Exit status: 143).

More logs @
https://stainless.corp.google.com/search?view=matrix&row=queued_date&col=board&first_date=2018-01-26&last_date=2018-02-01&suite=wifi_perf&reason=Unhandled+AutoservRunError%3A+Timeout+encountered%3A+%2Fusr%2Fbin%2Fssh&exclude_cts=true&exclude_not_run=true&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true


Sample failure:
Unhandled AutoservRunError: Timeout encountered: /usr/bin/ssh -a -x -o Protocol=2 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -l root -p 22 chromeos15-row1-rack7-host1 "export LIBC_FATAL_STDERR_=1; if type \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\" \"server[stack::run_once|run|run] -> ssh_run(/usr/local/bin/netperf -H 192.168.0.254 -p 12865 -t UDP_STREAM -l 10 -- -P 0,12866)\";fi; /usr/local/bin/netperf -H 192.168.0.254 -p 12865 -t UDP_STREAM -l 10 -- -P 0,12866"

 

Comment 1 by kirtika@google.com, Feb 2 2018

Mergedinto: 808174
Status: Duplicate (was: Untriaged)

Sign in to add a comment