New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 693143 link

Starred by 2 users
Status: Archived
Owner: ----
Closed: Jul 26
Cc:
█ phajdan.jr@chromium.org
█ phajdan@google.com
rbasuvula@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Failed test on the first run, does not fail if run it separately.

Project Member Reported by dimaa@google.com, Feb 16 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
Tried on the latest chromium build

Run whole test suite:
1. ninja -C out/Default/ content/test:content_unittests
2. out/Default/content_unittests

Run failed test separately:
1. out/Default/content_unittests --gtest_filter="BrowserThreadTest.Release"

What is the expected behavior?

What went wrong?
[325/4652] BrowserThreadTest.Release (CRASHED)
Above is the test which crashed when we ran whole test suite.

But if we will run this test separately - it will pass.

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 
Flash Version:

Comment 1 by dimaa@google.com, Feb 16 2017 

The batch of BrowserThreadTest.Release test:

FrameConnectedBluetoothDevicesTest.Destruction_MultipleMaps
FrameConnectedBluetoothDevicesTest.DestroyedByWebContentsImplDestruction
BrowserAssociatedInterfaceTest.Basic
BrowserThreadTest.PostTask
BrowserThreadTest.Release
BrowserThreadTest.ReleasedOnCorrectThread
BrowserThreadTest.PostTaskViaTaskRunner
BrowserThreadTest.ReleaseViaTaskRunner
BrowserThreadTest.PostTaskAndReply
BrowserThreadTest.RunsTasksOnCurrentThreadDuringShutdown

Comment 2 by phajdan.jr@chromium.org, Feb 16 2017

Cc: phajdan@google.com phajdan.jr@chromium.org

Comment 3 by dimaa@google.com, Feb 16 2017 

Revision hash: 83d63d4b6acb4af448f5532f0ca7fee1828dae32

Comment 4 by dimaa@google.com, Feb 16 2017 

Tried to run smaller list of tests - just tests that were in batch  - got the same crash. 

out/Default/content_unittests --gtest_filter="FrameConnectedBluetoothDevicesTest.Destruction_MultipleMaps:FrameConnectedBluetoothDevicesTest.DestroyedByWebContentsImplDestruction:BrowserAssociatedInterfaceTest.Basic:BrowserThreadTest.PostTask:BrowserThreadTest.Release:BrowserThreadTest.ReleasedOnCorrectThread:BrowserThreadTest.PostTaskViaTaskRunner:BrowserThreadTest.ReleaseViaTaskRunner:BrowserThreadTest.PostTaskAndReply:BrowserThreadTest.RunsTasksOnCurrentThreadDuringShutdown"

Comment 5 by rbasuvula@chromium.org, Feb 17 2017

Cc: rbasuvula@chromium.org
Labels: TE-NeedsTriageHelp
This looks like out of scope for TE, hence adding the respective label for it to  triage further.
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 26 2017

Labels: Hotlist-Google
Project Member

Comment 7 by sheriffbot@chromium.org, Jul 26

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment