Parents (Total: 4)

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

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	7E1D93726C3DFF8A4363D6723CF9AD98
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.2
PackageVersion	2.0.2
SHA-1	C3BD9883A221F84C9BAE77562A1FE1AE0DCEAFF3
SHA-256	DD9282E9AE3DE63E3BD83AB7D3D6111F1C24A674D84F3A73F552FEECCD9C7E54

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	A5DCD1FF333F3DB159BF9FA79356F359
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.2
PackageVersion	2.0.2
SHA-1	C087A687966203048B22B005D5E35656A85FE5D4
SHA-256	77A0FBEA1748603FA24ADEDC6D8CC25B29D365FEFDB9B025E186EF6E9CDE3418