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

Issue 912775 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Render tests have slight differences on local device.

Project Member Reported by dewittj@chromium.org, Dec 7

Issue description

I'm adding a new render test, and have a N5 with the correct API level locally, and it produces png files that don't match what the tryjobs have. I'd love to be able to iterate locally without waiting for the bots.  Here is a sample:

https://00e9e64bac81b0fc36e0f97e8b86d47d9c36d205319d51f3ec-apidata.googleusercontent.com/download/storage/v1/b/chromium-result-details/o/html%2Fchrome_public_test_apk_android-kitkat-arm-rel_142050_2018_12_06_T23_39_47-UTC?qk=AD5uMEvyAnrxH43TRLp6B5BAxjWDhl819yvb2c_kg0GfDQlLBA0o_q-DoGwk-cZyr9BLL9mhg6IIAiKGVPI116-AqMmwU06GG1P1ma8powAstiZaUeE6DUIaH3eIyqD436aVTBIq319B-ewl6TXWLZL-ZQlpDs_7JS0gByqxPg9pJm_hNSBDpQwV_TLOF-vV_o_pVUaQ6CGPpV2GAxS30zpOmOF2XkClevf6KGmGcNi9dC1ps6aRWlqIgWnNcqxl7GgjXxcBEdN5w12XctVl7whsfYlBURaaIs1QMq-yUl5XObnOoONxgMi5O6QHzkTSZVwVcXHjt-7kQtJYEVOAGG2-Ugo1WvNef-laOuFdGXn0hn1Mal_V_dkJ6KnQmD4loI4O81fLE3SN9vOarzWqe_ttvWJM4lsKaurt1YhM2YWWaleUUHfWgqc4NW1kgmC6y1gQTovTji5Ea17eEz1NTLDcW8Fh_dZRJF56wn99EXksWXjnzGXFCX6TJO9PDqdBsL5_KOsjn50-SimUASY0QKhvvucrNEtrScFiALO4fDJUsBsnueeHqvKL-v9oTyNV2lxMGf-mOD6lzGCqJlKHWz-ECeymbSAXYoCd-6gn-ALRrZ6zukl0yD-Zl6PFRaZaq545hS9y_I_6MfaDyN-M9hB17mswTOwyJJ_rZfRuuDYInj1VlGrdJdClnbRoPzlqL3Au3Hk2F21tOOybK_4Ztp8kCzOyPiYBOkihckFd29brqE8wY1JZXct5sHHqmq_NLkipj5QGz1oZaV-PGZlK9S9WzE9354Gza8wMMirDYXPH83dzatdCXWkMh3RLX2Gb8CBEn0YSGRMUJZpunHydigEKurmeEO-pMOwqxKmwocWkmsXYQRcLYDY

There seems to be a 1-pixel difference in some of the text rendering.

How can we standardize device setup? Or is there an emulator that could give me pixel perfect results?
 
I can't access the link you provided (I'm getting a "Locked Domain Expired" "Not valid after 2018-12-07T00:22:38.583Z" message).

I think John (on cc) would probably be the best to answer questions about standardised device setup. I would have assumed that a freshly imaged device would give the correct results.
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment