🤖 Add average test runner run time to config.json#1937
Merged
Conversation
This commit 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. Its value has been populated by timing the execution time of running the test runner in Docker on one of the track's practice exercise. Clearly, the execution time will differ between exercises and between solutions, so this should be seen as a general indicator.
ErikSchierboom
added a commit
to ErikSchierboom/java
that referenced
this pull request
May 19, 2021
This commit 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. Its value has been populated by timing the execution time of running the test runner in Docker on one of the track's practice exercise. Clearly, the execution time will differ between exercises and between solutions, so this should be seen as a general indicator.
ErikSchierboom
added a commit
to ErikSchierboom/java
that referenced
this pull request
May 20, 2021
This commit 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. Its value has been populated by timing the execution time of running the test runner in Docker on one of the track's practice exercise. Clearly, the execution time will differ between exercises and between solutions, so this should be seen as a general indicator.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
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 exercism/docs#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
leapexercise, 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
exercism/v3-launch#35