pkgsrc/devel/py-test-timeout/distinfo

$NetBSD: distinfo,v 1.1 2017/10/19 06:52:03 adam Exp $

SHA1 (pytest-timeout-1.2.0.tar.gz) = 6895457de75f39992af318693136fd05d2c825f7
RMD160 (pytest-timeout-1.2.0.tar.gz) = 3e0674c33446d700105f90fc1c7afcf252bfe932
SHA512 (pytest-timeout-1.2.0.tar.gz) = b86548843e9ff8c8f7d1c39735025cdfa98befe2860e2a8a5d422d08bd7f542032384f147125a2a2841268154cc3a3874ef0aa4765d454fd5390edb773b106ae
Size (pytest-timeout-1.2.0.tar.gz) = 13258 bytes
This is a plugin which will terminate tests after a certain timeout. When doing so it will show a stack dump of all threads running at the time. This is useful when running tests under a continuous integration server or simply if you don't know why the test suite hangs. Note that while by default on POSIX systems py.test will continue to execute the tests after a test has timed, out this is not always possible. Often the only sure way to interrupt a hanging test is by terminating the entire process. As this is a hard termination (os._exit()) it will result in no teardown, JUnit XML output etc. But the plugin will ensure you will have the debugging output on stderr nevertheless, which is the most important part at this stage. 2017-10-19 08:51:11 +02:00			$NetBSD: distinfo,v 1.1 2017/10/19 06:52:03 adam Exp $

			`SHA1 (pytest-timeout-1.2.0.tar.gz) = 6895457de75f39992af318693136fd05d2c825f7`
			`RMD160 (pytest-timeout-1.2.0.tar.gz) = 3e0674c33446d700105f90fc1c7afcf252bfe932`
			`SHA512 (pytest-timeout-1.2.0.tar.gz) = b86548843e9ff8c8f7d1c39735025cdfa98befe2860e2a8a5d422d08bd7f542032384f147125a2a2841268154cc3a3874ef0aa4765d454fd5390edb773b106ae`
			`Size (pytest-timeout-1.2.0.tar.gz) = 13258 bytes`