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	1C506DB59C4A6BBD4A48061559EEB56A
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	python36-pytest-timeout
PackageRelease	17.10
PackageVersion	1.4.2
SHA-1	588347EE3ED7232112BC90AA05FA6527F7F2C596
SHA-256	9418463355EFDA54E129A9983C3AD2D630EF202A3782FC359C7EF429266FF81C

Key	Value
MD5	3487EFF3242920F06255DEB6857C84A8
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	python36-pytest-timeout
PackageRelease	1.3
PackageVersion	1.4.2
SHA-1	B08EE7A70143DA395EA1E0B1D5E2A4F839DBA94D
SHA-256	257774C10E5487D69BF6347464A4C3966175A64A831C19A90E011B591128DA47

Key	Value
MD5	0298FBD033B6B51CC9D488C0BA2E2CE1
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.5
PackageVersion	1.4.2
SHA-1	3105262E83DDB75465E5DA7B8C81ABA714D906B8
SHA-256	EA2FF3C3026E4951CB1628CA4E075F4EC3F525EC8128FDBFE4694F164294B187

Key	Value
MD5	77AE5AC6DF368C0C4F3ABF1BCC6CA0AC
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.14
PackageVersion	1.4.2
SHA-1	EEDE280AB1F29524B8B73F7EC57E5B9FA6015D8D
SHA-256	3B470B7FE41AB368376C681B3CF989FDB9D5930200DFC1AC307550704141D643