Result for C6DA3ABBB426C403464803A17AE3311146A2351D

Query result

Key Value
FileName./usr/lib/python3.9/site-packages/__pycache__/pytest_timeout.cpython-39.opt-1.pyc
FileSize12381
MD5EADF788156282AFA65104C813F190829
SHA-1C6DA3ABBB426C403464803A17AE3311146A2351D
SHA-256FD7EEDE2E4CC00FB33F86C568CFFE26503B30EF94693FCDE72F8040665FFCE04
SSDEEP384:kEZ73lbOjG5OvBc9wtU4TIWAzhWWIwDR1S:k0hXOvCqtU4TQBIwu
TLSHT19C4208898907AB32FCE9F674D26D42E89732D3BB3316525A3419D19C2F0415C8E736DC
hashlookup:parent-total4
hashlookup:trust70

Network graph view

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
MD535F91F8339B55E6666BA9D1642AC5879
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
PackageRelease18.2
PackageVersion2.0.2
SHA-19A6E43597A3C66E01EFE47C276C165B64572EDC7
SHA-256EDA7A7D1C38BBED5CBB78895EFA7AB5156F79EC72F085C0C03914F00652B8A8C
Key Value
MD59A2B2DF252383F2BE6F061F5AE61AEB2
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
PackageRelease18.1
PackageVersion2.0.2
SHA-19F065B3FDA839CD89777750F3EE55021865A3A99
SHA-2566C48F85AF5CC211BB0C075C1A9FF4EF329DAADBF9BA54387E967D234D7410BBF
Key Value
MD5307A14EFDA587A29FA8CC4659ADAD4B7
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
PackageRelease18.2
PackageVersion2.0.2
SHA-198E8D083F1D4942A3802A7F64D1861227D9E5B78
SHA-2567148E55291641395C32E49C630C8C0071BCF1455F1074ADCE16A8B641590BC92
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