New issue
Advanced search Search tips

Issue 723709 link

Starred by 1 user
Status: WontFix
Owner:
xixuan@chromium.org
Closed: Mar 2018
Cc:
akes...@chromium.org
glevin@chromium.org
steve...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

peach_pit-chrome-pfq failed HWTest [sanity]

Project Member Reported by afakhry@chromium.org, May 17 2017 
It is likely an infra issue: https://uberchromegw.corp.google.com/i/chromeos/builders/peach_pit-chrome-pfq/builds/3516


Triggered task: peach_pit-chrome-pfq/R60-9559.0.0-rc4-sanity
chromeos-server22-157: 362edaeb31a02110 3
  Autotest instance: cautotest
  Bug filing disabled due to missing imports.
  Can't file pool: bvt, board: peach_pit in critical state
  TestLabException: Not enough DUTs for board: peach_pit, pool: bvt; required: 1, found: 0, suite: sanity, build: peach_pit-chrome-pfq/R60-9559.0.0-rc4
  Traceback (most recent call last):
    File "/usr/local/autotest/site_utils/run_suite.py", line 1805, in main
      code, output_dict = main_without_exception_handling(options)
    File "/usr/local/autotest/site_utils/run_suite.py", line 1623, in main_without_exception_handling
      raise e
  NotEnoughDutsError: Not enough DUTs for board: peach_pit, pool: bvt; required: 1, found: 0, suite: sanity, build: peach_pit-chrome-pfq/R60-9559.0.0-rc4
  Will return from run_suite with status: INFRA_FAILURE

Is that just a flake and cycle green the next time the PFQ is run, or is it an issue that requires intervention?

Comment 1 by afakhry@chromium.org, May 17 2017

Cc: steve...@chromium.org
peach_pit-chrome-pfq failed again, but this time HWTest [bvt-inline] https://uberchromegw.corp.google.com/i/chromeos/builders/peach_pit-chrome-pfq/builds/3517

I see the following from the logs: 

15:37:34: WARNING: (stderr):
Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No current process: you must name one.
The program is not being run.

15:38:04: WARNING: Killing 21866 (sig=15 SIGTERM)
15:38:09: INFO: Refreshing due to a 401 (attempt 1/2)
15:38:09: INFO: Refreshing access_token
15:37:34: ERROR: pre-kill notification (SIGXCPU); traceback:
....

Any idea what's going on?

Comment 2 by steve...@chromium.org, May 17 2017 

These appear to be two different failures:

#0 - "Not enough DUTs for board: peach_pit, pool: bvt; required: 1, found: 0" means that there were no DUTs available to run the tests.

#1 - STEP_LINK appears to have failed but I have no clue why it failed or what it was attempting to do.

Comment 3 by chingcodes@chromium.org, May 24 2017

Owner: xixuan@chromium.org
There where some low pool counts, not sure if peach was one that got rebalanced

Comment 4 by xixuan@chromium.org, Mar 19 2018

Status: WontFix (was: Assigned)
►

Sign in to add a comment