Open
Bug 1868483
Opened 1 year ago
Updated 1 year ago
Determine if we could and should use browsertimes extra profiler run equivalent (enableProfileRun)
Categories
(Testing :: Raptor, task, P3)
Testing
Raptor
Tracking
(Not tracked)
NEW
People
(Reporter: kshampur, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxp])
some relevant links for enableProfileRun
https://github.com/sitespeedio/browsertime/pull/1943
https://github.com/sitespeedio/browsertime/blob/a08b44677d9eb91edd5c83b32909ff599a56157b/CHANGELOG.md#1790---2022-04-19
https://github.com/sitespeedio/browsertime/issues/1942
if this works in a way that is exactly what we want (at the least, behaves like --extra-profiler-run) we should look into adopting this flag, and use this opportunity to clean up the code base a bit
Reporter | ||
Updated•1 year ago
|
Component: Performance → Raptor
Updated•1 year ago
|
Comment 1•1 year ago
•
|
||
I agree with seeing if we can move to using the browsertime one. That said, we'll have difficulty using it in it's current state with our customized tests that run multiple iterations within a single browser instance since it'll run for too long.
You need to log in
before you can comment on or make changes to this bug.
Description
•