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

Issue metadata

Status: Verified
Closed: Feb 2018
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Sign in to add a comment

Issue 814514: veyron_rialto-release: No module named telemetry.core

Reported by, Feb 21 2018 Project Member

Issue description

Failing for ~5days

First failure:

[Test-Logs]: graphics_Idle: ERROR: Unhandled ImportError: No module named telemetry.core
[Test-Logs]: login_Cryptohome: ERROR: Unhandled ImportError: No module named telemetry.core
[Test-Logs]: login_CryptohomeIncognito: retry_count: 1, ERROR: Unhandled ImportError: No module named telemetry.core
[Test-Logs]: login_LoginSuccess: ERROR: Unhandled ImportError: No module named telemetry.core
[Test-Logs]: login_LogoutProcessCleanup: retry_count: 1, ERROR: Unhandled ImportError: No module named telemetry.core
[Test-Logs]: security_NetworkListeners: retry_count: 1, ERROR: Unhandled ImportError: No module named telemetry.core
[Test-Logs]: security_ProfilePermissions.guest: retry_count: 1, ERROR: Unhandled ImportError: No module named telemetry.core
[Test-Logs]: security_ProfilePermissions.login: retry_count: 1, ERROR: Unhandled ImportError: No module named telemetry.core
[Test-Logs]: security_SandboxStatus: retry_count: 1, ERROR: Unhandled ImportError: No module named telemetry.core

I wonder if it's related to which had similar issues. Timing does not exactly fit, but several canary builds before #1947 failed because of infra issues, so it's still possible that the CL broke veyron_rialto but the build only started failing because of it 1-2 days later.

Comment 1 by, Feb 21 2018

+achuith, telemetry expert

Comment 2 by, Feb 22 2018

probably caused by this:

The cryptohome tests package now includes tests that rely on telemetry to emulate Chrome logins. should it belong to a different package?

Comment 3 by, Feb 22 2018

Maybe login_Cryptohome and login_CryptohomeIncognito should move to autotest-tests-cryptohome instead of autotest-chrome, but that won't change the other tests that are failing (e.g. security_*), right?

My impression is that overrides (or maybe rather is executed after?) a similar method in autotest-chrome:

Comment 4 by, Feb 22 2018

I added both that custom src_prepare() and DEPEND on autotest-chrome in a single update. Maybe just DEPEND was enough. W/o those it was (understandably) failing - see all those errors for patchset 3 in CL:857208. After that it passed Pre-CQ and CQ.
But that means that for the majority of the boards it works fine  even when both autotest-chrome and autotest-tests-cryptohome do this installation of telemetry into a tempdir. 

Likely, the issue is a little different: for veyron_rialto we only had autotest-tests-chryptohome. We didn't have autotest-chrome (or a test that needs telemetry in autotest-tests-chryptohome). It now stumbles on autotest-chrome, but would stumble on the updated autotest-tests-chryptohome if it was coming first in the dependencies tree. 

I guess, the telemetry package is built differently for veyron_rialto? And it simply doesn't install telemetry.core?
And if we need to support telemetry-less boards like this, I need to move platform_InitLoginPerf out of autotest-tests-chryptohome to some other package, and revert all changes to autotest-tests-chryptohome ebuild. The question is what should that other package that is only included for boards with Chrome be?

Comment 5 by, Feb 22 2018

platform_InitLoginPerf may need to go to autotest-chrome.

Looks like we did exactly that for tests_platform_Pkcs11InitOnLogin, which is included in autotest-chrome ebuild for similar reasons? 

So, reverting CL:875208 and adding platform_InitLoginPerf to autotest-chrome sounds like the right approach. Not sure who owns autotest-chrome to confirm. +cywang for opinion.

Comment 6 by, Feb 22 2018

Yes, I believe we put the autotests import telemetry to test chrome in autotest-chrome.

Comment 7 by, Feb 22 2018

Status: Assigned (was: Unconfirmed)

Comment 8 by, Feb 22 2018

Status: Started (was: Assigned)
Note: I couldn't reproduce the issue on the local veyron_rialto build. Though I noticed that it built Chrome from scratch to complete build_packages. Are those failing builders incremental - that could affect it.

Still, it apparently adds chrome to the set of built packages when dependencies are resolved correctly. So, moving platform_InitLoginPerf to autotest-chrome (which is not included in case of USE=chromeless_tests, as on veyron_rialto) is the right move.

Submitted for review.

Comment 9 by, Feb 23 2018

Project Member
The following revision refers to this bug:

commit 0ddaa4bcccd08cfb9f751b57ddc4f811dab65543
Author: Andrey Pronin <>
Date: Fri Feb 23 22:16:02 2018

Move platform_InitLoginPerf to autotest-chrome

autotest-tests-cryptohome can be used on a headless target like
veyron_rialto and shouldn't utilize telemetry.

Move platform_InitLoginPerf to autotest-chrome and remove all
dependencies on telemetry from autotest-tests-cryptohome.

BUG= chromium:814514 
TEST=build_packages --board=veyron_rialto
     emerge-eve autotest-chrome autotest-tests-cryptohome

Change-Id: I2b09e111678d804e9cd8b126ef26db326cf5c0c3
Commit-Ready: Andrey Pronin <>
Tested-by: Andrey Pronin <>
Reviewed-by: Achuith Bhandarkar <>
Reviewed-by: Chung-yih Wang <>


Comment 10 by, Feb 25 2018

Status: Verified (was: Started)
The 5 last builds have been green

Sign in to add a comment