Result for 4C626CD26A4C72D59D0E9AAFEAF23E178E6B73B2

Query result

Key Value
FileName./usr/lib/python3.9/site-packages/pytest_timeout-2.0.2-py3.9.egg-info/PKG-INFO
FileSize13798
MD5A782FCE35E06C82F8F3B81F94A83AA1A
SHA-14C626CD26A4C72D59D0E9AAFEAF23E178E6B73B2
SHA-256C32D841CE76404CBF248A120FD220CC9B4FD2F07BC7EF31D20A7D13859B407BE
SSDEEP384:ZpFMA8Yhjc5dNQCAv3e7uM9bz6bKlKm+Kv:2A8SC0+amn
TLSHT11552B7033AC767B10BD68656537D60E7F736C2BD92971598B8DEC018230273583BE6D9
hashlookup:parent-total21
hashlookup:trust100

Network graph view

Parents (Total: 21)

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

Key Value
MD5722B77ABD1962A157784CE3C3BF7B55C
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
PackageRelease18.1
PackageVersion2.0.2
SHA-10168D0892751DCC22BB28AF710849544D94A1FC8
SHA-256B407AE7EA17CC8BEA8E3E4A24D20720C55112B7048923A197744FDA716748BDD
Key Value
MD562558C3CE30CDFA88B94EF5F115665EF
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.1
PackageVersion2.0.2
SHA-103768E1706F31DC8447376C0F94A1A49073EFFDA
SHA-25609A0D26FDBC60133671973F2038BA56DAC64BE8A657AA006B51F9656A2CB3A6B
Key Value
MD56DA0910FE3ECD2D5A15BA9F11939DD27
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.1
PackageVersion2.0.2
SHA-1051C811E728B6A9A2C8D195B1F58D32D37DABCD2
SHA-256B54F3EA9B504F9AE63C6AE55D5E17B34928CF998A92A085F5D108DDA63999DA0
Key Value
MD58C6DC97EBC4A73EBC0E526B91050D99E
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.1
PackageVersion2.0.2
SHA-10A0BC64C2411ADA68F9DB28F5F32CB9F53821C56
SHA-2566448DD3B5E5B5D1A85A008C91640590AEDDD346C1081F681D889B56C1B7AA60B
Key Value
MD5877C5B9EFDC1DE7D49EFF9A16CE8C1D3
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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython39-pytest-timeout
PackageRelease1.1
PackageVersion2.0.2
SHA-10CABD43F9B1394701088FF9C8A7D7C65ED328946
SHA-2564BF7591D250F6CC5288773FFE0A04856A02BAC01573600E2FF8DA5B316564E22
Key Value
MD5113F1F4F0F22525B98F08D0C378E91FB
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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython38-pytest-timeout
PackageRelease1.1
PackageVersion2.0.2
SHA-1361F08B7A8157F40155FA7AF974DA389FF15DD9D
SHA-256C79D1172DF39D72092358C971F93952C62AAE350D48BA354873E9A99FFFB36BF
Key Value
MD588FEA309DB63C6F4C09DC689516559E5
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.
PackageNamepython310-pytest-timeout
PackageRelease18.1
PackageVersion2.0.2
SHA-13C3E800660FC23B07110F61A374E36655B940642
SHA-256B1EF30FAC9C9724424D08C97E764967B02676425297D5E230A4D3A10F28928B4
Key Value
MD500345E7B30FFBB7A6D897EAFD7DE800D
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
PackageReleaselp152.2.1
PackageVersion2.0.2
SHA-13F9AAC8C32FDAC7A9A1FE3041125743BBEDE7AF6
SHA-256885C063352C80BFE40F1C42D1D0F22A36CD0A0AC4704DA1D684D791B7DF2C1B6
Key Value
MD5392CC6957CD9B05AB8A0FA58F9C40E63
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.
PackageNamepython310-pytest-timeout
PackageRelease18.2
PackageVersion2.0.2
SHA-1876984CB9916EAB310F0C20A619CBC9385B9F59C
SHA-2561A5931F7B1A84A57FC574572590CB31C1AC2F738C931DEDC66382735AD5978C6
Key Value
MD5A701E8A7EDCC43FEC680C7D27650F3A2
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
PackageReleaselp154.2.1
PackageVersion2.0.2
SHA-18DB4D581ED6AC9B067375E276FF82F13A0AD84AF
SHA-256A44F40E87C933449735857D0DE43F0BB69ADE192C53C038EBD66821F39A4D59D