>From the logs it looks like the JAVA_HOME isn't set. And when I looked at the job config it seems you've commented out that section.
Could you also file a JIRA? - the CLI should fail more gracefully when the JAVA_HOME isn't set. On Mon, 22 Jun 2020 at 13:36, Rahul Aggarwal < rahul.aggar...@puresoftware.com> wrote: > Hi sir, > > Thank you for the suggestion. Yes, pip2 install mock has solved the mock > import problem. > But I am again coming up with some test errors. I am linking my travis-ci > job logs below. > https://travis-ci.com/github/rahulgit-ps/storm/jobs/352331819 > I am guessing that the code is making some assumptions that are not working > for arm64 travis job. > Can you please review the travis logs? > > Regards > Rahul > > > > > On Mon, Jun 22, 2020 at 8:29 PM Govind Menon <govindappume...@gmail.com> > wrote: > > > What is the Python version which is showing the error? It's possible your > > default Python is also 3 - try pip2 install mock as well. > > > > On Mon, 22 Jun 2020 at 04:26, Rahul Aggarwal < > > rahul.aggar...@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. >
