Summary: | =www-client/chromium-16.0.912.63 fails test DnsConfigServiceTest.GetSystemConfig with large /etc/hosts | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jonathan Lovelace <kingjon3377> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED UPSTREAM | ||
Severity: | minor | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://code.google.com/p/chromium/issues/detail?id=107810 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log (compressed) showing failing test |
Description
Jonathan Lovelace
2011-12-16 00:24:45 UTC
Created attachment 295985 [details]
Build log (compressed) showing failing test
This does not seem like a Gentoo-specific behavior to me. I think it would be better to deal with this upstream. Yes, this is probably not Gentoo-specific; I've now reported it upstream (see URL). But if this is confirmed it'd be a kindness to disable this test (or mark it as flaky, which I think lets it run but doesn't hard-fail the build on a test failure) until it's fixed, as the package does take (my machine) on the order of six hours to build. For what it's worth, after changing the 0.0.0.0s to 127.0.0.1 in my /etc/hosts the test still fails, so it's pretty clearly triggered by the *size* of my hosts file. This test is now skipped in chromium-18.x. |