-
Notifications
You must be signed in to change notification settings - Fork 38
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
Python test test_set_aperture
failing
#1401
Comments
According to @elmjag, this might be related to a timing issue, so the test passes sometimes and the other times it fails. If I understood correctly he made an attempt at a fix in this commit elmjag@9e65579. |
The problem comes from the evaluation of the size of the slits. If the slits are smaller than the aperture, than the beam size is taken from the slits and the test_set_aperture fails systematically with 'A100' == 'slits'. The problem is intermittent, because the test are using random aperture size, so when A100 is not used, the tests pass.
While waiting for the SlitMockup to be changed and to make it take the values from the configuration file, I vote for 1. |
Oh yes, now I see it. The problem is the fact we pick new aperture randomly. I suggest that, at least for now, we just always pick the first aperture from the available list. It works and it is still a good test on the In general I think using randomness in these kind of tests is problematic. If we want to test switching to different aperture sizes, we should make a parameterized test instead. We want to keep our test suite as deterministic as possible. |
Very good, as the ApertureMockup is also deterministic - A5 is the firs value ans A10 is the one set in the init. |
As pointed out in these:
it seems like
test_set_aperture
is failing... sometimes.The text was updated successfully, but these errors were encountered: