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

Issue 814068 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocked on:
issue 810460



Sign in to add a comment

testRunRecordWprList failure on chromeos - vpython support needed

Project Member Reported by achuith@chromium.org, Feb 21 2018

Issue description

2/20 16:06:11.645 INFO |run_chromeos_tests:0052| [259/260] scripts_smoke_unittest.ScriptsSmokeTest.testRunRecordWprList failed unexpectedly 0.0289s:
02/20 16:06:11.646 INFO |run_chromeos_tests:0052|   Traceback (most recent call last):
02/20 16:06:11.648 INFO |run_chromeos_tests:0052|     File "/usr/local/telemetry/src/tools/perf/scripts_smoke_unittest.py", line 53, in testRunRecordWprList
02/20 16:06:11.659 INFO |run_chromeos_tests:0052|       venv=True)
02/20 16:06:11.661 INFO |run_chromeos_tests:0052|     File "/usr/local/telemetry/src/tools/perf/scripts_smoke_unittest.py", line 26, in RunPerfScript
02/20 16:06:11.662 INFO |run_chromeos_tests:0052|       stderr=subprocess.STDOUT, cwd=self.perf_dir)
02/20 16:06:11.663 INFO |run_chromeos_tests:0052|     File "/usr/local/lib64/python2.7/subprocess.py", line 710, in __init__
02/20 16:06:11.665 INFO |run_chromeos_tests:0052|       errread, errwrite)
02/20 16:06:11.666 INFO |run_chromeos_tests:0052|     File "/usr/local/lib64/python2.7/subprocess.py", line 1335, in _execute_child
02/20 16:06:11.667 INFO |run_chromeos_tests:0052|       raise child_exception
02/20 16:06:11.669 INFO |run_chromeos_tests:0052|   OSError: [Errno 2] No such file or directory

First failing build:
https://uberchromegw.corp.google.com/i/chromiumos.chromium/builders/amd64-generic-telemetry/builds/13996

Suspect:
https://chromium-review.googlesource.com/c/chromium/src/+/911808
 
Cc: -chiniforooshan@chromium.org ashleymarie@chromium.org
Actually it's this one:
https://chromium-review.googlesource.com/c/chromium/src/+/908710

The lines seem to be:
https://cs.chromium.org/chromium/src/tools/perf/scripts_smoke_unittest.py?l=52-53


Cc: nednguyen@chromium.org
Good catch achuith@
Is it possible to disable this test just for chromeos?
nednguyen@, any thoughts about what to do here?
I vote for disabling that test just for ChromeOS until the ChromeOS infra also use vpython.
sounds good - I can disable, thanks!
Cc: achuith@chromium.org
Labels: -Pri-2 Pri-3
Owner: ----
Summary: testRunRecordWprList failure on chromeos - vpython support needed (was: testRunRecordWprList failure on chromeos)
Project Member

Comment 7 by bugdroid1@chromium.org, Feb 22 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fda2b19ede3213537af744e87ec067ea45390da3

commit fda2b19ede3213537af744e87ec067ea45390da3
Author: Achuith Bhandarkar <achuith@chromium.org>
Date: Thu Feb 22 01:01:49 2018

Disable testRunRecordWprList on chromeos.

BUG=814068
TEST=None
TBR=nednguyen@google.com

Change-Id: I4b52a8b19e70b1e07754326abe8c6ea01a0ce03f
Reviewed-on: https://chromium-review.googlesource.com/929783
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538287}
[modify] https://crrev.com/fda2b19ede3213537af744e87ec067ea45390da3/tools/perf/scripts_smoke_unittest.py

Cc: cmt...@chromium.org
Components: Tools>ChromeOS-Toolchain
Not sure if this is a toolchain issue.
Cc: -cmt...@chromium.org llozano@chromium.org
Components: -Tools>ChromeOS-Toolchain Infra>Client>ChromeOS
this is not in my team's reponsibility. 
We don't have anything to do with vpython. 
Adding build/infra team. 
Blockedon: 810460
Status: Available (was: Untriaged)
Cc: bpastene@chromium.org
Labels: -Pri-3 Pri-2
Quick question Achuith: was the failed telemetry test in #0 running in local mode or server mode? (The link gives a 404, so kinda hard to tell from here.) If it's in local mode, then we'd probably have to expect vpython to already be available in the VM. But if it's in server mode, then the test can be reasonably expected to bring a vpython with it into the VM.
Owner: bpastene@chromium.org
Status: Assigned (was: Available)
Also, I can take this as part of my work in  bug 843279 .
It's running in local modes, so the vpython would need to be available in the VM.

This bug isn't super urgent. If we end up supporting telemetry unittests in server mode with the work you're doing, we can actually wind this bot down and stop running these tests.

Comment 15 by benhenry@google.com, Jan 16 (6 days ago)

Components: Test>Telemetry

Comment 16 by benhenry@google.com, Jan 16 (6 days ago)

Components: -Tests>Telemetry

Sign in to add a comment