Skip to content
This repository has been archived by the owner on Aug 18, 2021. It is now read-only.

Look into including output of the 'window.performance.timing' object, in Jenkins' console log #202

Open
stephendonner opened this issue Jan 10, 2019 · 0 comments

Comments

@stephendonner
Copy link
Contributor

As a specific pieces of metadata to include, perhaps we should dump parts of, on in its entirety, the output from window.performance.timing, along with our current Jenkins console-log output, like so:

connectEnd: 1547060699269
connectStart: 1547060699269
​domComplete: 1547060699626
domContentLoadedEventEnd: 1547060699603
​domContentLoadedEventStart: 1547060699598
​domInteractive: 1547060699592
​domLoading: 1547060699364
​domainLookupEnd: 1547060699269
​domainLookupStart: 1547060699269
​fetchStart: 1547060699269
​loadEventEnd: 1547060699630
​loadEventStart: 1547060699626
​navigationStart: 1547060699267
​redirectEnd: 0
​redirectStart: 0
​requestStart: 1547060699351
​responseEnd: 1547060699365
​responseStart: 1547060699361
​secureConnectionStart: 1547060699267
​timeToContentfulPaint: 1547060699587
​timeToDOMContentFlushed: 1547060699615
timeToFirstInteractive: 1547060699603
​timeToNonBlankPaint: 1547060699587
​unloadEventEnd: 1547060699367
​unloadEventStart: 1547060699365 
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant