Bug #60511 | 5.5: Tests without ipv6 failing | ||
---|---|---|---|
Submitted: | 17 Mar 2011 12:50 | Modified: | 26 Apr 2012 18:59 |
Reporter: | Harald Reindl | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Tests | Severity: | S3 (Non-critical) |
Version: | 5.5.10 | OS: | Linux (Fedora 13/14 x86_64) |
Assigned to: | CPU Architecture: | Any |
[17 Mar 2011 12:50]
Harald Reindl
[17 Mar 2011 17:05]
Valeriy Kravchuk
These tests (some of them at least, based on test name) are checking if IPV6 support in MySQL works properly. Why shouldn't they fail if IPV6 usage is disabled at OS level?
[17 Mar 2011 17:38]
Harald Reindl
because myasld is multiple started explicitly with ipv6 and "110317 14:28:44 [ERROR] Can't create IP socket: Address family not supported by protocol 110317 14:28:44 [ERROR] Aborting" results in some hundret MB logfiles another reason is that you are unable to run the test-suite without "--force" to run all the following tests sorry but on an intranet-server nobody needs ipv6 the next 100 years and there are few setups out there using not 127.0.0.1 or unix-sockets and since it makes not sense crashing mysqld multiple the tests should be skipped if there is no ipv6 on os-level, with MySQL 5.0 the test-suite had no problem and did not write my filesystem full until make a seperate partition
[26 Apr 2012 18:59]
Sveta Smirnova
This was fixed in latest versions: currently if no ipv6 support exists tests are just skipped, don't fail.
[15 May 2012 19:59]
Bas Meijer
In 5.5.24 ipv6 based tests still fail, and it is unclear how this was "fixed", no explanation how this is detected