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
Setup regular ARM testing #87
Milestone
Comments
avtikhon
referenced
this issue
in tarantool/tarantool
Dec 17, 2019
Added ARM architecture for testing release and debug Tarantool builds on Travis-ci. Close #4270
avtikhon
referenced
this issue
in tarantool/tarantool
Dec 17, 2019
Added ARM architecture for testing release and debug Tarantool builds on Travis-ci. Close #4270
avtikhon
referenced
this issue
in tarantool/tarantool
Dec 20, 2019
Added ARM architecture for testing release and debug Tarantool builds on Travis-ci. Close #4270
avtikhon
referenced
this issue
in tarantool/tarantool
Dec 20, 2019
Added ARM architecture for testing release and debug Tarantool builds on Travis-ci. Close #4270
avtikhon
referenced
this issue
in tarantool/tarantool
Dec 20, 2019
Added ARM architecture for testing release and debug Tarantool builds on Travis-ci. Close #4270
avtikhon
referenced
this issue
in tarantool/tarantool
Dec 20, 2019
Added ARM architecture for testing release and debug Tarantool builds on Gitlab-CI. Close #4270
avtikhon
referenced
this issue
in tarantool/tarantool
Dec 20, 2019
Added ARM architecture for testing release and debug Tarantool builds on Gitlab-CI. Close #4270
ARM64 now in our pipelines. I don't see any interest in other ARM variants. It there anything to track here? |
Looks like no. So closing the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently ARM-build for Tarantool are prepared using on-demand strategy.
That means, that at any moment of time we cannot say for sure that
ARM-compiled Tarantool is working.
Let's do this:
This all relates to ARM-HF, 32b.
ARM64 looks broken on luajit side right now.
The text was updated successfully, but these errors were encountered: