win10 tests passing on GCE |
|||||||||||||
Issue descriptionhere is list of tests failing on the Win10 GCE bot (as of Feb 16) source - https://groups.google.com/a/google.com/forum/#!topic/chrome-windows/l-OcbHlyCLQ browser_tests https://chromium-swarm-dev.appspot.com/user/task/2cffaabb53340810 ChromeTracingDelegateBrowserTestOnStartup.StartupTracingThrottle https://chromium-swarm-dev.appspot.com/user/task/2cffaabb2196ef10 ChromeSecurityExploitBrowserTest.ChromeExtensionResources ChromeSecurityExploitBrowserTest.ChromeExtensionResources https://chromium-swarm-dev.appspot.com/user/task/2cffaab8978f5d10 TabRestoreTest.RestoreWindowAndTab https://chromium-swarm-dev.appspot.com/user/task/2cffaab5441e5810 ChromeTracingDelegateBrowserTest.BackgroundTracingThrottleTimeElapsed https://chromium-swarm-dev.appspot.com/user/task/2cffaaa9ebe05310 ChromeTracingDelegateBrowserTest.BackgroundTracingTimeThrottled https://chromium-swarm-dev.appspot.com/user/task/2cffaaa552229410 ChromeTracingDelegateBrowserTest.NewIncognitoSessionBlockingTraceFinalization ContinueWhereILeftOffTest.CookiesClearedOnExit https://chromium-swarm-dev.appspot.com/user/task/2cffaa9dcd581e10 SmartSessionRestoreTest.CorrectLoadingOrder components_unittests https://chromium-swarm-dev.appspot.com/user/task/2cffaaa9f173cf10 MetricsWebContentsObserverTest.* -> 6 tests crashed content_browsertests https://chromium-swarm-dev.appspot.com/user/task/2cffaaae96b27610 BackgroundTracingManagerBrowserTest.* -> 13 test cases. events_unittests (NOT ON FYI BOT) https://chromium-swarm-dev.appspot.com/user/task/2cffaa975ccae210 EventTest.AutoRepeat gfx_unittests (NOT ON FYI BOT) https://chromium-swarm-dev.appspot.com/user/task/2cffaab8afbdd110 ColorProfileTest.GetDisplayColorProfile RenderTextTest.TextDoesntClip installer_util_unittests https://chromium-swarm-dev.appspot.com/user/task/2cffaac18a1cca10 AdvancedFirewallManagerTest.AddRule interactive_ui_tests https://chromium-swarm-dev.appspot.com/user/task/2cffaabb8a275310 BrowserActionInteractiveTest.TabSwitchClosesPopup This is fixed net_unittests https://chromium-swarm-dev.appspot.com/user/task/2cffaaa107560810 CookieMonsterTest.DeleteAllForHost telemetry_perf_unittests https://chromium-swarm-dev.appspot.com/user/task/2cffaaa7a3752b10 7 failures. telemetry_unittests (NOT ON FYI BOT) https://chromium-swarm-dev.appspot.com/user/task/2cffaab478369610 telemetry.internal.browser.browser_unittest.ReferenceBrowserTest.testBasicBrowserActions unit_tests https://chromium-swarm-dev.appspot.com/user/task/2cffaabb3b1ca510 7 tests failed. 99 tests crashed. tests that are running/passing on the Win10 FYI bot as of now are: angle_unittests base_unittests browser_tests cacheinvalidation_unittests chrome_app_unittests chrome_elf_unittests components_unittests content_browsertests content_unittests courgette_unittests crypto_unittests device_unittests extensions_unittests gcm_unit_tests google_apis_unittests gpu_unittests installer_util_unittests interactive_ui_tests ipc_tests jingle_unittests media_blink_unittests media_unittests midi_unittests net_unittests ppapi_unittests printing_unittests remoting_unittests sbox_integration_tests sbox_unittests sbox_validation_tests setup_unittests skia_unittests sql_unittests sync_unit_tests ui_base_unittests unit_tests url_unittests views_unittests Eliminating the tests not on the FYI bot (which can be looked at later) - which are events_unittests, gfx_unittests, telemetry_unittests, and the tests that are alreayd fixed - BrowserActionInteractiveTest.TabSwitchClosesPopup on interactive_ui_tests this leaves (to be continued)
,
Mar 21 2016
it's complicated by the fact that the Chromium Win 10 FYI bot does not compile with dcheck_always_on=1 while the trybots do. This explains many of the differences.
,
Mar 21 2016
I'd recommend to enable dcheck_always_on=1 right away as a first step since https://build.chromium.org/p/chromium.fyi/builders/Chromium%20Win%2010/ is doing a Release_x64 build. This will likely expose more bugs.
,
Mar 21 2016
yup I created https://codereview.chromium.org/1821573002/ but I'm scared of turning the green bot red.
,
Mar 21 2016
Maruel - how easy would it be to stand up a trybot running on GCE/swarming for the passing tests? That would at least give us half-decent coverage and also prevent any regressions from sneaking in while I am fixing the other tests. The tests would be: accessibility_unittests app_list_unittests app_shell_unittests ash_unittests aura_unittests base_unittests battor_agent_unittests browser_tests cacheinvalidation_unittests cast_unittests cc_unittests chrome_app_unittests chrome_elf_unittests chromedriver_unittests components_browsertests compositor_unittests content_unittests courgette_unittests crypto_unittests device_unittests extensions_browsertests extensions_unittests gcm_unit_tests gn_unittests google_apis_unittests gpu_unittests interactive_ui_tests ipc_tests jingle_unittests libphonenumber_unittests media_blink_unittests media_unittests message_center_unittests midi_unittests mojo_common_unittests mojo_public_bindings_unittests mojo_public_system_unittests nacl_loader_unittests ppapi_unittests printing_unittests sbox_integration_tests sbox_unittests sbox_validation_tests setup_unittests skia_unittests sql_unittests sync_integration_tests sync_unit_tests telemetry_gpu_unittests ui_base_unittests ui_touch_selection_unittests url_unittests views_unittests wm_unittests we'd want to use the output from the 64-bit win builder.
,
Mar 21 2016
It's tricky because we have no way to differentiate between an ESX or a GCE VM at the moment. We only have ESX VMs on prod and only GCE VMs on staging.
,
Mar 21 2016
,
Mar 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build.git/+/b38504d09d36745afc701b9b921dd1aeeb1c531c commit b38504d09d36745afc701b9b921dd1aeeb1c531c Author: wfh@chromium.org <wfh@chromium.org> Date: Tue Mar 22 22:29:35 2016 Enable dcheck_always_on on Win 10 FYI bot. BUG=596344 Review URL: https://codereview.chromium.org/1821573002 git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/build@299429 0039d316-1c4b-4281-b951-d872f2087c98 [modify] https://crrev.com/b38504d09d36745afc701b9b921dd1aeeb1c531c/scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py [modify] https://crrev.com/b38504d09d36745afc701b9b921dd1aeeb1c531c/scripts/slave/recipes/chromium.expected/full_chromium_fyi_Chromium_Win_10.json
,
Mar 23 2016
,
Apr 28 2016
,
Jun 10 2016
,
Mar 13 2017
,
Jul 7 2017
,
Jul 7 2017
,
Jul 13 2017
Copying over from the other bug, smut@ set up a builder with the tests running on win10 on GCE here: https://luci-milo.appspot.com/buildbot/chromium.fyi/Chromium%20Win%2010%20GCE%20Tests We can use this for an up-to-date burndown list. Let us know if there is anything else we can provide to help get these tests passing.
,
Jul 14 2017
The link from #15 has changed. We now have two FYI builders, both of which test on the Win 10 GCE VMs: Built on Win 7: https://luci-milo.appspot.com/buildbot/chromium.fyi/Chromium%20Win%2010%20GCE%20Tests%20(Win%207%20Build)/ Built on Win 10 on GCE: https://luci-milo.appspot.com/buildbot/chromium.fyi/Chromium%20Win%2010%20GCE%20Tests%20(Win%2010%20Build)/ The following suites have failures: failed net_unittests on Windows-10 failed sbox_integration_tests on Windows-10 failed sbox_validation_tests on Windows-10 failed services_unittests on Windows-10
,
Aug 2 2017
,
Aug 17 2017
,
Aug 17 2017
wfh@ have you looked at the services_unittests failures, or is there a tracking bug for those?
,
Aug 17 2017
(I want to move the CQ bots to Win10 ASAP to reduce load in the golo to stuff that needs to run tests on win7 or bare metal where possible ...)
,
Sep 6 2017
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by wfh@chromium.org
, Mar 21 2016Labels: -Pri-3 Pri-2
Owner: wfh@chromium.org