dotnet/runtime

Unit tests are failing if IPv6 is not configured

Open

#23,798 opened on Oct 10, 2017

View on GitHub
 (13 comments) (0 reactions) (0 assignees)C# (5,445 forks)batch import
area-System.Nethelp wantedtest-bug

Repository metrics

Stars
 (17,886 stars)
PR merge metrics
 (Avg merge 12d 11h) (661 merged PRs in 30d)

Description

I bump to this while running test on FreeBSD, however this issue is not OS specific. Some tests make silent assumption about IPv6 and they fail if system is not configured to meet that. This is unpleasant for anybody from community to run tests and get good pass.

The easy repro for Linux is: sysctl -w net.ipv6.conf.all.disable_ipv6=1 ./build-tests.sh

The expected behavior would be that tests needing IPv6 would be skipped. Right now, some tests even hang for very long time.

Contributor guide

Research direction
Identify the failing tests and add a conditional check to skip them if IPv6 is not available.
Tech stack
csharp
Domain
backendtesting
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70