In case of further questions, please open a thread at Multi CPU Architecture - Travis CI Community - it helps us to track your feedback and response whenever we have something adjusted.
I’m really glad you’re trying out the ARM builds. Thanks for the report!
Wrt to python stuff: that’s correct, it’s not present in os image yet (it’s C/C++ focused at the moment). We will add it soon and before it happens one can add before_install step (https://docs.travis-ci.com/user/installing-dependencies/) and run package installation.
Thanks for checking out ARM builds and reporting back.
Yes, Java support is not added yet (we’re working on os images structure for different languages to keep things starting up fast), so if one needed - please install relevant package in before_install step.
Convenience environment variable is not available yet - thanks for that question. It’ll be added over coming couple of weeks or so.
I the meantime, one can determine the arch of build box by running linux script/cli commands,
on ubuntu for example dpkg --print-architecture
or uname -m
I’m trying this for DPDK project. There is permission issue when setting hugepage which is required to run DPDK: https://travis-ci.com/Reyfone/dpdk/jobs/245236623
Used “sudo sh -c ‘echo 1024 > /proc/sys/vm/nr_hugepages’” in setup.sh.
After searching around, it came up to me apparmor policy denied access to some key system directory.
I’m not using any container in my CI configuration. Tried to turn off apparmor as suggested on above page, but didn’t succeed.
When building for amd64, which is VM based environment, the same command run successfully.
Can you suggest how to set hugepage in LXD environment?
Hi @Reyfone!
Happy to see you testing ARM based builds.
Our ARM support currently is powered by ARM+LXD - so your single build job actually is running within LXD container. This means accessing certain system folders or features, that can give access to the whole LXD host, are blocked by apparmor due to security reasons. See one of the topics where it’s been explained already and our updated Multi CPU Architecture documentation
Please re-post a query for huge pages support within LXD as a separate topic in ARM CPU Architecture category so we could track it and handle the answer. We’re gathering feedback on various use-cases, including also the ones where LXD itself is not sufficient due to security constraints.
We’ve just updated OS images for ARM builds within LXD (changelog here ) and this should cover some language scenarios as well. Could you re-run your build? If it fails back with the same error, please report as a separate topic in Multi CPU Architecture community forum?
This one was, as it appears, by design - until the job reaches ‘cancellable’ state, the cancel button should not appear.
Some fixes were done on refreshing the view and while job is reaching the ‘cancellable’ state, pending icon/animation should appear now.
On file system change - I am afraid it’s nothing you can do from .travis.yml . Keeping such a thread open may allow other users to see if they have demand for the same feature.
Thanks for testing out Arm builds! If the issue persists, would you mind to move it as a thread to https://travis-ci.community/c/environments/multi-cpu-arch/96 and provide link to the build job that actually resulted in that failure? Not much can be done on the error message itself.
Thanks for testing!
Java setup may be still missing, so if a Java packet needed, please install relevant package in before_install step and make sure environmental variables are set correctly.