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

Issue 632247 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
█ dshi@chromium.org
dgarr...@chromium.org
█ jrbarnette@chromium.org
█ kirtika@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

tests marked as ABORT but passed

Project Member Reported by kevcheng@chromium.org, Jul 28 2016 
https://uberchromegw.corp.google.com/i/chromeos/builders/wolf-paladin/builds/11734/steps/HWTest%20%5Bbvt-inline%5D/logs/stdio

The following test is marked as PASSED but then a test with the same name but has "_SERVER_JOB" appended to it is marked as abort.  They share the same job id.  What's going on?

login_OwnershipNotRetaken_SERVER_JOB    http://cautotest/tko/retrieve_logs.cgi?job=/results/71120953-chromeos-test/
  login_OwnershipNotRetaken               http://cautotest/tko/retrieve_logs.cgi?job=/results/71120953-chromeos-test/

login_OwnershipNotRetaken_SERVER_JOB    [ FAILED ]
login_OwnershipNotRetaken_SERVER_JOB      ABORT: 
login_OwnershipNotRetaken               [ PASSED ]

Comment 1 by kevcheng@chromium.org, Jul 28 2016 

Maybe it hit a timeout? Based on the time the suite started and the testing ended (93 mins).  Usually these bvt-inline on wolf takes 10 mins (testing-wise) so this definitely took a long time compared to a passing run.  

Failed Suite timings:
  Downloads started at 2016-07-27 20:05:18
  Payload downloads ended at 2016-07-27 20:05:27
  Suite started at 2016-07-27 20:05:38
  Artifact downloads ended (at latest) at 2016-07-27 20:05:40
  Testing started at 2016-07-27 20:13:30
  Testing ended at 2016-07-27 21:38:49

Passing Suite timings (from wolf-paladin #11732):
  Downloads started at 2016-07-27 16:10:33
  Payload downloads ended at 2016-07-27 16:10:41
  Suite started at 2016-07-27 16:11:04
  Artifact downloads ended (at latest) at 2016-07-27 16:11:07
  Testing started at 2016-07-27 16:20:20
  Testing ended at 2016-07-27 16:30:40

Comment 2 by kevcheng@chromium.org, Jul 28 2016 

A peach-pit-paladin failed but ran within a reasonable amount of time so maybe it's not a timeout problem?

https://uberchromegw.corp.google.com/i/chromeos/builders/peach_pit-paladin/builds/13128/steps/HWTest%20%5Bbvt-cq%5D/logs/stdio

Suite timings:
  Downloads started at 2016-07-27 07:07:12
  Payload downloads ended at 2016-07-27 07:07:19
  Suite started at 2016-07-27 07:08:28
  Artifact downloads ended (at latest) at 2016-07-27 07:08:31
  Testing started at 2016-07-27 07:08:34
  Testing ended at 2016-07-27 07:43:37
  

 logging_UserCrash_SERVER_JOB              [ FAILED ]
 logging_UserCrash_SERVER_JOB                ABORT: 
 logging_UserCrash                         [ PASSED ]

logging_UserCrash_SERVER_JOB              http://cautotest/tko/retrieve_logs.cgi?job=/results/71083366-chromeos-test/
logging_UserCrash                         http://cautotest/tko/retrieve_logs.cgi?job=/results/71083366-chromeos-test/

Comment 3 by davidri...@chromium.org, Aug 13 2016 

Another occurrence:
https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_speedy-paladin/builds/2836

  Suite timings:
  Downloads started at 2016-08-12 17:32:13
  Payload downloads ended at 2016-08-12 17:32:21
  Suite started at 2016-08-12 17:32:39
  Artifact downloads ended (at latest) at 2016-08-12 17:32:41
  Testing started at 2016-08-12 17:32:45
  Testing ended at 2016-08-12 18:09:42

Comment 4 by dshi@chromium.org, Aug 13 2016 

Re #3
From the status log:
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/73067308-chromeos-test/chromeos4-row4-rack11-host21/
INFO	----	----	Job aborted by autotest_system on 2016-08-12 18:09:40

The suite job was timed out.

Comment 6 by jrbarnette@chromium.org, Oct 24 2016

Labels: -Pri-3 OS-Chrome Pri-2
Owner: ----
Status: Available (was: Untriaged)
Possibly the same as  bug 658469 .

Comment 7 by dshi@chromium.org, Oct 25 2016

Status: WontFix (was: Available)
The timeout in #4 is due to devserver timeout
08/12 17:48:12.974 INFO |    connectionpool:0188| Starting new HTTP connection (1): 172.17.40.17
08/12 18:09:50.832 INFO |          autoserv:0694| Results placed in /usr/local/autotest/results/73067308-chromeos-test/chromeos4-row4-rack11-host21

172.17.40.17 is an old crash server that got overloaded. We have changed the crash server so dump symbolication is much faster now.
►

Sign in to add a comment