Skip to content

Fix unreliable clock epoch tests #1277

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

Merged
merged 1 commit into from
Feb 17, 2023
Merged

Conversation

oldnewthing
Copy link
Member

The clock epoch tests are sensitive to CPU speed and the precise moment the clock ticks over from one second to another. Change the way we do epoch tests so that they are not affected by either factor.

This fixes a spurious CI test failure where the test environment was 3 milliseconds too slow.

https://github.com/oldnewthing/cppwinrt/actions/runs/4195918696/jobs/7276654213

The clock epoch tests are sensitive to CPU speed and
the precise moment the clock ticks over from one second
to another. Change the way we do epoch tests so that
they are not affected by either factor.

This fixes a spurious CI test failure where the test
environment was 3 milliseconds too slow.

https://github.com/oldnewthing/cppwinrt/actions/runs/4195918696/jobs/7276654213
Copy link
Collaborator

@kennykerr kennykerr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this annoyance!

@kennykerr kennykerr merged commit 4e674c7 into microsoft:master Feb 17, 2023
@oldnewthing oldnewthing deleted the clock-test branch February 17, 2023 22:51
@kennykerr
Copy link
Collaborator

A few more unreliable tests... https://github.com/microsoft/cppwinrt/actions/runs/4208012719 🙄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants