MANIFEST.in
author Simon Heimberg <simohe@besonet.ch>
Mon, 25 Nov 2013 22:00:46 +0100
branchstable
changeset 1370 d6cab997a43e
parent 238 e4a389eca1b9
permissions -rw-r--r--
run-tests: test result shows when a failed test could not start a server Failing to start a server happens regularly, at least on windows buildbot. Such a failure often has nothing to do with the test, but with the environment. But half the test output can change because some data is missing. Therefore this is worth an extended error message. Detect the server failure in the diff output because it is most reliable there. Checking the output only does not show if the server failure was expected. Old failure message when server start failed: Failed test-serve.t: output changed New message: Failed test-serve.t: serve failed and output changed [ original upstream message ]
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
191
4c3775e904b6 Add MANIFEST.in
Christian Ebert <blacktrash@gmx.net>
parents:
diff changeset
     1
# $Id$
4c3775e904b6 Add MANIFEST.in
Christian Ebert <blacktrash@gmx.net>
parents:
diff changeset
     2
4c3775e904b6 Add MANIFEST.in
Christian Ebert <blacktrash@gmx.net>
parents:
diff changeset
     3
include tests/test-keyword tests/test-keyword.out
220
943e1e1ea042 Include MANIFEST.in in dist; hgignore MANIFEST
Christian Ebert <blacktrash@gmx.net>
parents: 191
diff changeset
     4
943e1e1ea042 Include MANIFEST.in in dist; hgignore MANIFEST
Christian Ebert <blacktrash@gmx.net>
parents: 191
diff changeset
     5
include MANIFEST.in