Get travis to run timing scripts

[Alizter]

Can we create a travis job that can run the timing scripts? When we create a PR one of the things we would like to do is to see how it compares with master. Currently we have to run the script manually, which can change deepening whose machine it is running on. Getting travis to do this would standardize the timing changes somewhat and make it less work for us.

I would suggest comparing the timing of master with the timing of the PR merged. We should be able to pop into the travis job and quickly see the table generated.

[JasonGross]

I can have Travis display the timing table for the current PR if it doesn't already, but the Travis machines aren't reliable enough, in my experience, to see accuracy of more than +- 10% or 20%. And although the absolute timing changes depending on the machine, I expect relative timing to be roughly the same across machines.

[Alizter]

@JasonGross This has been done now right?

[JasonGross]

Pull requests do not compare timing against master. We could have them do this though.

[JasonGross]

However, they do display the timing tables without any comparison

[Alizter]

@JasonGross It would be nice if we can have a job for PRs that compare their build against master. What would need to be done?