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

Issue 765364 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

VMTest failures on chrome-pfq tot informational builders

Project Member Reported by osh...@chromium.org, Sep 14 2017

Issue description

Comment 1 by osh...@chromium.org, Sep 14 2017

actually several tests are failing. It's timing out because test are failing due to timeout, which may be related to 764787.

01:19:42 INFO | autoserv| AUTOTEST_STATUS::  Found Minidump: False
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  Stack Trace:
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  ********************************************************************************
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  	Cannot get stack trace on CrOS
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  ********************************************************************************
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  Standard output:
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  ********************************************************************************
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  	Cannot get standard output on CrOS
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  ********************************************************************************
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  System log:
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  (Not implemented)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  Traceback (most recent call last):
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/autotest/common_lib/test.py", line 806, in _call_test_function
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      return func(*args, **dargs)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/autotest/common_lib/test.py", line 470, in execute
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      dargs)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/autotest/common_lib/test.py", line 347, in _call_run_once_with_retry
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      postprocess_profiled_run, args, dargs)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/autotest/common_lib/test.py", line 380, in _call_run_once
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      self.run_once(*args, **dargs)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/autotest/tests/login_LoginSuccess/login_LoginSuccess.py", line 48, in run_once
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      with chrome.Chrome(arc_mode=arc_mode):
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/autotest/common_lib/cros/chrome.py", line 167, in __init__
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      self._browser = browser_to_create.Create(finder_options)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_finder.py", line 48, in Create
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      browser_backend, self._platform_backend, self._credentials_path)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_with_oobe.py", line 14, in __init__
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      backend, platform_backend, credentials_path)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py", line 59, in __init__
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      self._browser_backend.Start()
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/telemetry/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      return func(*args, **kwargs)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_backend.py", line 171, in Start
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      self._WaitForBrowserToComeUp()
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/telemetry/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      return func(*args, **kwargs)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::    File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/chrome_browser_backend.py", line 192, in _WaitForBrowserToComeUp
01:19:42 INFO | autoserv| AUTOTEST_STATUS::      raise exceptions.BrowserGoneException(self.browser, e)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  BrowserGoneException: Timed out while waiting 240s for HasBrowserFinishedLaunching.
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  Found Minidump: False
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  Stack Trace:
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  ********************************************************************************
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  	Cannot get stack trace on CrOS
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  ********************************************************************************
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  Standard output:
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  ********************************************************************************
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  	Cannot get standard output on CrOS
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  ********************************************************************************
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  System log:
01:19:42 INFO | autoserv| AUTOTEST_STATUS::  (Not implemented)
01:19:42 INFO | autoserv| AUTOTEST_STATUS::	END FAIL	login_LoginSuccess	login_LoginSuccess	timestamp=1505369981	localtime=Sep 13 23:19:41

Comment 2 by osh...@chromium.org, Sep 14 2017

Owner: gurcheta...@chromium.org
Status: Assigned (was: Untriaged)
turns out gpu process is failing to start.


Cc: ihf@chromium.org
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 14 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/1229a4f63026fbac918b3514d6d0c8354ec8ad6a

commit 1229a4f63026fbac918b3514d6d0c8354ec8ad6a
Author: Gurchetan Singh <gurchetansingh@chromium.org>
Date: Thu Sep 14 23:15:41 2017

media-libs/mesa: temporarily re-enable swrast on all boards

We still have some non-Betty Chrome PFQ informational builders that run
VMTests. Let's unconditionally re-enable swrast drivers until we can
remove these.

BUG= chromium:765364 
TEST=Informational bots green again

Change-Id: Id9426cc1f367606aac3d52a99b221b15086f0cc5
Reviewed-on: https://chromium-review.googlesource.com/668023
Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org>
Tested-by: Gurchetan Singh <gurchetansingh@chromium.org>

[rename] https://crrev.com/1229a4f63026fbac918b3514d6d0c8354ec8ad6a/media-libs/mesa/mesa-17.1.1-r8.ebuild
[modify] https://crrev.com/1229a4f63026fbac918b3514d6d0c8354ec8ad6a/media-libs/mesa/mesa-17.1.1.ebuild

