Closed thehajime closed 9 years ago
oh... does #12 cause the crash ? With nuse/HEAD f4718be at a my environment, arch/sim/test/nuse/nuse-test.sh that ping to loopback works fine. If NUSECONF is not set, nuse_config_parse does not run (it means that process has a loopback interface only). https://github.com/thehajime/net-next-nuse/commit/f4718be83c5f427d73c35199e6343f0b9a406cef#diff-8b32e742271fcbcbb8ab0f2c7692d6adR429
Travis CI
6nsc: IPv6 over IPv4 tunneling driver
Segmentation fault
if succeed
6nsc: IPv6 over IPv4 tunneling driver
6NET: Registered protocol family 17
6NET: Registered protocol family 15
It seems that a cause is load tunneling driver or register protocol family 17 (IPPROTO_UDP). Travis environment issue ?
no, #12 is okay. the problem was the issue of Travis CI (as you were aware of): travis-ci/travis-ci#1503 when the test uses TAP device.
but now the problem is in NUSE, which cannot run on Travis environment. I guess some of symbols which NUSE is using now doesn't exist on the particular version of glibc. more to be debugged.
commit 52e261db5383d1874e605425052c578ba12e43e2 fixes this issue. The loopback ping test is enabled again (4c85f917d16dc542770495fd0b6aa279e5199126) and Travis CI is now happy !
https://travis-ci.org/libos-nuse/net-next-nuse/builds/41878427
currently, crashed on Travis CI (https://travis-ci.org/thehajime/net-next-nuse/builds/41203974).