Parents (Total: 8)

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

Key	Value
MD5	DE2B84813D21FA0F147CB4A8CDCC94C3
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	python2-pytest-timeout
PackageRelease	lp151.1.1
PackageVersion	1.3.3
SHA-1	F893DE2D79FF48F703B4ED87660E27FA6B419890
SHA-256	4A8EE759F6FDBA7DFF6F6AC941E2DD5FC926428A2BB6AAC3E4DB292D88456F25

Key	Value
MD5	44D7C097E4C1C62A8D88F2D1776BC02B
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.1.1
PackageVersion	1.3.3
SHA-1	A4502981FD7BC232E5F39BC9A6C1AE22FF845D15
SHA-256	78EE60F8AF20AF5409241788C1E9AA9B9732F27D52A8FD9001B8CF96AE3F75A0

Key	Value
MD5	245EC5B3AA48F5133BB249CAFCC11F56
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	python3-pytest-timeout
PackageRelease	lp151.1.1
PackageVersion	1.3.3
SHA-1	7422DC2386702269BC42F60520F5FAC11B553B55
SHA-256	D6EC28054DFA0BD33077215342D1763D36483870C7AA5D99413649E33A9660B7

Key	Value
MD5	9982CEEF8BC2C6AE34E6C55755B0F083
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.1.1
PackageVersion	1.3.3
SHA-1	73B2CE7538D7BCE8D929A742D587C80650C1E64A
SHA-256	ABE1B76CB3FA20EC5025CA5EBA4007D94BD56599D9A0BA2D2BD498FC65CB67C7

Key	Value
MD5	C7686BF57A2FD5A6508E6E1773AE737A
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	1.1
PackageVersion	1.3.3
SHA-1	6A02FF6BC379278E5A31576E147864A3E4E1BFB7
SHA-256	5D7408D452732CBA178E979BA26CBBA010B615C0AE19E87214F6F42A16E59221

Key	Value
MD5	4D42BBBBCDCA600073A5E67CAA8FE725
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.1.1
PackageVersion	1.3.3
SHA-1	CD97EA1271120ECA628A52C03959ED06533B3E33
SHA-256	C1E201B6A60F9E89FCD8BE65077A5B4763C029E98C0785AC6DC26C7D5A962BA6

Key	Value
MD5	E1AB2F693B3762768A2600B94FA4F383
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	1.1
PackageVersion	1.3.3
SHA-1	0EF64B0903DCD93C00EE505A5DDB564B43692CF7
SHA-256	52A3C0ECB1C0C78872779FB4DA1D153947999EA86250E5EC2E3E1A9D0D7AB5B0

Key	Value
MD5	74BB7923DCCC4D000C886E2E058FE1DF
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.1.1
PackageVersion	1.3.3
SHA-1	BF15D264EFD68800A6B267B2BE0340CA96B7A56A
SHA-256	982781549F3BDAC7FB7E6948D32837FABF2418D8A13FFF5927420B396F136B99