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

stress_mt test improvement #1454

Open
mcuee opened this issue Feb 2, 2024 · 2 comments
Open

stress_mt test improvement #1454

mcuee opened this issue Feb 2, 2024 · 2 comments
Labels
test related to tests, split from example label

Comments

@mcuee
Copy link
Member

mcuee commented Feb 2, 2024

From here by @tormodvolden
#1447 (comment)

I think stress_mt needs some serious rework. It needs to differentiate between errors in init, enumeration or control requests.
Also add a third round without the open and control requests.

Ideally it could go through all devices single-threaded and record a baseline, then run multithreaded and see if there is a difference (assuming the same devices are still around). At least for the device count. This wouldn't be difficult to add either. It would be more work to keep track of which devices can be opened and be sent control requests or not.

@mcuee mcuee added the test related to tests, split from example label label Feb 2, 2024
@tormodvolden tormodvolden changed the title stress_mt test improbement stress_mt test improvement Feb 2, 2024
@tormodvolden
Copy link
Contributor

I have started on something in #1458.

@tormodvolden
Copy link
Contributor

On the macOS CI it can also get into an infinite loop it seems like: https://github.com/libusb/libusb/actions/runs/8991096355/job/24697895520 (been running 2 hours now). Not sure if it is our code spinning or if it is stuck in a call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test related to tests, split from example label
Projects
None yet
Development

No branches or pull requests

2 participants