Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add Travis CI support for arm64 architectures #705

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

Merged
merged 3 commits into from
Nov 25, 2020

Conversation

karlding
Copy link
Collaborator

@karlding karlding commented Oct 8, 2019

Add support for the arm64 architecture from Travis CI's alpha offering.
This enables the test suite to run within an arm64 LXD container (minus
the tests that exercise SocketCAN, as the image is missing the required
kernel modules).

Add support for the arm64 architecture from Travis CI's alpha offering.
This enables the test suite to run within an arm64 LXD container (minus
the tests that exercise SocketCAN, as the image is missing the required
kernel modules).
@karlding
Copy link
Collaborator Author

karlding commented Oct 8, 2019

Proof that the worker is running on arm64 from the job log:

worker_info
Worker information
hostname: [email protected]
version: v6.2.1-20-g4ca60c6 https://github.com/travis-ci/worker/tree/4ca60c69640778fbc5c3203c4f4360ff72b969f1
instance: travis-job-hardbyte-python-can-594982587 b4a942b48ea3f45374c56e146cbe9b9c2c36d834426519af11d977b3cc5f7ff6 (via amqp)
startup: 3.534169152s

@codecov
Copy link

codecov bot commented Oct 8, 2019

Codecov Report

Merging #705 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #705   +/-   ##
========================================
  Coverage    69.52%   69.52%           
========================================
  Files           70       70           
  Lines         6485     6485           
========================================
  Hits          4509     4509           
  Misses        1976     1976

@christiansandberg
Copy link
Collaborator

I don’t want to be boring and all, but what part of the library needs testing on specific architectures?

@karlding
Copy link
Collaborator Author

Not really specific architectures, but there's code that relies on various sizes and alignments of types. The only way to really cover that besides mocking is to run the tests on different build environments.

There's also #591 in the backlog which calls out ARM testing.

@christiansandberg
Copy link
Collaborator

I know SocketCAN and PCAN have some OS and architectural differences so if we could test against the actual drivers then there would definitely be a point. But if we can’t test the integration then I can’t see how that increases our confidence. It does consume more resources and requires future maintenance so I think we need to investigate which tests will benefit from this.

Copy link
Collaborator

@felixdivo felixdivo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like this an think it replaces & closes #591. The maintenance effort is reasonable and it checks some code for which it's worth.

@christiansandberg I agree that we should somehow limit it though. Testing only a single Python version is a good compromise there.

That's my opinion, this surely is disputable.

@felixdivo felixdivo added the QA about improving and maintaining the quality of the library label Jan 29, 2020
@mergify mergify bot requested a review from hardbyte November 16, 2020 00:19
@felixdivo
Copy link
Collaborator

How are we going to proceed on this? Letting this rot here isn't too helpful either.

Copy link
Owner

@hardbyte hardbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy to add it.

@hardbyte hardbyte merged commit 01bb3e9 into hardbyte:develop Nov 25, 2020
@hardbyte hardbyte mentioned this pull request Nov 25, 2020
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants