Skip to content

Conversation

@SimonFrings
Copy link
Contributor

Over time we recognized failing tests because of an incorrect time measurement in our tests which mostly occurred when running our test suite under windows. Last seen here: https://github.com/clue/framework-x/actions/runs/3741602828/jobs/6351445435

I raised the sleep-time inside the responsible test to avoid any future tests failing because of inaccurate clocks.

@SimonFrings SimonFrings changed the title Fix wrong measurement for inaccurate clocks in tests Increase sleep time to cover test case for inaccurate clocks Dec 21, 2022
@clue
Copy link
Owner

clue commented Dec 21, 2022

@SimonFrings Good catch, thanks for the update! Looks like this has been in place since #49 and has indeed repeatedly caused some false negatives when testing on Windows in the past.

@clue clue merged commit 9e97ad3 into clue:main Dec 21, 2022
@SimonFrings SimonFrings added this to the v0.13.0 milestone Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants