New issue
Advanced search Search tips

Issue 700309 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Run tests on Linux Ozone buildbot

Project Member Reported by fw...@igalia.com, Mar 10 2017

Issue description

With the introduction of external window mode for [1], Linux Ozone starts to behave differently from Linux Ozone ChromiumOS. See for example [2] where new tests specific to external mode are added or [3] where some WindowManagerClient tests do not make sense in external mode.

I'm opening this bug to consider running some tests on Linux Ozone. We'll have to decide whether we want that and how many sets we want to run (probably at least mus, aura and mojo unittests?) or which configuration (headless, x11, wayland?).

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=666958
[2] https://codereview.chromium.org/2715533005/
[3] https://codereview.chromium.org/2740123002/
 

Comment 1 by fw...@igalia.com, Mar 10 2017

I opened the following bugs to at least run Mus WS and Mus Demo on headless:

https://chromium-review.googlesource.com/c/452481/
https://codereview.chromium.org/2739183002/

But tell me what you think about adding tests on the bot and the way to proceed.

Comment 2 by fw...@igalia.com, Mar 10 2017

I launched all the unittests locally today to compare Ozone/ChromeOS VS Ozone/LinuxOS (X11 and headless) and it seems I mostly get the same results (see below). Probably the failure and differences are due to my system configuration being different from the bot. Ideally I'd like to check on the bots, but I don't know how to do it. Anyway, my point is: which unit tests do we want to enable for the Ozone Linux bot? Only some Mus/Aura/Mojo/Ozone unittests? Or all the test suites like on the Ozone Chromium Linux bot?

--- chromeos-FAIL.txt
+++ linuxos-FAIL.txt
+[  FAILED  ] EndToEndTests/EndToEndTest.LargePostEarlyResponse/11
+[  FAILED  ] EndToEndTests/EndToEndTest.LargePostEarlyResponse/13
+[  FAILED  ] EndToEndTests/EndToEndTest.LargePostEarlyResponse/17
+[  FAILED  ] EndToEndTests/EndToEndTest.LargePostEarlyResponse/21
+[  FAILED  ] EndToEndTests/EndToEndTest.LargePostEarlyResponse/22
+[  FAILED  ] EndToEndTests/EndToEndTest.LargePostEarlyResponse/27
+[  FAILED  ] EndToEndTests/EndToEndTest.LargePostEarlyResponse/4
+[  FAILED  ] EndToEndTests/EndToEndTest.LargePostEarlyResponse/5
+[  FAILED  ] EndToEndTests/EndToEndTest.LargePostEarlyResponse/8
+[  FAILED  ] FilePathConversionTest.convert
+[  FAILED  ] FilePathTest.FromUTF8Unsafe_And_AsUTF8Unsafe
+[  FAILED  ] FilenameUtilTest.GenerateFileName
+[  FAILED  ] ProfileSyncServiceBookmarkTestWithData.MergeExpectedIdenticalModels
+[  FAILED  ] ProfileSyncServiceBookmarkTestWithData.Persistence
+[  FAILED  ] RTLTest.WrapPathWithLTRFormatting
+[  FAILED  ] SavePackageTest.TestSuggestedSaveNames
+[  FAILED  ] SysStrings.SysNativeMBAndWide
+[  FAILED  ] SysStrings.SysNativeMBToWide
+[  FAILED  ] SysStrings.SysWideToNativeMB
+[  FAILED  ] URLFixerTest.FixupRelativeFile

-[  FAILED  ] LayerTreeHostTilesTestPartialInvalidation.FullRaster_MultiThread_OneCopy
-[  FAILED  ] LayerTreeHostTilesTestPartialInvalidation.PartialRaster_MultiThread_OneCopy
-[  FAILED  ] LayerTreeHostTilesTestPartialInvalidation.PartialRaster_SingleThread_GpuRaster
-[  FAILED  ] ScreenMusTest.ConsistentDisplayInHighDPI
-[  FAILED  ] UIResourceLostBeforeCommit.RunSingleThread_DelegatingRenderer

Project Member

Comment 3 by bugdroid1@chromium.org, Mar 16 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5217bf718aa6da446b8acee61341b1f4ceab2248

commit 5217bf718aa6da446b8acee61341b1f4ceab2248
Author: fwang <fwang@igalia.com>
Date: Wed Mar 15 23:59:21 2017

Run Mus Demo and WS tests on Ozone Linux bot

For the related changes on chromium/tools/build, see
https://chromium-review.googlesource.com/c/452481/

BUG= 666958 ,700309

Review-Url: https://codereview.chromium.org/2739183002
Cr-Commit-Position: refs/heads/master@{#457270}

[modify] https://crrev.com/5217bf718aa6da446b8acee61341b1f4ceab2248/testing/buildbot/chromium.fyi.json
[modify] https://crrev.com/5217bf718aa6da446b8acee61341b1f4ceab2248/tools/mb/mb_config.pyl

Project Member

Comment 4 by bugdroid1@chromium.org, Apr 12 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f47783859bd6c4b4c363a1a4131c97c0abbaba98

commit f47783859bd6c4b4c363a1a4131c97c0abbaba98
Author: msisov <msisov@igalia.com>
Date: Wed Apr 12 09:06:37 2017

Add chrome compile target to Ozone Linux bot

Make bot not only run tests, but compile chrome as well to make sure
everything is in shape.

BUG= 666958 , 700309

Review-Url: https://codereview.chromium.org/2811853003
Cr-Commit-Position: refs/heads/master@{#463970}

[modify] https://crrev.com/f47783859bd6c4b4c363a1a4131c97c0abbaba98/testing/buildbot/chromium.fyi.json

Can this issue be closed now?
Status: Fixed (was: Untriaged)
Cc: msi...@igalia.com
Components: Internals>GPU>Testing
Labels: Proj-Ozone-Wayland Proj-Ozone
Status: Available (was: Fixed)
Not yet fixed to my satisfaction. Reopening.

Sign in to add a comment