Skip to content

Added arm64 jobs for Travis-CI #18000

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
wants to merge 1 commit into from
Closed

Conversation

odidev
Copy link

@odidev odidev commented Jul 21, 2020

  • Modified ".travis.yml" to add Arm64 jobs for Travis-CI
  • Used conda to install pandas, pyzmq & Ipython.

@odidev
Copy link
Author

odidev commented Jul 22, 2020

@tacaswell,

As suggested in #16879, tried removing pandas but it was giving test errors. So, installing pandas using conda to resolve the timeout error and added some dependencies as well.

Please review and let me know if any changes required.

@@ -184,10 +216,10 @@ script:
# Each script we want to run need to go in its own section and the program
# you want to fail travis needs to be the last thing called.
- |
# The number of processes is hardcoded (-n2), because using too many
# The number of processes is hardcoded (-n4), because using too many
Copy link
Member

Choose a reason for hiding this comment

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

we get 4 usable cores on travis now?

Copy link
Author

@odidev odidev Jul 27, 2020

Choose a reason for hiding this comment

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

In Arm64, we can use more than two cores, please refer "https://travis-ci.community/t/nproc-reports-32-cores-on-arm64/5851/2". In amd64 it is picking 4 workers as well, but it maybe running on 2 cores only.
but it("-n4") has significant difference in time for Arm64 platform.

Copy link
Member

Choose a reason for hiding this comment

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

The core count wasn't the problem, it was opening too many Inkscape and Ghostscript processes, as noted in the comment below. Though now we pipe everything into a single Inkscape instance (and Ghostscript?) per process, so maybe that's not an issue.

.travis.yml Outdated
@@ -131,6 +151,18 @@ install:
git describe
# Upgrade pip and setuptools and wheel to get as clean an install as possible.
python -mpip install --upgrade pip setuptools wheel
- |
# Using conda to install pandas, pyzmq & ipython
Copy link
Member

Choose a reason for hiding this comment

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

can we skip the tests the rely on pandas and jupyter instead? I would rather not bring conda / conda-forge into the mix on travis if possible...

Copy link
Author

Choose a reason for hiding this comment

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

Sure, we can skip those tests for Arm64 platform. Updated the same.

@odidev odidev force-pushed the odidev_arm64 branch 5 times, most recently from d4d1c90 to 40f51f0 Compare July 29, 2020 04:27
@odidev odidev force-pushed the odidev_arm64 branch 2 times, most recently from b4d288b to e7651dd Compare August 6, 2020 14:28
@@ -184,10 +216,10 @@ script:
# Each script we want to run need to go in its own section and the program
# you want to fail travis needs to be the last thing called.
- |
# The number of processes is hardcoded (-n2), because using too many
# The number of processes is hardcoded (-n4), because using too many
Copy link
Member

Choose a reason for hiding this comment

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

The core count wasn't the problem, it was opening too many Inkscape and Ghostscript processes, as noted in the comment below. Though now we pipe everything into a single Inkscape instance (and Ghostscript?) per process, so maybe that's not an issue.

@odidev odidev force-pushed the odidev_arm64 branch 6 times, most recently from 11bdcff to 54333d9 Compare August 13, 2020 13:27
Copy link
Member

@dstansby dstansby left a comment

Choose a reason for hiding this comment

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

It looks like these new builds are still timing out - do we know why?

@@ -154,6 +154,10 @@ def check_alt_backend(alt_backend):
@pytest.mark.parametrize("toolbar", ["toolbar2", "toolmanager"])
@pytest.mark.flaky(reruns=3)
def test_interactive_backend(backend, toolbar):
# Skipping the test for Travis-CI on arm64 platform
if os.environ.get('TRAVIS_CPU_ARCH') == "arm64":
Copy link
Member

Choose a reason for hiding this comment

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

Does this need a default value (ie. os.environ.get('TRAVIS_CPU_ARCH', '') in case this environment variable isn't present?

@odidev odidev force-pushed the odidev_arm64 branch 2 times, most recently from b731d7d to f058b6a Compare September 21, 2020 13:01
Signed-off-by: odidev <odidev@puresoftware.com>
@QuLogic
Copy link
Member

QuLogic commented Mar 11, 2021

Thanks for working on this. Unfortunately, Travis seems to be kind of dead for us, so I'm going to close this PR. We do have wheels for aarch64 added in #19402.

@QuLogic QuLogic closed this Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants