Long tasks are picked up from metrics collecting on slow devices
soulgalore opened this issue · comments
With tests running on a Moto G5 I could see long tasks happens after we stopped the Chrome trace log, meaning the task is picked up from when we get other metrics.
A workaround could be to get the long tasks first directly for Chromeium based browsers, and then run the collection of the rest of the metrics.
This has been fixed.