New issue
Advanced search Search tips

Issue 636726 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

"ChildProcessLauncherBrowserTest.ChildSpawnFail" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Aug 11 2016 
"ChildProcessLauncherBrowserTest.ChildSpawnFail" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 7 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyOQsSBUZsYWtlIi5DaGlsZFByb2Nlc3NMYXVuY2hlckJyb3dzZXJUZXN0LkNoaWxkU3Bhd25GYWlsDA.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

Comment 1 by hirosh...@chromium.org, Aug 15 2016

Labels: OS-Android
First failure: try run at 2016-08-10 00:02:02 UTC

The first failure time and the line of the failed assertion is the same as  Issue 636696 .
Perhaps the same issue?

Comment 2 by hirosh...@chromium.org, Aug 15 2016 

[FATAL:render_process_host_impl.cc(477)] Check failed: ::content::BrowserThread::CurrentlyOn(BrowserThread::IO). Must be called on Chrome_IOThread; actually called on CrBrowserMain.
(Stack trace not symbolized)
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/119625/steps/content_browsertests%20%28with%20patch%29%20on%20Android/logs/ChildProcessLauncherBrowserTest.ChildSpawnFail

Comment 3 by hirosh...@chromium.org, Aug 15 2016 

Hmm, already fixed? (Last failure was around 2016-08-11 00:00 UTC)

Comment 4 by sashab@chromium.org, Aug 16 2016

Status: Fixed (was: Untriaged)
►

Sign in to add a comment