Add script to capture travis build durations #2541
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@paulirish What is the unit on Y-axis? |
|
@stramel good question :). Y axis is time in seconds. |
brendankenny
approved these changes
Jun 21, 2017
There was a problem hiding this comment.
no clue about good ruby coding style, but seems like plausibly good code :) Time.now.to_date.prev_day($days_of_builds_to_consider).to_time is a sweet API.
Could wait for someone else with more ruby experience, but since it's pretty simple and since this is mostly for running on your machine, I'm good with it.
| def log_durations | ||
| repository = Travis::Repository.find('GoogleChrome/lighthouse') | ||
| repository.each_build do |build| | ||
| # next unless Integer(build.number) < 8283 |
There was a problem hiding this comment.
leaving it in in case people want to look for a specific range.
| repository.each_build do |build| | ||
| # next unless Integer(build.number) < 8283 | ||
|
|
||
| next if build.started_at.nil? |
There was a problem hiding this comment.
maybe add a comment mentioning when this would occur
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's the last 40 days of travis build durations:
Pretty cool data. Halfway down the X axis you'll see the variance kick off. AFAICT, this seems to be travis's fault. It starts right when the "fix appveyor" commits land on master. (around the #7972's of build numbers) But these commits ONLY touch appveyor.yml, so they couldn't matter less to Travis.
EDIT: i've amended the script to tag where the build is from so we can see just master branch builds too:
spreadsheet: https://docs.google.com/spreadsheets/d/197M4SRTdDbbpg4uRDCr-tI5l48L2qsAGkxIcIncKKew/edit#gid=0
cc @wardpeet