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

Fix timing tests by using ranges #111

Merged
merged 1 commit into from
Jul 5, 2023

Conversation

directionless
Copy link
Member

I've noticed several failures on these tests. Generally, I think it's because GitHub Actions is on shared CPUs and prone to randomly pausing. This, in turn, makes the timing tests very squirrely

This is an attempt at converting from expected counts, to range checks I don't love it, and it's not going to catch all failures, but I'm not sure there's a better approach

I've noticed several failures on these tests. Generally, I think it's
because GitHub Actions is on shared CPUs and prone to randomly pausing.
This, in turn, makes the timing tests very squirrely

This is an attempt at converting from expected counts, to range checks
I don't love it, and it's not going to catch all failures, but I'm
not sure there's a better approach
@directionless directionless changed the title Use ranges on timing related tests Fix timing tests by using ranges Jul 5, 2023
@RebeccaMahany RebeccaMahany merged commit 5ee3d12 into osquery:master Jul 5, 2023
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