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

Issue 767610 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 775219
Owner: ----
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

gpu_perftest failing on a1 perf bot

Project Member Reported by rnep...@chromium.org, Sep 21 2017

Issue description

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20One%20Perf/builds/534

mkdir failed for /storage/sdcard0/chromium_tests_root/, Read-only file system
 
I forgot to assign the bug number in the bisect, but its running here:
https://chromeperf.appspot.com/buildbucket_job_status/8967807403166187808
Cc: simonhatch@chromium.org reve...@chromium.org
Perfbot sheriff checking in: +simonhatch, can you tell if the bisect found a culprit?

CC-ing test owner reveman: Should we disable gpu_perftest on Android One until this is resolved?
re: #c2

Nope, no culprit, both revisions had return code of 1.
"mkdir failed for /storage/sdcard0/chromium_tests_root/, Read-only file system" seems like a failure on the device and not something that a chrome change is causing
Cc: vhang@chromium.org
It seems possible that the device does not have an sdcard in it? Has any a1 devices been replaced recently? Who should we add to the bug to find that out? I'm going to add Vince in the hopes he will know.
Cc: bpastene@chromium.org
Oh. The BattOr swap out. Did we in-place replace the phones? Or did we swap out with new ones? If we swapped out with new ones did we replace the sdcards if they had them?

I know the old provision devices script had a hack to make a1 devices work. I wrote it. I dont know if that made it to the new docker/swarming world though. Adding bpastene@ for that. 
The phones were indeed replaced during the battor swaps. (I know this because we were getting missing device alerts for the old ones.)

Swarming's provisioning doesn't have any special A1 logic, but we could add it if necessary. I'm not sure it's needed though since the other A1s seem fine, right?

Also, I noticed that the bot the test is failing on has a different os version than perf's other A1s:
https://chromium-swarm.appspot.com/botlist?c=id&c=os&c=task&c=status&c=device_os&f=pool%3AChrome-perf&f=device_type%3AAndroid%20One%20(sprout)&l=100&q=device_os&s=device_os%3Aasc

Is that intended? If not, it may have something to do with it.
Cc: pschmidt@chromium.org
Yeah, I think checking the old phones for SDCards that didn't get moved over is the correct next move.

As for the OS, my guess is that is by mistake. 

Comment 9 by vhang@chromium.org, Sep 27 2017

In crbug.com/729751, it was never mentioned that the SD card need to be moved over.  Do you have a list of phones that needs an SD card?  I can try to track down the old phones and pull the SD card from them.
Unfortunately I dont think anyone on that bug would have known about the SDCards that are required for the a1 devices to work in the labs.

I would assume all the new a1 devices would need them.
Issue 771637 has been merged into this issue.
Mergedinto: 775219
Status: Duplicate (was: Untriaged)

Sign in to add a comment