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	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

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	9252270C9F54D6BBD696594E4870D944
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	A5147BE966B56A44F855D28D70B33C6F8BAC424C
SHA-256	5E3C6D17C1E05924C8E36983BB0916A526B2A19DD2B2D44818EB365C6497D322

Key	Value
MD5	D790D70BD6BED499D59A995684A61249
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	python310-pytest-timeout
PackageRelease	1.1
PackageVersion	2.0.2
SHA-1	E7A298F0188BA01AD4C3C44E692C521F6D60BC02
SHA-256	D7389B1BCA3342D138E07BB7D01991275D76B7687E7A136DB7DDAC19FF899008