New issue
Advanced search Search tips

Issue 860385 link

Starred by 1 user
Status: Assigned
Owner:
calamity@chromium.org
Cc:
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Flaky content_browsertests: WebUIMojoTest on Android

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jul 5 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of shimazu@chromium.org

These two tests are sometimes failing on Android.
WebUIMojoTest.NativeMojoAvailable
WebUIMojoTest.ChromeSendAvailable

Comment 1 by shimazu@chromium.org, Jul 5

Cc: dpa...@chromium.org
Components: Tests>Flaky UI>Browser>WebUI
Labels: Type-Bug
Project Member

Comment 2 by bugdroid1@chromium.org, Jul 5 

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

commit 9b7e69b3c8d37ad6a297fc957b2a88d62b12afdd
Author: Makoto Shimazu <shimazu@chromium.org>
Date: Thu Jul 05 04:22:12 2018

Disable a couple of WebUIMojoTest on Android

TBR=dpapad@chromium.org
NOTRY=true

Bug: 860385
Change-Id: If2d73018196f01b62fa30bda0bf9422d686409d4
Reviewed-on: https://chromium-review.googlesource.com/1126688
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#572704}
[modify] https://crrev.com/9b7e69b3c8d37ad6a297fc957b2a88d62b12afdd/content/browser/webui/web_ui_mojo_browsertest.cc

Comment 3 by shimazu@chromium.org, Jul 5

Labels: -Sheriff-Chromium
Removed sheriff flag since the tests are disabled.
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 5 

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

commit 297edf86b0cc494ad9ee2d645361808dd2f10954
Author: Makoto Shimazu <shimazu@chromium.org>
Date: Thu Jul 05 05:23:11 2018

Revert "Disable a couple of WebUIMojoTest on Android"

This reverts commit 9b7e69b3c8d37ad6a297fc957b2a88d62b12afdd.

Reason for revert: typo

Original change's description:
> Disable a couple of WebUIMojoTest on Android
> 
> TBR=dpapad@chromium.org
> NOTRY=true
> 
> Bug: 860385
> Change-Id: If2d73018196f01b62fa30bda0bf9422d686409d4
> Reviewed-on: https://chromium-review.googlesource.com/1126688
> Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
> Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#572704}

TBR=dpapad@chromium.org,shimazu@chromium.org

Change-Id: I98c9317199692cb1a585969148cca55476b86dd0
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 860385
Reviewed-on: https://chromium-review.googlesource.com/1126640
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#572710}
[modify] https://crrev.com/297edf86b0cc494ad9ee2d645361808dd2f10954/content/browser/webui/web_ui_mojo_browsertest.cc
Project Member

Comment 5 by bugdroid1@chromium.org, Jul 5 

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

commit 83c878752ae22f975a0861ec2f6114d2939a9db4
Author: Makoto Shimazu <shimazu@chromium.org>
Date: Thu Jul 05 05:27:12 2018

Reland "Disable a couple of WebUIMojoTest on Android"

This reverts commit 297edf86b0cc494ad9ee2d645361808dd2f10954.

Original change's description:
> Revert "Disable a couple of WebUIMojoTest on Android"
> 
> This reverts commit 9b7e69b3c8d37ad6a297fc957b2a88d62b12afdd.
> 
> Reason for revert: typo
> 
> Original change's description:
> > Disable a couple of WebUIMojoTest on Android
> > 
> > TBR=dpapad@chromium.org
> > NOTRY=true
> > 
> > Bug: 860385
> > Change-Id: If2d73018196f01b62fa30bda0bf9422d686409d4
> > Reviewed-on: https://chromium-review.googlesource.com/1126688
> > Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
> > Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#572704}
> 
> TBR=dpapad@chromium.org,shimazu@chromium.org
> 
> Change-Id: I98c9317199692cb1a585969148cca55476b86dd0
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 860385
> Reviewed-on: https://chromium-review.googlesource.com/1126640
> Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
> Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#572710}

TBR=dpapad@chromium.org,shimazu@chromium.org

Change-Id: I03c4a813c3aa5ac25c44da75fd61bd73ebfbf2f9
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 860385
Reviewed-on: https://chromium-review.googlesource.com/1126641
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#572711}
[modify] https://crrev.com/83c878752ae22f975a0861ec2f6114d2939a9db4/content/browser/webui/web_ui_mojo_browsertest.cc

Comment 6 by tasak@google.com, Jul 5

Owner: calamity@chromium.org

Comment 7 by calamity@chromium.org, Jul 5 

Flake example at http://bit.ly/2u5zRoE.

../../content/browser/webui/web_ui_mojo_browsertest.cc:222: Failure
Value of: NavigateToURL(shell(), GURL(kChromeUIMojoWebUIOrigin + path))
  Actual: false
  Expected: true

The NavigateToURL call is failing, which is pretty weird. Android device OOM perhaps?

We could try replacing the invalid navigation above it with a different URL?

Comment 8 by benhenry@chromium.org, Aug 2

Status: Assigned (was: Available)
►

Sign in to add a comment