luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-27 07:56:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

tests/network-monitor: Always use the dummy proxy resolver

Browse Source 
If glib-networking is installed and built with libproxy support, this
test will use it. If a proxy is set in the environment, we might get
correctly told to go through it for certain accesses. However, this isn't
going to work, because the testsuite monkeys with the network monitor to
tell it that all addresses - including the proxy - aren't reachable.

We're trying to check if adding networks to a GNetworkMonitor works in
general. Proxies just get in the way here, so let's use the built in
dummy proxy resolver which just tells us that all URLs are directly
accessible.

https://bugzilla.gnome.org/show_bug.cgi?id=794801
This commit is contained in:
Iain Lane 2018-03-29 11:39:15 +01:00 committed by Philip Withnall
parent d0364b4438
commit e4227408b2
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
gio/tests/network-monitor.c
View File

@ -543,6 +543,16 @@ main (int argc, char **argv)
g_test_init (&argc, &argv, NULL);
/* GNetworkMonitor will resolve addresses through a proxy if one is set and a
* GIO module is available to handle it. In these tests we deliberately
* change the idea of a reachable network to exclude the proxy, which will
* lead to negative results. We're not trying to test the proxy-resolving
* functionality (that would be for e.g. glib-networking's testsuite), so
* let's just use the dummy proxy resolver, which always pretends the
* passed-in URL is directly resolvable.
*/
g_setenv ("GIO_USE_PROXY_RESOLVER", "dummy", TRUE);
init_test (&net127);
init_test (&net10);
init_test (&net192);