Parents (Total: 13)

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

Key	Value
MD5	F91F3A01CA29FD035E13DF237328DD46
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	bp153.1.20
PackageVersion	1.3.4
SHA-1	39FA68D8F638DF74A60A73025463DE51C0B4653B
SHA-256	16E35C98C20B948D424542222925DBACBEE77C7299C4351785FCEB657DCB83D9

Key	Value
MD5	21CBEF92700956780A84ABF14015C770
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.4
SHA-1	6DF92406613C650CDA9B815B824E53D621E6903A
SHA-256	16CF1C0D9C94D6036EDBC27F8CD1B6EF54760C89476C4DB1F490C862032B64AF

Key	Value
MD5	138A4F859A51F054B545AC2A3852FE71
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://www.suse.com/
PackageName	python3-pytest-timeout
PackageRelease	1.6
PackageVersion	1.3.4
SHA-1	C84E8A111CF59558C277D5808D2E77BFB51861B2
SHA-256	ED67B7D7507AF8131E6543D274EDBDEFF58FFE6DD5B9951FAE2C3EC526756786

Key	Value
MD5	F5763B4CE7B8DDD2A41B81DA7F3CA5D0
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.
PackageMaintainer	Fedora Project
PackageName	python3-pytest-timeout
PackageRelease	2.fc32
PackageVersion	1.3.4
SHA-1	683765E28F60B2330B493BCAFD21DCA00C4C269E
SHA-256	7B481D030E2A294A815BF9844A67D9D5574BE36A4AFBFD0B99544D4CC7C59CBF

Key	Value
MD5	39B81F05F61CAB921A7A30D080170733
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	lp152.1.1
PackageVersion	1.3.4
SHA-1	1264AF5ACFE4CDD4D542BD1F44781649F4DE8C0C
SHA-256	2528E0FE1D04E209B1F96B74BA6D02C47F7C914E525E42C8D25FC3CEB5641497

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	2D9A65AB9BC606889CD31C6050ED3439
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.3
PackageVersion	1.3.4
SHA-1	D2F422C159238EAC77C230D4770EEB1770B30CF7
SHA-256	33BD35AB249B21A1F3EFF928AD6F227BEA9C4121507A0A1A897D6D83759A8FD5

Key	Value
MD5	7F802A1C7DB9A413AF9D683D8A106531
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.13.3
PackageVersion	1.3.4
SHA-1	8B0B168472182D0889E85D14F5BE956E0CCC76A4
SHA-256	EA1D2FD5A1F2A90ABFC9F94F8933EF89E3475B9631106A82C72F4B30AB0720FC

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

Key	Value
MD5	2107796798AFDACD45E63201011B68DA
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.4
SHA-1	91D6BF68E3016BDDBC78C60EE98D3129B33A8F36
SHA-256	CA0DAB617AECD7728AB9F25B216FBC1A864DCC1DA0E5B2CBB8440948E5949612