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

I22 connection tests did not fail when they weren't mocking #850

Closed
callumforrester opened this issue Oct 17, 2024 · 3 comments · Fixed by #868 · May be fixed by #851
Closed

I22 connection tests did not fail when they weren't mocking #850

callumforrester opened this issue Oct 17, 2024 · 3 comments · Fixed by #868 · May be fixed by #851
Labels
bug Something isn't working

Comments

@callumforrester
Copy link
Contributor

#847 appears to have been caused by #841 not passing mock=True to the DeviceInitializationController, that should have caused a timeout failure when the CI tried to connect to PVs that don't exist on its network, instead the tests passed after a very long time, suggesting that something was timing out but not failing the test, perhaps an exception was being swallowed.

This issue is to investigate and prevent recurrence

Acceptance Criteria

  • The cause of the non-failure is known
  • A regression test/tests are in place to prevent recurrence
@callumforrester callumforrester added the bug Something isn't working label Oct 17, 2024
@callumforrester
Copy link
Contributor Author

Tagging @DominicOram and @DiamondJoseph for awareness

@DiamondJoseph
Copy link
Contributor

make_all_devices returns the connected devices and also collects all of the exceptions that were raised.
As discussed, the tests should have accounted for checking the collected exceptions.

@rtuck99
Copy link
Contributor

rtuck99 commented Oct 25, 2024

This is fixed in #858

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants