-
Notifications
You must be signed in to change notification settings - Fork 54
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
Gpio/update #256
Gpio/update #256
Conversation
vireshk
commented
Nov 29, 2022
@andreeaflorescu Some issues with builds here, timing out, any idea ? |
There seems to be some problem with the hosts on which we run the CIs and the first jobs that run will always timeout because they wait for the container to download. Even if the container is downloaded though the jobs take significantly longer to execute. @aghecenco did an initial investigation and it seems like all the threads are busy with epoll for some reason. We don't have a lot more details now, but we will prioritize this to find a fix. In the meantime, you can just retrigger the job and it should pass. This is not ideal, we'll keep you posted related to the fix. |
There is a legit failure from |
See rust-vmm/rust-vmm-ci#114 for the |
Tried. Still not passing. |
We're tracking the timeout issue here: rust-vmm/community#137 |
616e975
to
64a7e5d
Compare
The Rust language guidelines suggests not prefixing getters with get_. Remove the same from GPIO getters. https://rust-lang.github.io/api-guidelines/naming.html Signed-off-by: Viresh Kumar <[email protected]>
The libgpiod rust bindings got upstreamed recently. Migrate to the upstreamed version. Signed-off-by: Viresh Kumar <[email protected]>
@stefano-garzarella @mathieupoirier Can someone please review this ? |