Fix bisect-builds.py to work for the ChromeOS Files App |
|||||||
Issue descriptionbisect-builds.py (as described here - https://www.chromium.org/developers/bisect-builds-py) currently has a chromeos binary target, which can check out bisected versions of chromeos. However, launching the downloaded binary results in a version of chrome without a login screen and without a working files app. If we could get this to work, it would make bisecting builds much easier, testing features on certain versions easier, and help the testing team access different versions of ChromeOS as well. For this bug, investigate why the files app doesn't launch with fetched ChromeOS binaries from bisect-builds.py (which might simply be a case of passing the right flags), and see if the testing team can use this to bisect bugs as well.
,
Mar 28 2018
,
Mar 28 2018
+james, maybe you have advice? Backstory: issue 825695 , a regression affecting web and CrOS. No test squeaked, and a bisect-builds.py for CrOS failed us, so we filed this big. We resolved issue 825695 using 'git bisect' instead.
,
Mar 28 2018
There's a long history of bisect-builds.py not-really-working on chromeos: https://bugs.chromium.org/p/chromium/issues/list?can=2&q=bisect-builds+OS%3DChrome+&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids I suspect that's because the binaries on the build server are not actually what we ship on device (nor should they be). Showing the login screen might be as simple as adding --login-manager to the args. Dunno if signing in as a real user would give you a working file manager. It's also possible files needed by the File Manager are missing from the build archive. This is probably an issue to escalate with infra and/or chromeos-ui. It likely hasn't been addressed because it sits in the middle of those two orgs.
,
Mar 28 2018
Moved under ChromeOS infra
,
Mar 28 2018
#4 thanks, did try various args like --login-manager etc, no joy. Reading related bugs entered into issue 663450, seems "It's also possible files needed by the File Manager are missing from the build archive" is the likely cause.
,
Apr 4 2018
Aside: stumbled upon a new (to me) CrOS-specific command % cros bisect ... |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by noel@chromium.org
, Mar 27 2018