pkgsrc/devel/py-test-timeout/distinfo

$NetBSD: distinfo,v 1.6 2018/11/19 10:30:28 adam Exp $

SHA1 (pytest-timeout-1.3.3.tar.gz) = 855103ead70755a2af5c50726d543360e9b78bf8
RMD160 (pytest-timeout-1.3.3.tar.gz) = f04a8a7fac09d418609d73bb0ed18b74e164ed7c
SHA512 (pytest-timeout-1.3.3.tar.gz) = 633f5aee550d568e403b958f4490ecb828eb322811c9f18cfefb26613be4fc36da14232ecbef8666fcf2dc693a93674c00a853ab546ea8328a07ea34da79fb84
Size (pytest-timeout-1.3.3.tar.gz) = 11627 bytes
py-test-timeout: updated to 1.3.3 1.3.3 Fix support for pytest >= 3.10. 2018-11-19 11:30:28 +01:00			$NetBSD: distinfo,v 1.6 2018/11/19 10:30:28 adam Exp $
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
py-test-timeout: updated to 1.3.3 1.3.3 Fix support for pytest >= 3.10. 2018-11-19 11:30:28 +01:00			`SHA1 (pytest-timeout-1.3.3.tar.gz) = 855103ead70755a2af5c50726d543360e9b78bf8`
			`RMD160 (pytest-timeout-1.3.3.tar.gz) = f04a8a7fac09d418609d73bb0ed18b74e164ed7c`
			`SHA512 (pytest-timeout-1.3.3.tar.gz) = 633f5aee550d568e403b958f4490ecb828eb322811c9f18cfefb26613be4fc36da14232ecbef8666fcf2dc693a93674c00a853ab546ea8328a07ea34da79fb84`
			`Size (pytest-timeout-1.3.3.tar.gz) = 11627 bytes`