Skip to content
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

test case haul before 2.2 #24119

Merged
merged 1 commit into from
Sep 17, 2024
Merged

Conversation

metagn
Copy link
Collaborator

@metagn metagn commented Sep 16, 2024

closes #4774, closes #7385, closes #10019, closes #12405, closes #12732, closes #13270, closes #13799, closes #15247, closes #16128, closes #16175, closes #16774, closes #17527, closes #20880, closes #21346

@ringabout ringabout merged commit fe55dcb into nim-lang:devel Sep 17, 2024
16 checks passed
Copy link
Contributor

Thanks for your hard work on this PR!
The lines below are statistics of the Nim compiler built from fe55dcb

Hint: mm: orc; opt: speed; options: -d:release
174419 lines; 8.246s; 654.344MiB peakmem

Araq pushed a commit that referenced this pull request Sep 22, 2024
Added in #24119, the test checks if every string produced is equal, but
the value of the strings depend on the `now()` timestamp of when they
were produced. 30 of them are produced in a for loop in sequence with
each other, but the first one is set after the data is marshalled into
and unmarshalled from a file. This means the timestamp strings can
differ depending on the execution time and causes this test to be flaky.
Instead we just make 2 strings from the same data and check if they
equal each other.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment