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

Issue 894981 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

SkylabHWTest [bvt-arc] cheets_GTS.6.0_r1.GtsPermissionTestCases and cheets_NotificationTest failing of reef-chrome-pfq, grunt-chrome-pfq, kevin-arcnext-chrome-pfq, veyron_minnie-chrome-pfq

Project Member Reported by newcomer@chromium.org, Oct 12

Issue description

ucifer: 2018/10/12 12:49:28 Error recording host status in BigQuery: googleapi: Error 404: Not found: Project chromeos-skylab, notFound
lucifer: 2018/10/12 12:49:28 Running Autotest command /usr/local/autotest/server/autoserv [-s --control-name cheets_GTS.6.0_r1.GtsPermissionTestCases --host-info-subdir host_info_store -m chromeos6-row4-rack9-host12 --lab True --local-only-host-info True -n --require-ssp -r /usr/local/autotest/results/swarming-4082938e3d16a611/autoserv_test --verify_job_repo_url -p]
DEBUG:root:Getting control file list for suite: 
lucifer: 2018/10/12 12:49:30 OpenCensus Stackdriver exporter: failed to upload 1 spans: rpc error: code = NotFound desc = Requested entity was not found.
INFO:root:Parsed 3495 child test control files.
autoserv: Could not determine control file path, assuming we need SSP: Failed to find any control files with NAME cheets_GTS.6.0_r1.GtsPermissionTestCases
lucifer: 2018/10/12 13:02:56 Sending event test_passed with message autoserv

Looks test passed but fail to record due to infra issue?
for cheets_GTS.6.0_r1.GtsPermissionTestCases	

reef and other failing boards look to have started failing w/ R71-11150.0.0

https://stainless.corp.google.com/search?view=matrix&row=test&col=build&first_date=2018-09-29&last_date=2018-10-12&test=cheets_GTS.6.0_r1.GtsPermissionTestCases&board=reef&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false


errors,

10/12 11:06:38.152 ERROR|             utils:0287| [stderr] SELinux: Loaded file_contexts contexts from /file_contexts.bin.
10/12 11:08:00.374 ERROR|    tradefed_utils:0164| Failed (but not waived) tests:
com.google.android.permission.gts.DefaultPermissionGrantPolicyTest#testDefaultGrantsWithRemoteExceptions
10/12 11:08:41.980 ERROR|             utils:0287| [stderr] SELinux: Loaded file_contexts contexts from /file_contexts.bin.
10/12 11:09:40.348 ERROR|    tradefed_utils:0164| Failed (but not waived) tests:
com.google.android.permission.gts.DefaultPermissionGrantPolicyTest#testDefaultGrantsWithRemoteExceptions
10/12 11:10:20.457 ERROR|             utils:0287| [stderr] SELinux: Loaded file_contexts contexts from /file_contexts.bin.
10/12 11:11:19.829 ERROR|    tradefed_utils:0164| Failed (but not waived) tests:
com.google.android.permission.gts.DefaultPermissionGrantPolicyTest#testDefaultGrantsWithRemoteExceptions
10/12 11:11:35.332 ERROR|             utils:0287| [stderr] cat: /tmp/sysinfo/autoserv-IwFJ0j/.checksum: No such file or directory
Summary: SkylabHWTest [bvt-arc] cheets_GTS.6.0_r1.GtsPermissionTestCases and cheets_NotificationTest failing of reef-chrome-pfq, grunt-chrome-pfq, kevin-arcnext-chrome-pfq, veyron_minnie-chrome-pfq (was: SkylabHWTest [bvt-arc] cheets_GTS.6.0_r1.GtsPermissionTestCases and cheets_NotificationTest failing of reef-chrome-pfq)
Adding new boards that failed on the newest run.

veyron_minnie-chrome-pfq had other (probably) related failures too.
#2 is definitely an Arc issue. file https://b.corp.google.com/issues/117677270


Owner: ihf@chromium.org
Status: Started (was: Untriaged)
To unblock cq/pfq I will swap the test for GtsMemoryHostTestCases.

(The tests are just integration tests, i.e. test the ability to run Gts, not the correctness of Gts. We should not have external dependencies in the CQ. I was not aware of this issue.)
Project Member

Comment 7 by bugdroid1@chromium.org, Oct 13

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/16735515cacc8132885e60d64fc40627505c3db5

commit 16735515cacc8132885e60d64fc40627505c3db5
Author: Ilja H. Friedel <ihf@chromium.org>
Date: Sat Oct 13 00:39:12 2018

Status: Fixed (was: Started)
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-71; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-71 label, otherwise remove Merge-TBD label. Thanks.
Project Member

Comment 10 by bugdroid1@chromium.org, Oct 13

Labels: merge-merged-release-R71-11151.B
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/f3f9368d2237e57b381bf8e971352b74a1133095

commit f3f9368d2237e57b381bf8e971352b74a1133095
Author: Ilja H. Friedel <ihf@chromium.org>
Date: Sat Oct 13 00:40:45 2018

Project Member

Comment 11 by bugdroid1@chromium.org, Oct 13

Labels: merge-merged-release-R70-11021.B
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/1f345b1de27b0da70312963d8227ca857077e53e

commit 1f345b1de27b0da70312963d8227ca857077e53e
Author: Ilja H. Friedel <ihf@chromium.org>
Date: Sat Oct 13 00:41:10 2018

Project Member

Comment 12 by sheriffbot@chromium.org, Nov 26

Labels: -Merge-TBD

Sign in to add a comment