Skip to content

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

Closed
zariiii9003 opened this issue Jan 16, 2022 · 12 comments
Closed

Is Travis CI disabled? #1219

zariiii9003 opened this issue Jan 16, 2022 · 12 comments
Labels
QA about improving and maintaining the quality of the library testing

Comments

@zariiii9003
Copy link
Collaborator

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.

@zariiii9003 zariiii9003 added testing QA about improving and maintaining the quality of the library labels Jan 16, 2022
@felixdivo
Copy link
Collaborator

Well, the .travis.yml file is still in the repo.

@zariiii9003
Copy link
Collaborator Author

Maybe @hardbyte needs to grant Travis access rights again

@zariiii9003
Copy link
Collaborator Author

@hardbyte can you fix this?

@zariiii9003
Copy link
Collaborator Author

@hardbyte a little reminder: the socketcan tests are still not run

@hardbyte
Copy link
Owner

Oh I'm so bad at checking notifications. Sorry! Taking a look now.

First error is:

We are unable to start your build at this time. You exceeded the number of users allowed for your plan. Please review your plan details and follow the steps to resolution.

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.

@felixdivo
Copy link
Collaborator

I think it should still work, but not quire sure. They aren't to clear on this.

We have/had four things on travis

  • test socketcan -> probably hard to replace
  • arm64 builds -> ?
  • building documentation -> easy to move to Github actions (isn't it alread moved here, so can't we delete it from travis?)
  • deploy to PyPI -> easy to move

@felixdivo
Copy link
Collaborator

I also think having too many open issues is also not helping to keep on overview over what is going on.

@zariiii9003
Copy link
Collaborator Author

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.

Yes, they want credit card info to avoid fake users/crypto miners. They will not charge you but i'd be hesitant too.

@hardbyte
Copy link
Owner

Those last two items can be crossed off from changes in #1433

  • building documentation - Indeed already migrated. I've just removed that part from travis config.
  • deploy to pypi just moved

Would Qemu be an option for arm64 and maybe socketcan within docker?

@felixdivo
Copy link
Collaborator

As far as I know, socketcan does not work within docker. Maybe this has changed but I doubt it.

@hardbyte
Copy link
Owner

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.

@zariiii9003
Copy link
Collaborator Author

This is obsolete since the socketcan tests run on github actions. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA about improving and maintaining the quality of the library testing
Projects
None yet
Development

No branches or pull requests

3 participants