Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Journey duration calculation is way off #50

Closed
manuelkiessling opened this issue Mar 2, 2017 · 1 comment
Closed

Journey duration calculation is way off #50

manuelkiessling opened this issue Mar 2, 2017 · 1 comment
Assignees
@manuelkiessling
Labels
bug

Comments

@manuelkiessling
Copy link
Member

No description provided.

@manuelkiessling manuelkiessling self-assigned this Mar 2, 2017
manuelkiessling added a commit that referenced this issue Mar 2, 2017
@manuelkiessling
#50: Corrected calculation of journey duration.
d1ee702 
Instead of incorrectly summing up all request durations, we now calculate the difference between the start of the earliest starting request and the end of the latest ending request.
manuelkiessling added a commit that referenced this issue Mar 3, 2017
@manuelkiessling
#50: More robust journey duration calculation.
a3cc43e 
By accepting 'yyyy-MM-dd'T'HH:mm:ss.SSSxxx' and 'yyyy-MM-dd'T'HH:mm:ssxxx' as possible startedDateTime values in HARs.
@manuelkiessling
Copy link
Member Author

manuelkiessling commented Mar 3, 2017 •
edited
Loading

Commit a3cc43e neccessary due to lightbody/browsermob-proxy#616.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manuelkiessling manuelkiessling

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@manuelkiessling