Parents (Total: 9)

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

Key	Value
MD5	F6B3D8315B0B4651487E46FE0A367C05
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	DB9B4A4C2B930FFA284D183954CAF4C963EE74ED
SHA-256	FD9AFEE054F4F89FBAD0141BE73A6706DA5F856504B5D9F8A94EE1630382D7CC

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	A701E8A7EDCC43FEC680C7D27650F3A2
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	lp154.2.1
PackageVersion	2.0.2
SHA-1	8DB4D581ED6AC9B067375E276FF82F13A0AD84AF
SHA-256	A44F40E87C933449735857D0DE43F0BB69ADE192C53C038EBD66821F39A4D59D

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	D94C8162911D93CDEF380EA091E7D35D
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	9B8F5217318034DA15BD0A9AB012E8A9D7548FE5
SHA-256	457D8072C9A11A9668E58DE8AD093E5010201E72A1E260406AEF7CA35B692EE8

Key	Value
MD5	E2C69BD2824791F6086176EB22E11456
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	18.2
PackageVersion	2.0.2
SHA-1	E9BEB29102280A577532564F107FD804E178DF9F
SHA-256	A6DCC0F04A62FE87BEF6643C00749C5796290ECD04EA0791295E99EA5C78F00E

Key	Value
MD5	47C73179689BECC94105DE16189ABA39
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	F14FD8FDCD27005B7BF7D88EDE7EDA39B2510ABD
SHA-256	AB42784C76A682224E38D4461FE2A388CF3A82A0B848B2186E9EF79194B7D589

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