Comment 5 by ihf@chromium.org, Sep 14 2017

Cc: gurcheta...@chromium.org
Owner: ihf@chromium.org
Thanks for reverting. I will try to find all values that enable vm_tests for non-betty class boards.

Comment 6 by ihf@chromium.org, Sep 15 2017

Labels: -Pri-1 Pri-2
Lumpy and Tricky are fine again.

Betty failure was indeed unrelated.

I still need to figure out how to kill VMTest on informational builders for sure.
Cc: -seobrien@chromium.org
Project Member

Comment 9 by bugdroid1@chromium.org, Sep 28 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/1a8eecd7a057aadc8cfe558ef093032315276ca9

commit 1a8eecd7a057aadc8cfe558ef093032315276ca9
Author: Bernie Thompson <bhthompson@google.com>
Date: Thu Sep 28 18:18:53 2017

Add betty-incremental builder

Complete with VM tests.

BUG= chromium:765364 
TEST=None

Change-Id: If4bebaa1efcd85b38fcb618f0f8682bc39d1e37a
Reviewed-on: https://chromium-review.googlesource.com/674028
Commit-Ready: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>

[modify] https://crrev.com/1a8eecd7a057aadc8cfe558ef093032315276ca9/cbuildbot/config_dump.json
[modify] https://crrev.com/1a8eecd7a057aadc8cfe558ef093032315276ca9/cbuildbot/waterfall_layout_dump.txt
[modify] https://crrev.com/1a8eecd7a057aadc8cfe558ef093032315276ca9/cbuildbot/chromeos_config.py

Project Member

Comment 10 by bugdroid1@chromium.org, Oct 12 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/9af4a9a23a7589ce4dec411604695c4572c75190

commit 9af4a9a23a7589ce4dec411604695c4572c75190
Author: Ilja H. Friedel <ihf@chromium.org>
Date: Thu Oct 12 17:42:35 2017

cbuildbot: clean up betty vmtest.

1) Explicitly define a list of VM capable boards:
   amd64-generic, betty, newbie, novato and all of lakitu.
2) Switch ASAN build from amd64-generic to betty so it will support
   vm_tests.
3) Clean up minor defines.
4) Override all boards which are not supported to *not* run VM tests.

BUG= chromium:765364 , chromium:772568
TEST=unittest

Change-Id: I51abc7894d3d857b03bd4d6c32bec7493ce55335
Reviewed-on: https://chromium-review.googlesource.com/704594
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Tested-by: Ilja H. Friedel <ihf@chromium.org>
Commit-Queue: Ilja H. Friedel <ihf@chromium.org>

[modify] https://crrev.com/9af4a9a23a7589ce4dec411604695c4572c75190/cbuildbot/config_dump.json
[modify] https://crrev.com/9af4a9a23a7589ce4dec411604695c4572c75190/cbuildbot/waterfall_layout_dump.txt
[modify] https://crrev.com/9af4a9a23a7589ce4dec411604695c4572c75190/cbuildbot/stages/vm_test_stages_unittest.py
[modify] https://crrev.com/9af4a9a23a7589ce4dec411604695c4572c75190/cbuildbot/chromeos_config_unittest.py
[modify] https://crrev.com/9af4a9a23a7589ce4dec411604695c4572c75190/cbuildbot/chromeos_config.py

Project Member

Comment 11 by bugdroid1@chromium.org, Oct 15 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/a4c7e3d5918d9e8ab694cb0742867a04250d52c8

commit a4c7e3d5918d9e8ab694cb0742867a04250d52c8
Author: Gurchetan Singh <gurchetansingh@chromium.org>
Date: Sat Oct 14 02:42:59 2017

media-libs/mesa: enable swrast drivers when USE flag is set (reland)

With CL:704594 landed, we can stop building unnecessary drivers for
every board. Note the 9999 ebuild already has this change.

