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

Introduce FakeTimeProvider.AdjustTime #5192

Merged
merged 1 commit into from
Jun 1, 2024
Merged

Introduce FakeTimeProvider.AdjustTime #5192

merged 1 commit into from
Jun 1, 2024

Conversation

geeknoid
Copy link
Member

@geeknoid geeknoid commented May 31, 2024

This addresses #5072 by allowing time to be
adjusted forwards and backwards in order to simulate the system's clock being adjusted. Messing around
with the time in this way doesn't affect outstanding timers.

Microsoft Reviewers: Open in CodeFlow

Copy link
Contributor

Choose a reason for hiding this comment

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

Was this meant to be included or was it from working on #5191 ?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yep, makes sure we don't regress...

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh, sorry, that file shouldn't be there.

This addresses #5072 by allowing time to be
adjusted forwards and backwards in order to simulate
the system's clock being adjusted. Messing around
with the time in this way doesn't affect outstanding
timers.
@geeknoid geeknoid merged commit 300c3ca into main Jun 1, 2024
6 checks passed
@geeknoid geeknoid deleted the geeknoid/faketimer branch June 1, 2024 13:14
@github-actions github-actions bot locked and limited conversation to collaborators Jul 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants