Benchmarking the jest script

[elicwhite]

The goal is to benchmark the jest script to monitor and analyze the test suite run time over time using https://github.com/TheSavior/timing-stats.

At the end of the build, there will be a file called build_times.json. This is specified in the package.json file. It will append the current results to whatever the content of that file is. If CI pushes back to master this is trivial. In order to push to a different branch, we'll need to check out the other branch before running add-temp-timing-to-json and then pushing.

[thymikee]

These benchmark times will be heavily affected by the load on Travis servers, so I'm worried this will be unreliable

[elicwhite]

Sorry, I don't think I added enough context since I've been talking to @cpojer for a while about this. Here is a blog post draft that walks through part of the goal for this type of data.

I think part of this will be an exploration of the data. While travis load surely changes, we may still be able detect trends or bigger problems. I think it could be reasonable to explore this and decide if we get anything valuable out of it.

[cpojer]

Thanks!

We'll probably try to see if the new benchmarking feature inside of Jest may work for this: #3026 and then come back to your PR. I'm super interested to see if CI is stable enough to track this long-term.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.