BUG= chromium:765364 
TEST=emerge-cave doesn't build swrast_dri.so or kms_swrast_dri.so
     emerge-betty doesn't build i965.so

Change-Id: Ia4cb6318185036f5057334925a52a37c5e03cc9d
Reviewed-on: https://chromium-review.googlesource.com/716867
Commit-Ready: Gurchetan Singh <gurchetansingh@chromium.org>
Tested-by: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[rename] https://crrev.com/a4c7e3d5918d9e8ab694cb0742867a04250d52c8/media-libs/mesa/mesa-17.1.1-r11.ebuild
[modify] https://crrev.com/a4c7e3d5918d9e8ab694cb0742867a04250d52c8/media-libs/mesa/mesa-17.1.1.ebuild

Project Member

Comment 12 by bugdroid1@chromium.org, Oct 16 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/3e65096ed31bc0ad76d5b393da072b2d86ed69fe

commit 3e65096ed31bc0ad76d5b393da072b2d86ed69fe
Author: Ilja H. Friedel <ihf@chromium.org>
Date: Mon Oct 16 07:17:48 2017

chromeos_config: apply no_vmtest template late.

Apparently pre-cq and other builders don't use CreateBoardConfigs.
Move the application of the no_vmtest_builder template to the
very end.

Also add new unit test to check that no board that isn't listed
attempts to run VM tests. Did check that it uncovered several
config before this change and not after.

BUG= chromium:765364 , chromium:772568
TEST=run_tests

Change-Id: I3139d64609a16032c95d97cf347e5ae1e698a435
Reviewed-on: https://chromium-review.googlesource.com/719771
Commit-Ready: Ilja H. Friedel <ihf@chromium.org>
Tested-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>

[modify] https://crrev.com/3e65096ed31bc0ad76d5b393da072b2d86ed69fe/cbuildbot/config_dump.json
[modify] https://crrev.com/3e65096ed31bc0ad76d5b393da072b2d86ed69fe/cbuildbot/waterfall_layout_dump.txt
[modify] https://crrev.com/3e65096ed31bc0ad76d5b393da072b2d86ed69fe/cbuildbot/chromeos_config_unittest.py
[modify] https://crrev.com/3e65096ed31bc0ad76d5b393da072b2d86ed69fe/cbuildbot/chromeos_config.py

Project Member

Comment 13 by bugdroid1@chromium.org, Oct 16 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/c51866c2ebcc62100cf3cbc3775715354595d0a2

commit c51866c2ebcc62100cf3cbc3775715354595d0a2
Author: Ilja H. Friedel <ihf@chromium.org>
Date: Mon Oct 16 07:17:48 2017

chromeos_config: re-add amd64-generic-asan.

In 9af4a9a23a7589ce4dec411604695c4572c75190 I switched all of amd64-generic-asan
to betty-asan. Now I have more information and I believe it is better if they
co-exist. (amd64-generic is fully public and VM capable, while betty has private
bits.) So this is a partial revert and re-adds amd64-generic-asan.

BUG= chromium:765364 , chromium:772568,  chromium:774251 
TEST=unittest

Change-Id: I0021db9c4d4e432b2e00f2a318e37f09c046c272
Reviewed-on: https://chromium-review.googlesource.com/720151
Commit-Ready: Ilja H. Friedel <ihf@chromium.org>
Tested-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>

[modify] https://crrev.com/c51866c2ebcc62100cf3cbc3775715354595d0a2/cbuildbot/config_dump.json
[modify] https://crrev.com/c51866c2ebcc62100cf3cbc3775715354595d0a2/cbuildbot/waterfall_layout_dump.txt
[modify] https://crrev.com/c51866c2ebcc62100cf3cbc3775715354595d0a2/cbuildbot/chromeos_config.py

Project Member

Comment 14 by bugdroid1@chromium.org, Oct 17 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/e550f58e089c1bce534e1002cc674d3ea3ed9595

commit e550f58e089c1bce534e1002cc674d3ea3ed9595
Author: Ilja H. Friedel <ihf@chromium.org>
Date: Tue Oct 17 00:47:45 2017

