We will auto-merge this PR shortly. No action is required
This PR adds a new test_runner.average_run_time key to the config.json file. The purpose of this field is allow the website to show a progress bar while the test runner runs. The average run time is defined in seconds with one digit of precision.
We've pre-populated the average run time value by timing the execution time of the test runner in Docker on the example solution of the bob exercise, repeating that 4 more times, and then averaging the execution times. Clearly, the actual average execution time will differ between exercises and solutions, so this should be seen as very general indicator.
This is mostly a stop-gap solution for now. We'll revisit this in 6 months time or so.
We will auto-merge this PR shortly. No action is required
This PR adds a new
test_runner.average_run_timekey to theconfig.jsonfile. The purpose of this field is allow the website to show a progress bar while the test runner runs. The average run time is defined in seconds with one digit of precision.For more information, see https://github.com/exercism/docs/pull/130
We've pre-populated the average run time value by timing the execution time of the test runner in Docker on the example solution of the
bobexercise, repeating that 4 more times, and then averaging the execution times. Clearly, the actual average execution time will differ between exercises and solutions, so this should be seen as very general indicator.This is mostly a stop-gap solution for now. We'll revisit this in 6 months time or so.
Tracking
https://github.com/exercism/v3-launch/issues/35