Parents (Total: 5)

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

Key	Value
MD5	B28476175EC178EDBF18547393B78A42
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	bp153.1.20
PackageVersion	1.3.4
SHA-1	9591FAFADAEAD2100B1AFEBA857C553DF6A3FBBC
SHA-256	6F3B2A64229FFEFC6FB4439B759DB8E9613AEC394DD4F80D23ED5C3908D378A3

Key	Value
MD5	8FB027D45AF133B530351BD667464127
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	lp152.13.3
PackageVersion	1.3.4
SHA-1	76415AF31D4E974C58C321D05D36ED7B4A5E7E0F
SHA-256	23ED0165A8E9FDB23161FB89F6F85F0626C7A87772971B63FE7FFA0ECB31463D

Key	Value
MD5	7E054D6E8D8055F3D25634EE037B280A
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	lp152.1.1
PackageVersion	1.3.4
SHA-1	26196AC5CEC51809F7D5F7C01100B4A0AE812E78
SHA-256	FFB8D648F7CCBFBDEFE6518F35F8F1EFB8983FD8244299E72462D9AE211DDD3B

Key	Value
MD5	5D9B78A5060FEFB071F758DEECBF027B
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.4
SHA-1	B956510C15A7C90F0E2E4814A5B174440988ADE0
SHA-256	80D75AF890264716924EE8C975338AB822242755A17F8545E87DE17935F2632E

Key	Value
MD5	43F43BF880E07AC6C281DE6244F45C8A
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.4
SHA-1	849923C2266C64C0EB33E6AF1FACD38BFF032487
SHA-256	1CD62CB3856AD7237A491047CBB195B7D83D427033E12F039F66338E08EBE8AF