Brian Kroth

For the record, one of the goals here is to be able to get some better stats on how long tests take. See Also #67

The other reason we were discussing this was in the course of troubleshooting #67 and trying to figure out which tests were taking a long time. I had written this...

@grlap for visibility

Related #55 @amueller to comment further on whether or not we should have the notebooks checked in with content in the repo or leave that for the webpages. I do...

This would be a great way to start incorporating @nhprog's GoogleBenchmark/PAPI efforts and some of the context stuff that @amueller started #60

@grlap for visibility

This currently times out after 6hrs even though the timeout on the job is higher. I'm guessing we run into some Github Action runners limits.

Seems that didn't work. https://github.com/microsoft/MLOS/actions/runs/318951578

@byte-sculptor can you look into just decreasing the length of those long haul runs to say 5 hours 55 minutes instead?

For the record, one of the goals of doing this would be to gain some confidence that the fix we applied in #206 (`n_samples = 5000`) is a good one.