- Timestamp:
- Jan 28, 2016, 2:46:58 PM (7 years ago)
- Branches:
- asyncio, debian/master, debian/stretch-backports, jessie-backports, main, master, proxy-ticket, upstream
- Children:
- 4d2d182
- Parents:
- 29d3311
- git-author:
- Thomas Klute <thomas2.klute@…> (01/28/16 14:39:10)
- git-committer:
- Thomas Klute <thomas2.klute@…> (01/28/16 14:46:58)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
test/README
r29d3311 rb21bf4f 88 88 backend, and there is no technical requirement to use "runtests". 89 89 90 By default (if "unshare" is available and --disable-test-namespaces91 has NOT been passed to configure), each test case is run inside its 92 own network namespace. This avoids address and port conflicts with90 By default (if "unshare" is available and has the permissions required 91 to create network and user namespaces), each test case is run inside 92 its own network namespace. This avoids address and port conflicts with 93 93 other tests as well has the host system. 94 94 … … 127 127 The first two of these issues are avoided when the tests are isolated 128 128 using network namespaces, which is the default (see "Implementation" 129 above). 129 above). The ./configure script tries to detect if namespaces can be 130 used (some Linux distributions disable them for unprivileged 131 users). If this detection returns a false positive or you do not want 132 to use namespace isolation for some other reason, you can run 133 configure with the --disable-test-namespaces option. 130 134 131 135 In some situations you may want to see the exact environment as
Note: See TracChangeset
for help on using the changeset viewer.