-
Notifications
You must be signed in to change notification settings - Fork 667
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
Potential issues with the test codes: tostring bug when using Python 3.9 #373
Comments
Since we do not support legacy Python versions, I think the following simple fixes will do.
|
Once I applied the above simple patch, it is now running better and the two failed cases are expected.
|
@jonasmalacofilho The patch here says "Merge #332: support pytest (disables currently unsuable hardware tests)". |
That makes sense,
What firmware configuration did you use?
I no longer remember what I was thinking when I merged that PR, but it certainly makes sense to keep the hardware tests enabled in |
Thanks for merging the patch. As for the firmware configuration, I am building Wander's FW as is. I was wrong to say that there were no isoc endpoints. But isoc transfer may not work well under libusb Windows. So it is kind of expected.
|
Running log under macOS Big Sur (Mac Mini M1): the errors are not expected. I need to check further.
|
Tests seem to be okay under Linux. This was probably the main platform Wander tested.
|
On the other hand, I think USB PICs are not that popular. ARM based is probably more popular. I will explore Linux Gadget based solution as well. Unfortunately my Raspberry Pi 2, 3B+ and Raspberry Pi 400 are not supporting USB OTG, only USB hosts. I will need to dig out my other NanoPi and Orange Pi boards. |
Close this issue for now. I will talk about tests related topics in #235. |
I understand that the HW based test has been disabled. However, it seems to me that I can still run it and there are a few error messages which may point to the errors of the test codes (probably they are not matching with the latest pyusb codes).
I just built the bmfw from Wander (https://github.com/walac/bmfw) and here is the run log. I am using Python 3.9.5 within a virtual environment under Windows 10 64bit. The two failed cases are kind of expected because my FW built configuration may not match the test code (for example no isochronous endpoint). But the two errors may be a problem.
The text was updated successfully, but these errors were encountered: