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 temptronic test timing issue #1110

Merged

Conversation

BenediktBurger
Copy link
Member

Closes #1106

This should solve the problem: reducing the time limit.
It's brute force, but I do not see any other option.

Copy link

codecov bot commented May 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.48%. Comparing base (92175a1) to head (bc56d16).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1110   +/-   ##
=======================================
  Coverage   58.48%   58.48%           
=======================================
  Files         262      262           
  Lines       18198    18198           
=======================================
  Hits        10643    10643           
  Misses       7555     7555           
Flag Coverage Δ
unittests 58.48% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@bilderbuchi
Copy link
Member

Don't have this instrument, but this change looks fine to me.. a 5% jitter in timing on various systems would not concern me, and it's only in test code anyway.
👍

@BenediktBurger
Copy link
Member Author

Thanks for the review!

@BenediktBurger BenediktBurger merged commit e364f44 into pymeasure:master May 21, 2024
18 checks passed
@BenediktBurger BenediktBurger deleted the fix-temptronic-test-timing branch May 21, 2024 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI fails due to timing issue occasionally
2 participants