Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests vulnerable to connectivity issues #181

Closed
vbabiy opened this issue Mar 15, 2011 · 1 comment
Closed

tests vulnerable to connectivity issues #181

vbabiy opened this issue Mar 15, 2011 · 1 comment
Labels
auto-locked Outdated issues that have been locked by automation type: bug A confirmed bug or unintended behavior

Comments

@vbabiy
Copy link
Contributor

vbabiy commented Mar 15, 2011

Because the tests work with actual remote servers, it's common to see false positives (i.e. failures that aren't bugs) in my buildbot. It would require some work, but it should be possible to set up mock interfaces that allow us to test all this stuff without actually going out over the network.


@carljm
Copy link
Contributor

carljm commented Apr 20, 2011

Closing this as a duplicate of #259, since the description there reflects the work that was done in GSoC 2010 to address this (but inadequately, IMO).

@carljm carljm closed this as completed Apr 20, 2011
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: bug A confirmed bug or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants