kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/py-test-timeout/Makefile

20 lines
546 B
Makefile
Raw Normal View History

pytest from versioned deps.
2020-05-16 19:38:39 +02:00
# $NetBSD: Makefile,v 1.10 2020/05/16 17:38:40 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.4 1.3.4 Give the threads a name to help debugging. Changed location to https://github.com/pytest-dev/pytest-timeout because bitbucket is dropping mercurial support.
2020-01-07 09:48:43 +01:00
DISTNAME= pytest-timeout-1.3.4
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
PKGNAME= ${PYPKGPREFIX}-${DISTNAME:S/py//}
CATEGORIES= devel python
MASTER_SITES= ${MASTER_SITE_PYPI:=p/pytest-timeout/}
MAINTAINER= pkgsrc-users@NetBSD.org
py-test-timeout: updated to 1.3.4 1.3.4 Give the threads a name to help debugging. Changed location to https://github.com/pytest-dev/pytest-timeout because bitbucket is dropping mercurial support.
2020-01-07 09:48:43 +01:00
HOMEPAGE= https://github.com/pytest-dev/pytest-timeout
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
COMMENT= Py.test plugin to abort hanging tests
LICENSE= mit
pytest from versioned deps.
2020-05-16 19:38:39 +02:00
PYTHON_VERSIONED_DEPENDENCIES= test
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
USE_LANGUAGES= # none
.include "../../lang/python/egg.mk"
pytest from versioned deps.
2020-05-16 19:38:39 +02:00
.include "../../lang/python/versioned_dependencies.mk"
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
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink