-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Add Arm64 builds to Travis #5932
Conversation
52354c9
to
bdef03c
Compare
Hey @HouBingjian @guyuqi @cnqpzhang @wangxiyuan @Zhiwei-Dai, Travis-CI now offers builds on Arm64 based machines. Good news - I have added this to our We have two test cases which are failing on Arm64: The |
@adamretter good news. Looking forward for ARM support. And @Yikun can help with the ARM problem. some of the errors is included in the issues I created before. If you need arm VM for debugging, please let us know. We can provide for you. |
The |
I also run the
And the
But the
|
|
bdef03c
to
f0e26ca
Compare
@wangxiyuan I also just rebased to bring in any recent changes. |
f0e26ca
to
49d37a8
Compare
Things may have stabilized a bit for release (including #6024). I just did "make check" on master (f32a311) on our ARM64 instance on EC2, and only folly_synchronization_distributed_mutex_test failed consistently. Added PR #6126 for that. Inconsistent failures:
|
…6126) Summary: This test is crashing on ARM but is not yet production code. Let's not let it block ARM CI. See PR #5932 Pull Request resolved: #6126 Test Plan: ./folly_synchronization_distributed_mutex_test, on Linux/ARM, on Linux/x86_64, and with LITE=1 on Linux/x86_64 (also disabled) Differential Revision: D18836576 Pulled By: pdillinger fbshipit-source-id: d8a36eea2f048e8330411d994435d1c58a15d978
@pdillinger Thanks for your fix. Could you take a look at #5751 ? |
49d37a8
to
4f0d984
Compare
Thanks @pdillinger I have now rebased this on your fixes, let's see how she flies now... |
Now just a single failure in |
Closed #5751 it's passed now. |
@adamretter Cool, But when I ran
the java version is the same
But the gcc is not (it's 5.4.0 on ubuntu16.04):
|
Ah, I know why. Different legacy filter schema on ARM due to cache line size. Will prepare a PR |
@wangxiyuan it would probably be useful to examine the stack trace |
Summary: This test was recently updated but failed to account for Bloom schema variance by CACHE_LINE_SIZE. (Since CACHE_LINE_SIZE is not defined in our C code, the test now simply allows a valid result for any CACHE_LINE_SIZE, not just the current one.) Unblock #5932 Pull Request resolved: #6153 Test Plan: ran unit test with builds TEST_CACHE_LINE_SIZE=128, =256, and unset (64 on Intel) Differential Revision: D18936015 Pulled By: pdillinger fbshipit-source-id: e5e3852f95283d34d624632c1ae8d3adb2f2662c
f0bed2b
to
eaa8758
Compare
eaa8758
to
35bfc1c
Compare
…acebook#6126) Summary: This test is crashing on ARM but is not yet production code. Let's not let it block ARM CI. See PR facebook#5932 Pull Request resolved: facebook#6126 Test Plan: ./folly_synchronization_distributed_mutex_test, on Linux/ARM, on Linux/x86_64, and with LITE=1 on Linux/x86_64 (also disabled) Differential Revision: D18836576 Pulled By: pdillinger fbshipit-source-id: d8a36eea2f048e8330411d994435d1c58a15d978
Summary: This test was recently updated but failed to account for Bloom schema variance by CACHE_LINE_SIZE. (Since CACHE_LINE_SIZE is not defined in our C code, the test now simply allows a valid result for any CACHE_LINE_SIZE, not just the current one.) Unblock facebook#5932 Pull Request resolved: facebook#6153 Test Plan: ran unit test with builds TEST_CACHE_LINE_SIZE=128, =256, and unset (64 on Intel) Differential Revision: D18936015 Pulled By: pdillinger fbshipit-source-id: e5e3852f95283d34d624632c1ae8d3adb2f2662c
I tried TEST_GROUP=platform_dependent on local Arm64 host with Ubuntu-16.04 of different modes (VM, docker, LXD), and passed DBWALTest.TruncateLastLogAfterRecoverWithoutFlush test in all of them. |
I created a topic in Travis. Welcome to comment. 😃 |
35bfc1c
to
31d9988
Compare
Using #6436 instead |
Summary: This patch based on #5932 offers a better solution to add arm64 to TravisCI matrix. Really thank adamretter for initiating Arm CI setup. Difference comparing to amd64: 1. For CMake, as no official arm64 release ready on Kitware page, a third party (conda-forge) released one is used instead of building from source. The main reason is to save CI time. 2. Explicit export JAVA_HOME on arm64 3. Disable mingw test Signed-off-by: Yuqi Gu <yuqi.gu@arm.com> Pull Request resolved: #6436 Differential Revision: D20428505 Pulled By: pdillinger fbshipit-source-id: 81ef02435e41480bb71710b783d85ebf452ce926
Subsumes #5928