testForegroundTab failure on chromeos 3/1 |
||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of oshima@google.com amd64-generic-telemetry:14167 failed Builders failed on: - amd64-generic-telemetry: https://luci-milo.appspot.com/buildbot/chromiumos.chromium/amd64-generic-telemetry/14167
,
Mar 1 2018
Just found this : crbug.com/815220 bleung@, looks like this is the same issue?
,
Mar 1 2018
Really strange:
3/01 07:43:52.002 INFO |run_chromeos_tests:0052| [347/1152] telemetry.internal.browser.browser_unittest.BrowserTest.testForegroundTab failed unexpectedly 11.3489s:
03/01 07:43:52.003 INFO |run_chromeos_tests:0052| Traceback (most recent call last):
03/01 07:43:52.005 INFO |run_chromeos_tests:0052| File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/testing/browser_test_case.py", line 39, in WrappedMethod
03/01 07:43:52.007 INFO |run_chromeos_tests:0052| method(self)
03/01 07:43:52.009 INFO |run_chromeos_tests:0052| File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/browser/browser_unittest.py", line 80, in testForegroundTab
03/01 07:43:52.010 INFO |run_chromeos_tests:0052| self.assertEqual(self._browser.foreground_tab, original_tab)
03/01 07:43:52.011 INFO |run_chromeos_tests:0052| File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py", line 95, in foreground_tab
03/01 07:43:52.013 INFO |run_chromeos_tests:0052| raise exceptions.TabMissingError("No foreground tab found")
03/01 07:43:52.014 INFO |run_chromeos_tests:0052| TabMissingError: No foreground tab found
,
Mar 1 2018
Seems to be a consistent failure in testForegroundTab This is the list of catapult CLs and none of them stand out: https://chromium.googlesource.com/catapult.git/+log/b019720d08b2..279fcf542e09 This could be a change in behavior in chrome
,
Mar 1 2018
None of the rest of the chrome CLs particularly stand out either. Oshima-san, would you be possibly able to do a bisect?
,
Mar 1 2018
which log file was it?
,
Mar 1 2018
Details on how to run the test are here: https://chromium.googlesource.com/chromiumos/docs/+/master/cros_vm.md Basically enter the cros-chrome SDK: achuith@achuithz620:~/code/chrome$ cros chrome-sdk --debug --download-vm --board=amd64-generic --clear-sdk-cache Start the VM: (sdk amd64-generic R66-10436.0.0-b21303) achuith@achuithz620 ~/code/chrome $ cros_vm --start Run the test: (sdk amd64-generic R66-10448.0.0-b21345) achuith@achuithz620 ~/code/chrome $ src/third_party/catapult/telemetry/bin/run_tests --browser=cros-chrome --remote=localhost --remote-ssh-port=9222 testForegroundTab To update chrome in the VM in the doc: (sdk) .../chrome/src $ autoninja -C out_$SDK_BOARD/Release/ chrome chrome_sandbox nacl_helper (sdk) .../chrome/src $ deploy_chrome --build-dir=out_$SDK_BOARD/Release/ --to=localhost --port=9222
,
Mar 1 2018
For the log, click on telemetry_UnitTestsServer, which will take you to pantheon. Click on telemetry_UnitTests->debug->telemetry_UnitTest.DEBUG. Search for 'failed unexpectedly'
,
Mar 3 2018
It looks like Tab.Activate() isn't always finishing or we're not waiting long enough for it to finish? It is trying to locate the "foreground tab" by iterating through the tabs and checking for "!document.hidden". On failure: the original tab IS in the foreground, but "document.hidden" is true (on both tabs) so the test fails. Not sure why document.hidden would be true on the foreground tab unless maybe the test isn't waiting long enough or something? If I open the inspector and print document.hidden, it is false.
,
Mar 3 2018
,
Mar 5 2018
CL was reverted. https://chromium-review.googlesource.com/c/chromium/src/+/947802
,
Mar 5 2018
,
Mar 5 2018
Last 20 builds have been green - thank you for tracking this down, Evan and Oshima-san! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by osh...@chromium.org
, Mar 1 2018Components: Tests>Telemetry
Labels: -Pri-2 OS-Chrome Pri-1