Parents (Total: 23)

The searched file hash is included in 23 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	722B77ABD1962A157784CE3C3BF7B55C
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageName	python38-pytest-timeout
PackageRelease	18.1
PackageVersion	2.0.2
SHA-1	0168D0892751DCC22BB28AF710849544D94A1FC8
SHA-256	B407AE7EA17CC8BEA8E3E4A24D20720C55112B7048923A197744FDA716748BDD

Key	Value
MD5	62558C3CE30CDFA88B94EF5F115665EF
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageName	python3-pytest-timeout
PackageRelease	2.1
PackageVersion	2.0.2
SHA-1	03768E1706F31DC8447376C0F94A1A49073EFFDA
SHA-256	09A0D26FDBC60133671973F2038BA56DAC64BE8A657AA006B51F9656A2CB3A6B

Key	Value
MD5	6DA0910FE3ECD2D5A15BA9F11939DD27
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageName	python3-pytest-timeout
PackageRelease	2.1
PackageVersion	2.0.2
SHA-1	051C811E728B6A9A2C8D195B1F58D32D37DABCD2
SHA-256	B54F3EA9B504F9AE63C6AE55D5E17B34928CF998A92A085F5D108DDA63999DA0

Key	Value
MD5	8C6DC97EBC4A73EBC0E526B91050D99E
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageName	python3-pytest-timeout
PackageRelease	lp153.2.1
PackageVersion	2.0.2
SHA-1	0A0BC64C2411ADA68F9DB28F5F32CB9F53821C56
SHA-256	6448DD3B5E5B5D1A85A008C91640590AEDDD346C1081F681D889B56C1B7AA60B

Key	Value
MD5	877C5B9EFDC1DE7D49EFF9A16CE8C1D3
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python39-pytest-timeout
PackageRelease	1.1
PackageVersion	2.0.2
SHA-1	0CABD43F9B1394701088FF9C8A7D7C65ED328946
SHA-256	4BF7591D250F6CC5288773FFE0A04856A02BAC01573600E2FF8DA5B316564E22

Key	Value
MD5	113F1F4F0F22525B98F08D0C378E91FB
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python38-pytest-timeout
PackageRelease	1.1
PackageVersion	2.0.2
SHA-1	361F08B7A8157F40155FA7AF974DA389FF15DD9D
SHA-256	C79D1172DF39D72092358C971F93952C62AAE350D48BA354873E9A99FFFB36BF

Key	Value
MD5	88FEA309DB63C6F4C09DC689516559E5
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageName	python310-pytest-timeout
PackageRelease	18.1
PackageVersion	2.0.2
SHA-1	3C3E800660FC23B07110F61A374E36655B940642
SHA-256	B1EF30FAC9C9724424D08C97E764967B02676425297D5E230A4D3A10F28928B4

Key	Value
MD5	00345E7B30FFBB7A6D897EAFD7DE800D
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageName	python3-pytest-timeout
PackageRelease	lp152.2.1
PackageVersion	2.0.2
SHA-1	3F9AAC8C32FDAC7A9A1FE3041125743BBEDE7AF6
SHA-256	885C063352C80BFE40F1C42D1D0F22A36CD0A0AC4704DA1D684D791B7DF2C1B6

Key	Value
MD5	B01D68D168CD4E0DB8580E4A37DFBA9D
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageName	python3-pytest-timeout
PackageRelease	lp153.18.1
PackageVersion	2.0.2
SHA-1	5408EA84360175E55AE9D2EB886482A6DBCE5725
SHA-256	F1DF66B35131A9E4D39E47D7FFE01D574EA4A5AF45B534B75EC1D2D0A2D79823

Key	Value
MD5	392CC6957CD9B05AB8A0FA58F9C40E63
PackageArch	noarch
PackageDescription	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. See below for detailed information on the timeout methods and their side-effects.
PackageName	python310-pytest-timeout
PackageRelease	18.2
PackageVersion	2.0.2
SHA-1	876984CB9916EAB310F0C20A619CBC9385B9F59C
SHA-256	1A5931F7B1A84A57FC574572590CB31C1AC2F738C931DEDC66382735AD5978C6