ERL-1124: inet_SUITE:t_gethostnative fails for s390x on travis

[OTP-Maintainer]

Original reporter: JIRAUSER13101
Affected version: Not Specified
Component: Not Specified
Migrated from: https://bugs.erlang.org/browse/ERL-1124

---

While trying to run tests in  travis job/build for s390x for master branch, one test case failure is observed for inet_SUITE:t_gethostnative with the following error:
inet_SUITE:t_gethostnative failed on line 696
Reason: case_clause
Whereas when ran manually on s390x VM, the test case passes. 

Can someone please help me in knowing the functionality of `t_gethostnative` at "https://github.com/erlang/otp/blob/master/lib/kernel/test/inet_SUITE.erl#L692" ? It will be really appreciated. 

Thanks in advance.

[OTP-Maintainer]

mikael pettersson said:

Please provide the full stack trace of that failed test case.

[OTP-Maintainer]

JIRAUSER13101 said:

Travis build logs:
1) https://travis-ci.org/garazdawi/otp/jobs/622590495 - (line no 2048)
2) https://travis-ci.org/erlang/otp/jobs/627756329 - (line no 2051)

Please let me know if anything else is needed from my side.

[OTP-Maintainer]

mikael pettersson said:

Thanks, the second one with the "try_again" bit hints that the error originates from erts/etc/common/inet_gethost.c translating a TRY_AGAIN or EAI_AGAIN error from the system components.  Possibly lib/kernel/src/inet_gethost_native.erl should retry in this case.

[OTP-Maintainer]

mikael pettersson said:

FWIW, I just got the same error in a trivial typo fixing branch on s390x in travis.  Looks like that CI pipeline is broken.

[OTP-Maintainer]

JIRAUSER13101 said:

Hi Mikael, yes it fails only on Travis CI and not when running the same test steps manually on s390x container/VM.

Can you please let us know possible reasons for the "try_again" error thrown for the failed test only on Travis CI ? or help us in understanding the functionality of t_gethostnative at "https://github.com/erlang/otp/blob/master/lib/kernel/test/inet_SUITE.erl#L692"
 Also, wondering if ipv6/ipv4 may cause  the issue.

Thanks.

[OTP-Maintainer]

JIRAUSER13101 said:

Any updates on this issue? 

[OTP-Maintainer]

mikael pettersson said:

This should have been fixed yesterday as [https://github.com/erlang/otp/pull/2458] was reverted.

[OTP-Maintainer]

JIRAUSER13101 said:

Hi Mikael, we want to fix it for s390x and add support for it in travis. 
Needed pointers in understanding the cause of failure.

[OTP-Maintainer]

mikael pettersson said:

The problem would seem to be outside of the Erlang VM, somewhere in the s390x travis pipeline.  It could be almost anything, from a configuration issue in that pipeline, glibc on s390x or the s390x linux kernel having some issue, or whatever host (VM? docker? Hercules? qemu?) this eventually runs on.  You'd need to run your own custom job in that pipeline to reproduce the issue and determine its origin.  I can't help you with that.