Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Introduce current execution elapsed time when using --headless -t/--run-time
See original GitHub issueExecution time / running time not printed in the console when --headless
It quite difficult when cleaning the console (because the amount of stats printed even using 15s) for long load tests and not using a CI tool to keep track of remaining time.
Currently the print:
Name # reqs # fails | Avg Min Max Median | req/s failures/s
----------------------------------------------------------------------------------------------------------------------------------------------------------------
POST Request 17749 0(0.00%) | 112 58 3375 92 | 11.90 0.00
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Aggregated 17749 0(0.00%) | 112 58 3375 92 | 11.90 0.00
Adding after / before the running time HH:MM:SS?
Execution Time: 00:10:45 << here or maybe at the bottom >>
Name # reqs # fails | Avg Min Max Median | req/s failures/s
----------------------------------------------------------------------------------------------------------------------------------------------------------------
POST Request 17749 0(0.00%) | 112 58 3375 92 | 11.90 0.00
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Aggregated 17749 0(0.00%) | 112 58 3375 92 | 11.90 0.00
Execution Time: 00:10:45 << here >>
I don’t think there’s a need of knowing the remaining time, just showing the elapsed execution time would be enough.
Thanks
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
Observations running more than 5 million headless sessions a ...
Tip #1: Scale horizontally and not vertically. When running headless chrome, especially with puppeteer, it's really easy to scale horizontally.
Read more >Selenium java code runs test successfully but fails when run ...
My java selenium java test case with Chrome version 77 runs fine when options.setHeadless(false); but fails when I change this line options.
Read more >Getting Started with Headless Chrome - Chrome Developers
It's a way to run the Chrome browser in a headless environment. Essentially, running Chrome without chrome! It brings all modern web platform ......
Read more >bypass headless chrome detection · Issue #396 - GitHub
I need to understand how to execute js code in chromedp, as in puppeteer. Because every time after run chromedp.Navigate() values are reset...
Read more >Using Watir to run Selenium with Headless Chrome - Medium
The execution is over when you get a “Process finished with exit code 0” message, at which time a screenshot.png file is created...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m kinda struggling trying to debug the code, but no luck 🙃, so I’m still trying to get this done.
That’s excellent, yes you’re right, the additional line is a bad idea.
I will give it a go, it will take me some time but 🤷 will try some.