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	31FC57E3C38FC9904CBEF1E031ADDF59
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	lp151.2.1
PackageVersion	1.3.0
SHA-1	8B319E0A081BFF336EE3C84C542D5499F1937B86
SHA-256	9DB80ED9359693B8B2AF889AEDA5D1D412569ACB49AC8CC4319CF38BC2273A83

Key	Value
MD5	56AB0C0357A8DD50E4EECB437E788714
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	lp150.2.1
PackageVersion	1.3.0
SHA-1	A638B9CCDA0041D4388ACBFD86D38C8DE2FF58FE
SHA-256	431DE81E902A4A385D639229B37D8A8468FE2AF86AD7ECB5F2A3680C1B7F2684

Key	Value
MD5	0F259CAA954694C150861A43CC85610E
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	python2-pytest-timeout
PackageRelease	lp150.2.1
PackageVersion	1.3.0
SHA-1	BD593C3DDE9695340B162C555B83CD1F3E4FF093
SHA-256	E2EDABE87F26B5468CF33D29B48E492D4C817588F7D31C39357DDF8DF8411E3E

Key	Value
MD5	4482308A6EAB04E48C15AEB52B3B06BA
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	python2-pytest-timeout
PackageRelease	lp151.2.1
PackageVersion	1.3.0
SHA-1	D954FF36DBFC24FA9ABF423A8683005164CE0DC8
SHA-256	73C90760563D5303FB7EB56BFEA5669CEB93AF87CF98E995237530DC56E93984