Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upFailing test #1962
Comments
This comment has been minimized.
This comment has been minimized.
|
Perhaps the test wants the negative response from the network that srv.name.one.example.org doesn't exist. And yes, that's something we should avoid. |
beorn7
added
area/testing
kind/bug
labels
Sep 8, 2016
This comment has been minimized.
This comment has been minimized.
|
@dmilstein it seems you added that test. Do you have time to rewrite it to not depend on a internet connection / working DNS discovery? |
This comment has been minimized.
This comment has been minimized.
|
Drat, didn't realize it was actually resolving. Yep, I'll take a look and fix that. Sorry about that, iPhone brevity in effect
|
dmilstein
added a commit
to dmilstein/prometheus
that referenced
this issue
Sep 8, 2016
grobie
added a commit
that referenced
this issue
Sep 8, 2016
This comment has been minimized.
This comment has been minimized.
|
Fixed with #1966 |
grobie
closed this
Sep 8, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
TheTincho commentedSep 8, 2016
Hi,
When building prometheus 1.1.1 for Debian, I have one test failing:
I don't know if this is really trying to access the network or not. In any case, it is a problem: Debian builds are forbidden from trying to access the network at all.
This is running with golang 1.7