-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add changes for the final run #12
base: main
Are you sure you want to change the base?
Conversation
The change is based on feedback from discussion on Github mainly around filesystem cache bia in-between runs and ensuring correctness. * We now should run solutions against a bunch of input/output pairs of 1M rows each and verify that they produce the correct input and exit early if there is a failure. * We drop the Linux filesystem cache after syncing any dirty pages to Disk before each run. * The runner will now run for 10 times (5 more times) to ensure minimal variance, and also we will drop the two most outliers when counting the results (slowest and fastest solutions).
I will still need to test this on a live setting, and ensure that the changes are applied for all languages before we merge this. |
@@ -142,12 +163,33 @@ fn compute_verdict(output: &Path, expected_output: &Path) -> Result<Verdict> { | |||
output.read_to_string(&mut output_str)?; | |||
expected_output.read_to_string(&mut ex_output_str)?; | |||
if output_str.trim() != ex_output_str.trim() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will that mean solutions with an additional line in the end would fail ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why would they? (we still compare the trimmed version of both so it should be fine)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just double checking, as some submissions (most?) are adding a new line at the end
The change is based on feedback from discussion on Github mainly around filesystem cache bia in-between runs and ensuring correctness.