You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.
Currently, I have a decent number of test failures, because my system isn't exactly what the test cases expect, at least some of them are due to that.
This poses a bit of a problem, given that ideally we would be able to run all tests successfully in a container without access to the host hardware, so we could run them during CI.
I am very much open to suggestions on how to manage this.
In a perfectly ideal world, it would be a docker setup with a real bluez stack, just with enough emulated hardware to pass all of our test cases.
I have a sneaking suspicion that this might not be a trivial undertaking.
The text was updated successfully, but these errors were encountered:
Currently, I have a decent number of test failures, because my system isn't exactly what the test cases expect, at least some of them are due to that.
This poses a bit of a problem, given that ideally we would be able to run all tests successfully in a container without access to the host hardware, so we could run them during CI.
I am very much open to suggestions on how to manage this.
In a perfectly ideal world, it would be a docker setup with a real bluez stack, just with enough emulated hardware to pass all of our test cases.
I have a sneaking suspicion that this might not be a trivial undertaking.
The text was updated successfully, but these errors were encountered: