-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update MIB simulator #159
Update MIB simulator #159
Conversation
Now it behaves a bit more like the "real deal", where previously it would just silently accept STARTACQUISITION commands but ignore them. Also switch over `test_acquisition_triggered_control` to a non-draining sim and connection, as draining should no longer be the common case. We still have `test_acquisition_triggered_garbage` to have coverage for the draining case. Fix the control connection to properly parse the mpx prefix to make sure we don't get a short read from the control socket.
Previously, sequence numbers would be sent as they are in the file, but this is of course not correct - they need to continue monotonously. Only works in uncached mode, so enforce that. Also warn if the user specifies `max_runs` and not `continuous`.
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #159 +/- ##
==========================================
- Coverage 79.84% 79.49% -0.36%
==========================================
Files 35 35
Lines 3458 3491 +33
Branches 576 582 +6
==========================================
+ Hits 2761 2775 +14
- Misses 560 577 +17
- Partials 137 139 +2 ☔ View full report in Codecov by Sentry. |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Might increase the success chance when the CI machine is overwhelmed...
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know how one would write it but we're missing a test case in continuous
mode. Is that something that will be easier to add once the dependent PRs are merged?
Co-authored-by: Matthew Bryan <78845903+matbryan52@users.noreply.github.com>
Thanks for the review!
I also noticed that continuous mode is now one of the last remaining "blind spots" of coverage. And indeed, right now, the client part of continuous mode is only accessible using the low-level APIs, which will be replaced by the rust-based backend, so I'll add a test case in #161. |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor Checklist:
Reviewer Checklist:
/azp run libertem.libertem-live-data
passed