-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ipv6 disabled on kernel cmdline disrupts Tox = most tests fail #2335
Comments
The errors in the current build all fail at:
Does anyone have a Vagrant file for spinning up machines to test Tox with different command lines? |
A year later and 2/2 more tests failed:
|
Interesting. I'll look into adding a qemu VM with Linux and ipv6 disabled. The code can deal with ipv6 not being provisioned, but maybe not with it being absent entirely. |
A qemu VM with Linux and ipv6 disabled would be really nice - it's black and white for me: I reboot the same system and run the same code the tests run clean. Thing is, it means I'm working in a greyzone: I've doing ctypes wrapping of the library into Python which will SEGV if you get it wrong. And I'm running that under a Qt GUI which is reported to SEGV on exit if it feels like it. I'll appreciate the test coverage. |
I disabled ipv6 on my nixos using
running it by itself:
|
thanks - my tests give more dramatic results; bear in mind i don't know C or ctest: does subprocess aborted mean a SEGv? What does auto_tests/auto_network_test do? It does nothing for me and returns 0: Here's my run on a 3 day old pull:
|
@emdee-is 's failure:
|
@Green-Sky I just pulled down the current repo: running behind tor: 93% tests passed, 4 tests failed out of 56 Total Test time (real) = 969.58 sec The following tests FAILED: I can increase the timeout_which needs to be big behind tor. Where does ctest get the names/IPs of the bootstrap nodes to connect to? #2467 If they are bad the tests will fail. |
I think the failure in proxy test is expected if you are behind a firewall - it assumes it has open access to clearnet to run a proxy. |
Signing this off as working - many thanks. I still get
but that's for other reasons: #2469 Please note that bootstrap and tcp_relay tests are the only tests that use the network. All the other ctests ate not testing real network-connected behaviour. |
ipv6 disabled on kernel cmdline disrupts Tox and most tests fail
Boot a linux with
ipv6.disable=1
and run the testsuiteAll the tests fail all at the same place.
Note that this is on a build with USE_IPV6 "Use IPv6 in tests" OFF in the CMakeLists.txt which just disables tests - no change to the library I think.
As most of the tests fail if you boot a linux with
ipv6.disable=1
and run the testsuite, booting a vm withipv6.disable=1
should be a test.The text was updated successfully, but these errors were encountered: