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

Issue 752843 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Performance is not increasing with --headless option for the automation test cases

Reported by tejes...@gmail.com, Aug 7 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
1. Executed multiple tests with browser and without browser(--headless option).
2. Could not find any changes in execution duration.  
3. In both ways the test execution taking same time. Even sometimes tests executed in less time with browser than --headless option?
4. Is this option(I mean --headless option) for only running the tests without browser or for any thing else.

What is the expected behavior?
Expecting the test execution duration should become less with --headless option.

What went wrong?
Could not find any changes in execution duration.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 60.0.3112.90  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

Please let me know your comments ASAP
 
Components: Internals>Headless
Cc: eseckler@chromium.org skyos...@chromium.org altimin@chromium.org alexclarke@chromium.org
Status: Available (was: Unconfirmed)
Adding OWNERs of headless/OWNERs
Labels: Needs-Feedback
This really depends on what you're testing. For instance if your tests are rendering-heavy, they may (currently) be slower with headless since there is no GPU acceleration. Can you provide a way to reproduce this result?
Project Member

Comment 4 by sheriffbot@chromium.org, Aug 9

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
Closing as WontFix as we don't have enough data to investigate this further. We will reopen this bug if new information becomes available.

Sign in to add a comment