Hostname addon to fix openjdk7 buffer overflow. Issue 2651 #145
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In both the recent
https://travis-ci.org/jythontools/jython/jobs/535576706
and original
https://travis-ci.org/jythontools/jython/jobs/313613197#L728
we see:
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/libnet.so(Java_java_net_Inet4AddressImpl_getLocalHostName+0x1a5)
which suggests
travis-ci/travis-ci#5227
... is the culprit. Also, the FTP job failure shows the following:
0.00s$ hostname
travis-job-f506d6d7-075f-46e9-a40c-7245b966dcae
... which is pretty long.
The recommended fix is to use the hosts addon
https://docs.travis-ci.com/user/hosts/
Darjus applied an early workaround to the travis config in c547fb5, but there is now a more standard one available, and maybe the old one doesn't work any more.
CI has run, with expected number of failures and no buffer overflow crash in
test_builtin
. Since the issue is intermittent and depends on the hostname assigned, this is partial evidence. However the job log does show the hostname change being applied.