New issue
Advanced search Search tips

Issue 839510 link

Starred by 2 users
Status: Duplicate
Merged: issue 847558
Owner:
loyso@chromium.org
Closed: Dec 17
Cc:
philipchen@chromium.org
apronin@chromium.org
dgarr...@chromium.org
adurbin@chromium.org
emaxx@chromium.org
louiscollard@chromium.org
henryhsu@chromium.org
coconutruben@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Flaky cryptohome unit tests on VM images

Project Member Reported by norvez@chromium.org, May 3 2018 

See for example https://luci-milo.appspot.com/buildbot/chromeos/betty-release/1205

The UnitTest is orange because cryptohome's tests fail the first time. I've seen the same thing on novato, not sure about other devices.

Note that the VMTests stage is failing for a different reason, it's a regression caused by b/72749926

Assigning to the sheriffs for triage.

Comment 1 by dgarr...@chromium.org, May 3 2018 

Process is to find an owner for the bug, and disable the test if necessary.

Comment 2 by agicsaki@chromium.org, May 7 2018

Cc: philipchen@chromium.org
Owner: adurbin@chromium.org

Comment 3 by zalcorn@chromium.org, Sep 28 

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

Comment 4 by weifangsun@chromium.org, Nov 8 

<UI triage> Bug owners, please add the appropriate component to your bug. Thanks!

Comment 5 by ovanieva@chromium.org, Dec 14 

adurbin@chromium.org
 what is the right component for this?

Comment 6 by adurbin@chromium.org, Dec 14

Cc: apronin@chromium.org
I'm not sure to be honest. Andrey, do you have a suggestion?

Comment 7 by apronin@chromium.org, Dec 14

Cc: adurbin@chromium.org louiscollard@chromium.org emaxx@chromium.org
Components: OS>Systems OS>Systems>Security
Owner: loyso@chromium.org
For cryptohome unit tests, file under OS>Systems>Security. We'll triage and change the component if necessary.

In this case it was ServiceTestNotInitialized.CheckAutoCleanupCallback that failed:

cryptohome-0.0.1-r2527: [ RUN      ] ServiceTestNotInitialized.CheckAutoCleanupCallback
cryptohome-0.0.1-r2527: [0503/140204:WARNING:service_monolithic.cc(80)] Attestation-based enterprise enrollment will not be available.
cryptohome-0.0.1-r2527: [0503/140204:WARNING:service.cc(761)] TPM is not enabled. Disabling TPM alert metrics
cryptohome-0.0.1-r2527: [0503/140204:INFO:service.cc(235)] Stopping cryptohome task processing.
cryptohome-0.0.1-r2527: ../../../../../../../tmp/portage/chromeos-base/cryptohome-0.0.1-r2527/work/cryptohome-0.0.1/platform2/cryptohome/service_unittest.cc:338: Failure
cryptohome-0.0.1-r2527: Actual function call count doesn't match EXPECT_CALL(homedirs_, FreeDiskSpace())...
cryptohome-0.0.1-r2527:          Expected: to be called at least 48 times
cryptohome-0.0.1-r2527:            Actual: called 47 times - unsatisfied and active

Tentatively assigning to loyso@ for checking (+emaxx, in case he can take a look) who authored https://crrev.com/c/1078030, also in May 2018.
Is this a dup of  issue 847558  and fixed by the same CL?

Comment 8 by loyso@chromium.org, Dec 17

Mergedinto: 847558
Status: Duplicate (was: Unconfirmed)
This is the dupe. The line
EXPECT_CALL(homedirs_, FreeDiskSpace()).Times(AtLeast(48));
was deleted in my CL back on 2 June 2018.
►

Sign in to add a comment