Result for F84FB1AFDCF69BE2841947D5DBD86CBA9FE2181D

Query result

Key Value
FileName./usr/share/doc/packages/python39-pytest-timeout/README.rst
FileSize10742
MD5D628CDB95F5F0EBABEEFC24C4CD83A14
SHA-1F84FB1AFDCF69BE2841947D5DBD86CBA9FE2181D
SHA-256CF94644EAFC65907C9E6AB1B68DE37E88B2D2A4ADD7413E18498B0574D42116C
SSDEEP192:f2KgkrjhwjQciweNQiAKvole7uMTKcKHlU0KibztB2bA:fRvPh3c5eNQPKv2e7uMTbKlKm+A
TLSHT1552284032A4767B10796866953BE60E7F332C2BD52A75598B8DEC118230273883BBAD5
hashlookup:parent-total14
hashlookup:trust100

Network graph view

Parents (Total: 14)

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

Key Value
MD554C64C07384D9CF5C344E5BAA3A1A6A5
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython38-pytest-timeout
PackageRelease3.2
PackageVersion1.4.2
SHA-1555CDB49F8F3C6A6F9C8BD5354768C71E9013486
SHA-256A1D7365525B718216C93B751C292A903ED4356AA2E25362462FF2D184F10BBFA
Key Value
MD5F86623732FF674B79869FF2694DF75E9
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython38-pytest-timeout
PackageRelease17.10
PackageVersion1.4.2
SHA-10498E7723FD9F1300EF42621DACB2E5DC4964D8A
SHA-2560A6D6F5105876049198F910C6A7AF5D9EFE90D10E1AB22F39ACE282E591E73E2
Key Value
MD521DF9427BD048D29485B68189E30DB62
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython38-pytest-timeout
PackageRelease3.1
PackageVersion1.4.2
SHA-1B3A09F8CD237481395EE8E275D2BC931E283295E
SHA-256AB8893FEE9FCAB22E857A71195CA67E7E39826D390F0B237250E4188466256B2
Key Value
MD54860F7435B8740C338A35410B0BF93AE
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython39-pytest-timeout
PackageRelease1.3
PackageVersion1.4.2
SHA-19FC15A9DF3775DAE50A4AA0320755E1C6C47F16B
SHA-256905C9F86793FE6F4B696455ECCAC8CB575E0BD60A436802A33B6936158C3F292
Key Value
MD56A4DC553FE3AC98EFA41498886945CF4
PackageArchnoarch
PackageDescriptionThis 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.
PackageMaintainerFedora Project
PackageNamepython3-pytest-timeout
PackageRelease2.fc33
PackageVersion1.4.2
SHA-1562FBA8749EFD8BC0AFA63F05F2D1BF96A575ADA
SHA-256DCE1882EDE219417E880D4BCA5A3FB504167873EE004ADB9EA0BE544E3C75065
Key Value
MD5E374AFC6CB353E9CDB20EC577B2F9AFD
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython39-pytest-timeout
PackageRelease17.10
PackageVersion1.4.2
SHA-1172222EB9C1EB19F0A2D0239A0B8BE82A0FCEC17
SHA-25688CE3A9F3BC32731ABAC14166AA5BECD7029A80D9DA63D3805416E6547619984
Key Value
MD516C953DD04787680D0E710769F407653
PackageArchnoarch
PackageDescriptionThis 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.
PackageMaintainerFedora Project
PackageNamepython3-pytest-timeout
PackageRelease3.fc34
PackageVersion1.4.2
SHA-10405470EA65F189148E45064FC404C8B0F43D73F
SHA-256FD71BCBD00B1875CFB2B00C75DD4A4D891EC2C8893F52377F31A58FCCB522235
Key Value
MD51C506DB59C4A6BBD4A48061559EEB56A
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython36-pytest-timeout
PackageRelease17.10
PackageVersion1.4.2
SHA-1588347EE3ED7232112BC90AA05FA6527F7F2C596
SHA-2569418463355EFDA54E129A9983C3AD2D630EF202A3782FC359C7EF429266FF81C
Key Value
MD58CE708EED250D9A3926E0E82578C3F73
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython2-pytest-timeout
PackageRelease2.5
PackageVersion1.4.2
SHA-17EF62320CB30B67F607D3D81BB3AC25F02C0FC14
SHA-25683219B9CBEAD3C02FC0592B3372DE242ECE9B68103C7E5401E9EF201ABC7A5F4
Key Value
MD53487EFF3242920F06255DEB6857C84A8
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython36-pytest-timeout
PackageRelease1.3
PackageVersion1.4.2
SHA-1B08EE7A70143DA395EA1E0B1D5E2A4F839DBA94D
SHA-256257774C10E5487D69BF6347464A4C3966175A64A831C19A90E011B591128DA47
Key Value
MD50298FBD033B6B51CC9D488C0BA2E2CE1
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython3-pytest-timeout
PackageRelease2.5
PackageVersion1.4.2
SHA-13105262E83DDB75465E5DA7B8C81ABA714D906B8
SHA-256EA2FF3C3026E4951CB1628CA4E075F4EC3F525EC8128FDBFE4694F164294B187
Key Value
MD559B8C1D0391353B104803952111E9FAB
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython38-pytest-timeout
PackageRelease1.3
PackageVersion1.4.2
SHA-160757C822182FCCE95A38BACD67957CA36D3CDAF
SHA-25632E92B94793C79537179E882F2788BEC97FF30A3930A235F46A145F55042E9D2
Key Value
MD53BBD9FC8595FC41156691B8043CA82BE
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython2-pytest-timeout
PackageReleaselp153.2.14
PackageVersion1.4.2
SHA-139DCE83CAD287D3C25BC1976F2FD73977D26D96C
SHA-25620E85B960D20D1E2A48A7586067B48CB673EC2EE4A6AAD7AC3BDFCED28B5B180
Key Value
MD577AE5AC6DF368C0C4F3ABF1BCC6CA0AC
PackageArchnoarch
PackageDescriptionThis 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.
PackageNamepython3-pytest-timeout
PackageReleaselp153.2.14
PackageVersion1.4.2
SHA-1EEDE280AB1F29524B8B73F7EC57E5B9FA6015D8D
SHA-2563B470B7FE41AB368376C681B3CF989FDB9D5930200DFC1AC307550704141D643