cbuildbot: move betty-asan to internal waterfall.

betty-asan builds from internal sources unlike amd64-generic-asan,
so it should live on the internal waterfall.

BUG= chromium:765364 , chromium:772568,  chromium:774251 
TEST=run_tests

Change-Id: I6ec03570622a5617bccf72d510388eda0eb52d87
Reviewed-on: https://chromium-review.googlesource.com/722118
Commit-Queue: Ilja H. Friedel <ihf@chromium.org>
Tested-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Trybot-Ready: Bernie Thompson <bhthompson@chromium.org>

[modify] https://crrev.com/e550f58e089c1bce534e1002cc674d3ea3ed9595/cbuildbot/config_dump.json
[modify] https://crrev.com/e550f58e089c1bce534e1002cc674d3ea3ed9595/cbuildbot/waterfall_layout_dump.txt
[modify] https://crrev.com/e550f58e089c1bce534e1002cc674d3ea3ed9595/cbuildbot/chromeos_config.py

Project Member

Comment 15 by bugdroid1@chromium.org, Oct 27 2017

Labels: merge-merged-release-R63-10032.B
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/0b859d567c5d092f0a8ff8f5561e8f2cf98b0654

commit 0b859d567c5d092f0a8ff8f5561e8f2cf98b0654
Author: Gurchetan Singh <gurchetansingh@chromium.org>
Date: Fri Oct 27 16:23:02 2017

media-libs/mesa: enable swrast drivers when USE flag is set (reland)

With CL:704594 landed, we can stop building unnecessary drivers for
every board. Note the 9999 ebuild already has this change.

BUG= chromium:765364 
BUG= chromium:777874 
TEST=emerge-cave doesn't build swrast_dri.so or kms_swrast_dri.so
     emerge-betty doesn't build i965.so

Change-Id: Ia4cb6318185036f5057334925a52a37c5e03cc9d
Reviewed-on: https://chromium-review.googlesource.com/716867
Commit-Ready: Gurchetan Singh <gurchetansingh@chromium.org>
Tested-by: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
(cherry picked from commit a4c7e3d5918d9e8ab694cb0742867a04250d52c8)
Reviewed-on: https://chromium-review.googlesource.com/741089
Commit-Queue: Nicolas Norvez <norvez@chromium.org>
Tested-by: Nicolas Norvez <norvez@chromium.org>
Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org>

[rename] https://crrev.com/0b859d567c5d092f0a8ff8f5561e8f2cf98b0654/media-libs/mesa/mesa-17.1.1-r11.ebuild
[modify] https://crrev.com/0b859d567c5d092f0a8ff8f5561e8f2cf98b0654/media-libs/mesa/mesa-17.1.1.ebuild

Project Member

Comment 16 by bugdroid1@chromium.org, Nov 11 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/885bba6d73e17bf74c81d85fe1fe5c4ebeeb2818

commit 885bba6d73e17bf74c81d85fe1fe5c4ebeeb2818
Author: Gurchetan Singh <gurchetansingh@chromium.org>
Date: Sat Nov 11 02:45:52 2017

media-libs/arc-mesa: Don't build swrast in AMD/Intel vendor images

This is the arc-mesa analogue of CL:716867. video_cards_llvmpipe is
already in profiles, so we should be good.

BUG= chromium:765364 
TEST=emerge-samus arc-mesa doesn't build kms_swrast_dri.so
     emerge-betty does

Change-Id: Ife21d206c26caed234f81ca9c3c84d35623f1781
Reviewed-on: https://chromium-review.googlesource.com/764789
Commit-Ready: Gurchetan Singh <gurchetansingh@chromium.org>
Tested-by: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/885bba6d73e17bf74c81d85fe1fe5c4ebeeb2818/media-libs/arc-mesa/arc-mesa-9999.ebuild

Comment 17 by ihf@chromium.org, Apr 12 2018

Status: Fixed (was: Assigned)

Sign in to add a comment