-
Notifications
You must be signed in to change notification settings - Fork 633
Is Travis CI disabled? #1219
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
Comments
Well, the |
Maybe @hardbyte needs to grant Travis access rights again |
@hardbyte can you fix this? |
@hardbyte a little reminder: the socketcan tests are still not run |
Oh I'm so bad at checking notifications. Sorry! Taking a look now. First error is:
I tried deactivating a few users to see if that helps, but it looks very much like it wants my credit card which I'm reluctant to do. |
I think it should still work, but not quire sure. They aren't to clear on this. We have/had four things on travis
|
I also think having too many open issues is also not helping to keep on overview over what is going on. |
Yes, they want credit card info to avoid fake users/crypto miners. They will not charge you but i'd be hesitant too. |
Those last two items can be crossed off from changes in #1433
Would Qemu be an option for arm64 and maybe socketcan within docker? |
As far as I know, socketcan does not work within docker. Maybe this has changed but I doubt it. |
Oh that's right, I believe it can work but only when supported by the host kernel... which defeats the point in our case. I guess there is a small chance that vcan is now supported by the latest github worker images. |
This is obsolete since the socketcan tests run on github actions. Closing. |
The last Travis CI run was 7 months ago.
We still have our socketcan tests and mypy on Travis only. Also the Travis badge link is broken.
The text was updated successfully, but these errors were encountered: