Hi there, Thank you so much for this detailed information. I am glad to have a quick response from you. I got busy with my routine office stuff, so could not focus much on this package this whole week. Actually I am more focused towards adding arm64 support to travis-ci only, because of my professional commitments. I have tried something like this : 1. As pip and pip3 were causing issues, hence I changed the python version from 2.7 to 3. Now mock is getting installed successfully. Alternatively, we can also install mock using pip2 on python 2.7 . 2. Also, JAVA_HOME was getting set with jre, not jdk. So, I manually installed openjdk-11-jdk and then set JAVA_HOME according to it. That issue has been cleared now. 3. After that, I am getting issues related to swapon file permissions, and an unexpected interrupt in 3 out of 6 arm64 tests on travis-ci. I am linking my logs below. Plz have a look at those test cases with jdk 11 on arm64. TRAVIS-CI logs : https://travis-ci.com/github/rahulgit-ps/storm
I will keep sharing my findings. Hoping the same :) Thanks and Regards Rahul Aggarwal On Tue, Jun 23, 2020 at 8:54 AM Sheng Liu <liusheng2...@gmail.com> wrote: > Hi Rahul, > > Thanks for bringing this up. My colleague and I have done some attempts > about adding ARM CI support for Storm by using Travis CI. here is an > example of Travis results[1], we have also met some issues: > 1. The "No module named mock" error you have mentioned, that is because in > the Travis ARM container, the "pip" command refer to pip3 than pip2 that > cause mock cannot be correctly installed in python2 env, You take a > look[2]. > 2. Storm CI job frequently hang in Travis ARM CI[3], there are some issues > reported in Travis community, but no sulution currently. > 3. disk quota exceeded error also frequently occured on Travis ARM64 > container[4], this is also a common issue and has be metioned many times in > Travis community, but no solution currently. > > Because there are some issues about Travis ARM CI to run such a relative > heavy CI job, and seem no solution in the short term. I would like to > propose to use the OpenLab CI to provide the ARM CI for Storm community, > the OpenLab is a CI infrastructure we maintained for building CI jobs for > open source projects, we provide both x86 and ARM resources. We have > integrated many CI jobs for popular opensource projects in OpenLab please > see[5]. For an example, we have integrated the ARM CI for Pytorch community > in OpenLab CI recently, you can see the succeed building status of the > "Linux (aarch64) CPU" in [6] and the CI jobs [7]. > > any thoughts? > > [1] https://github.com/liusheng/storm/pull/4/checks > [2] https://github.com/liusheng/storm/pull/4/files > [3] > > https://travis-ci.community/t/output-is-truncated-heavily-in-arm64-when-a-command-hangs/7630/5 > [4] https://travis-ci.community/t/disk-quota-exceeded-on-ppc64le/8006/4 > [5] http://status.openlabtesting.org/projects > [6] https://github.com/pytorch/pytorch/blob/master/README.md > [7] http://status.openlabtesting.org/builds?project=pytorch%2Fpytorch > > On 2020/06/22 09:26:09, Rahul Aggarwal <r...@puresoftware.com> wrote: > > Hi Team,> > > > > I am adding arm64 support to storm's travis-ci with jdk 8 and 11.> > > During build, I am getting an error related to mock as below :> > > > > ImportError: No module named mock> > > > > I have manually installed mock via pip install mock and pip3 install > mock.> > > But the error is still the same.> > > Can you please suggest a resolution.> > > > > Thanks & Regards> > > Rahul Aggarwal> > > > > -- > > > > > > > > > > > *Disclaimer* -The information transmitted is intended solely for the > > > individual> > > or entity to which it is addressed and may contain confidential > > > and/or> > > privileged material. Any review, re-transmission, dissemination or > > > other use of> > > or taking action in reliance upon this information by persons > > > or entities other> > > than the intended recipient is prohibited. If you have > > > received this email in> > > error please contact the sender and delete the > > > material from any computer. In> > > such instances you are further prohibited > > > from reproducing, disclosing,> > > distributing or taking any action in reliance > > > on it.As a recipient of this email,> > > you are responsible for screening its > > > contents and the contents of any> > > attachments for the presence of viruses. > > > No liability is accepted for any> > > damages caused by any virus transmitted by > > > this email.> > > > -- *Disclaimer* -The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. In such instances you are further prohibited from reproducing, disclosing, distributing or taking any action in reliance on it.As a recipient of this email, you are responsible for screening its contents and the contents of any attachments for the presence of viruses. No liability is accepted for any damages caused by any virus transmitted by this email.
